Hello Guys,
Please help our agent unable to login in Sonata Dialer. Getting an error “FAILED CONNECTION. The connection to the server has failed”
Saw an error on the browser console and says “Websocket connection error”
I used custom port for my HTTPS not sure if it is related to that but based on the change logs VITALPBX team said that it can handle custom port on the version that I am running.
Sonata Dialer version is 4.0.2-1-0
Thank you,
First step would be to check if port 8089 is properly accessible in your server, so check your firewall setting and you can test the following urls, https://yourdomain.com:8089/ws and https://yourdomain.com:8089/httpstatus
If the urls are not loading for your and the port is open in the firewall try restarting the asterisk service in order to also restart the websocker webserver , from the asterisk console of your server core restart now
Yes, I’ve checked that already.
For https://yourdomain.com:8089/httpstatus here is the result on my end
and for this https://yourdomain.com:8089/ws
I did core restart now in the asterisk console and tried again but the issue still the same.
This is not related port 8089. You can see user is showing in registered stat it means ports are open and working
It may be related permission issue on queue form or script which is assigned to this Agnet or may be backend server
I don’t think it is related to permission on queue, form or script. I am currently on testing stage so just created 1 entry on queue, form and script and selected those entries.
If you selected default agent role and then assigned these assets to this user. You will see the same error on agent login screen
Yeah if you go to Role interface there you will see Agent role is not visible may be it is the cause of issue
Yes, I can’t see Agent Role. I think they designed like that but not sure.
@zahid do you use Sonata Dialer also? if yes, do you encounter the same issue as mine?
Hopefully, someone from VitalPBX team will check on this issue.
Yeah i am also on same stage and created same issue on forum
ws is not the same as wss
Hello!
Please run the following commands in the server terminal:
dialer app:fix-permissions
dialer logs:clear
systemctl restart sonata-dialer
systemctl enable sonata-dialer-worker@1 && systemctl start sonata-dialer-worker@1
systemctl enable sonata-dialer-worker@2 && systemctl start sonata-dialer-worker@2
systemctl enable sonata-dialer-worker@3 && systemctl start sonata-dialer-worker@3
Then, reload the App and check if everything is working properly
Regards,
Hi @maynor
Run those commands but still having the same issue.
Cleared App Data after running those commands and tried again same.
Please take note that I am using custom HTTPS port, could that be the reason why having websocket error?
Installed a new version of Vitalpbx which is 4.5 and reconfigured everything and got the same error. Same issue on version Sonata Dialer 4.5.0-2-0
Also, as a testing I allowed all the ports on all firewalls TCP and UDP 0 - 65535 and still getting the same issue.
Try as default as possible
We will conduct the necessary tests to reproduce the issue and resolve it as soon as possible, in the meantime, if feasible, please try using the default HTTPS port
@maynor
Thank you. We will wait and expect for your updates. Really appreciate if we can solve it ASAP.
In my case connection error has been fixed but i getting another issue
My current version is 4.2.0-2
I have created all of aspects as per requirement and active my campaign then login as agent and unable to see any form, contact in agent interface also facing error ( There are no campaigns in active period) while it is active in admin interface
Please check if you have selected the correct time zone under Settings > General Settings. Then, verify that the campaign has pending contacts and that the date range and shift time are configured correctly.
I confirmed now that it is about the custom HTTPS port we’ve set.
Putting back to default 443 works fine and no issue.
When using custom HTTPS port and do inspect element you can able to see the error and it is showing
wss://servername.com/dialer-ws/console failed
the error occurs because it doesn’t include the HTTPS custom port on the WSS link. It still using the default which is 443.
I think it should be like this
wss://servername.com:https-custom-port/dialer-ws/console
wss://servername.com:6781/dialer-ws/console
Another thing I noticed was the error saying FAILED TO LOAD RESOURCES
and on the login window and when signed in as an agent the logo doesn’t show, it just a blank.
Thank you! It is working now after changing my Time zone
