Vitxi Extensions cant registered

Yesterday i had this issue Empty .env file Vitxi 4.1.0-0 - #4 by maynor

I was able to register vitxi extension in the end, but now once again extensions are not able to register. Also when logging in vitxi seems to freeze right after login showing a blank screen and three loading dots. You have to do a web oage refresh in order to get the interface to load but even after that registration is not happening.

@maynor any idea how to troubleshoot this issue. As mentioned in my previous post firewall rules have been and where working before the update to 4.1.0-0

1 Like

Hello,

Did you complete the wizard or after re-creating the .env did it not redirect to the installation wizard?

Regards,

No after I recovered the .env file it didnt prompt to do any sort of wizard yesterday.

When logging in this is the loading page with the dots that is showing up.

The logs are showing this 401 when the screen is white with the loading dots.

XXX.XXX.XXX.35 - - [15/Aug/2024:18:00:44 -0400] "POST /vitxi-service/v1/broadcasting/auth HTTP/2.0" 401 75 "https://pbx.domain.com/" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/127.0.0.0 Safari/537.36"

And nothing happens unless we reload the page.

Please verify that port 6001 is enabled in VitalPBX and in any firewall you have active

Then, run the following commands:

vitalpbx apply-firewall
/usr/share/vitxi/backend/artisan websockets:ssl-config
systemctl restart vitxi

After that, reload the app by pressing Ctrl+F5 or Ctrl + Shift + R

@maynor, port 6001 is open, I have applied the firewall and ran the following

php artisan websockets:ssl-config
SSL configuration updated successfully!

I cant run /usr/share/vitxi/backend/artisan websockets:ssl-config directly as I get this:

/usr/share/vitxi/backend/artisan websockets:ssl-config
/usr/bin/env: ‘php\r’: No such file or directory

and have restart vitxi multiple times, but still only get the 4 dot loading animation when trying to log in the first time after reloading with CTRL+F5 and after that extensions still cant register.

I compared the .env file to another working server, not sure how it happened but for some reason the WSS_PORT variable in the .env file had extra characters after the actual port 8089, which where the ones causing the issue.

I left the variable like it was supposed to
WSS_PORT = 8089

Restarted Vitxi and since the clients where reaching the websocket properly they where able to register once again.

2 Likes

That’s great that it’s working now! There might have been an unexpected error, or perhaps something went wrong during the package download/update process.

Yes, @maynor something odd happened during the update, but eveything is back to normal. Thank you for all your help.

1 Like

I’m glad to help.

Just in case, We will review the scripts to rule out any internal issues.

Best regards!