I have a client with an Elastix 2.4 system running Asterisk 11.11 and FOP2 2.26. There are about 10 users connecting to FOP2. It's been fine since the initial installation. We have never been able to access it via Firebox but Chrome has worked fine. Late last week I could not access the panel from the server I use for access (W2008) from any browser. The other users were fine until today when they could not access the panel from Chrome but found they could use IE. The panel sits at the "Connecting to server - attempt 1. From researching the problem that would seem to indicate a connection problem. I've checked the firewall, which is off.
Anyone have a thought at would I should look at next?
Thanks
-
10 years ago
-
Do you have websockets enabled or disabled in /var/www/html/fop2/js/presence.js ? Try changing that and see if the problem goes away. Best regards,
-
They were enabled. I have disabled them and restarted fop2. fop2 is still not connecting.
-
I can get in with Chrome now but not Firefox which is the way it was before. Thanks for the help.
-
My users are reporting things are OK. Any idea what changed to require changing the websockets change?
-
I think the problem is that the latest chrome update does not allow to have a regular websocket connection over a secure http connection. You can have normal and secure http connections withing your browser and web server (http/https). You can also have websockets and secure websockets (ws/wss).
FOP2 supports secure web sockets since version 2.27 released this year. Version 2.26 does not support it.
Prevous Chrome versions allowed to use a secure http connection and an insecure websocket connection. The last udpate negates that connection.
So, you have to either disable websockets for FOP 2.25/2.26 in presence.js, or upgrade FOP2 to version 2.27 and be sure to set the ssl certificates in fop2.cfg.
Other browsers are not affected by this, except firefox that since its first support for websockets it denied non secure websockets over https, for what you have a workaround via about:config described in this post:
http://www.fop2.com/blog/firefox-11-websockets-and-fop2
So, to all users using https to connect to fop2, you should upgrade to FOP 2.27 to avoid issues, or disable websockets in /var/www/html/fop2/js/presence.js
Best regards,
-
Thanks for the explanation.
