# Vitxi 4.6.0-5 cant connect to server

**URL:** https://forums.vitalpbx.org/t/vitxi-4-6-0-5-cant-connect-to-server/6431
**Category:** VitXi WebRTC
**Created:** [August 26, 2026, 2:37pm UTC](https://forums.vitalpbx.org/t/vitxi-4-6-0-5-cant-connect-to-server/6431 "2026-08-26T14:37:41Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![hlev](https://forums.vitalpbx.org/user_avatar/forums.vitalpbx.org/hlev/32/42_2.png) [@hlev](https://forums.vitalpbx.org/u/hlev)
#### Post date: [August 26, 2026, 2:37pm UTC](https://forums.vitalpbx.org/t/vitxi-4-6-0-5-cant-connect-to-server/6431/1 "2026-08-26T14:37:42Z")

</div>

Server was recently upgrade from 4.2.0-6 to 4.5.3-8 for some reason the connection to the server is not able to be set, Vitxi 4.6.0-5 is installed directly in the vital server and no settings where changed.

 ![image](https://forums.vitalpbx.org/uploads/default/original/2X/5/5da34ce32a38907aba07557f5c3aee312918f6f7.png)

Firewall rules are also set in place for 8089, 6001 and 3501. Once again everything was working properly before, any further steps to troubleshoot or fix this issue?

---

<div class="post-metadata">

### Author: ![hlev](https://forums.vitalpbx.org/user_avatar/forums.vitalpbx.org/hlev/32/42_2.png) [@hlev](https://forums.vitalpbx.org/u/hlev)
#### Post date: [August 26, 2026, 2:43pm UTC](https://forums.vitalpbx.org/t/vitxi-4-6-0-5-cant-connect-to-server/6431/2 "2026-08-26T14:43:49Z")

</div>

For some reason the .env file was missing OCTANE\_SERVER=swoole as the error logs kept showing roadrunner, adding this to the .env file and doing a full reboot allowed Vitxi to connect again without the RPC error.

---

<div class="post-metadata">

### Author: ![maynor](https://forums.vitalpbx.org/letter_avatar_proxy/v4/letter/m/3e96dc/32.png) [@maynor](https://forums.vitalpbx.org/u/maynor)
#### Post date: [August 26, 2026, 4:39pm UTC](https://forums.vitalpbx.org/t/vitxi-4-6-0-5-cant-connect-to-server/6431/3 "2026-08-26T16:39:23Z")

</div>

Hello,

Perfect! FYI, port 6001 is no longer necessary, so you may remove it from the firewall rules.

Best regards,
