<![CDATA[FOP2 websocket in Chrome - latest release issues]]>It seems that the latest release of Google chrome has changed its compatibility with websocket, and as such the fop2 panel no longer works in the latest version of Google Chrome.

The code to change this is hidden in your obfuscated code, and as such I'm not able to tell it to use just flash (the main solution I see). Can I get some guidance here please?

]]>http://localhost:4567/topic/891/fop2-websocket-in-chrome-latest-release-issuesRSS for NodeTue, 27 Oct 2026 08:37:19 GMTSun, 18 Sep 2011 20:43:40 GMT60<![CDATA[Reply to FOP2 websocket in Chrome - latest release issues on Mon, 26 Dec 2011 18:23:54 GMT]]>

I am having the same issue.

intento conectar web socket en ws://voip.techex.local:4445

Although this is in both IE and Chrome..

However

[root@voip ~]# /usr/local/fop2/fop2_server --test
Flash Operator Panel 2 - No valid license found. Demo Mode
Connection to manager OK!

Thanks in advance!

Olof

Hi Olof,

If it happens in IE, then it is not the same issue. If you cannot connect to port 4445 could be because you are not on the same network and your router/firewall is not redirecting port 4445. It could be because fop2_server is not running (the --test switch just tries a connection to the manager, it does not tell you if the service is running or not, you can check that with "ps uax |grep fop2" or similar.

Best regards,

]]>http://localhost:4567/post/3965http://localhost:4567/post/3965Mon, 26 Dec 2011 18:23:54 GMT<![CDATA[Reply to FOP2 websocket in Chrome - latest release issues on Sat, 24 Dec 2011 09:33:13 GMT]]>I am having the same issue.

intento conectar web socket en ws://voip.techex.local:4445

Although this is in both IE and Chrome..

However

[root@voip ~]# /usr/local/fop2/fop2_server --test
Flash Operator Panel 2 - No valid license found. Demo Mode
Connection to manager OK!

Thanks in advance!

Olof

]]>http://localhost:4567/post/3964http://localhost:4567/post/3964Sat, 24 Dec 2011 09:33:13 GMT<![CDATA[Reply to FOP2 websocket in Chrome - latest release issues on Mon, 26 Sep 2011 17:11:19 GMT]]>Try to catch me on the live help, you will need to grant me access to your server in order to try connecting myself.. there are ways to do it without the need to disclose passwords or open up firewalls (reverse ssh/port redirection). It would be the only way to troubleshoot for real, forum or email is not good enough.

]]>http://localhost:4567/post/3963http://localhost:4567/post/3963Mon, 26 Sep 2011 17:11:19 GMT<![CDATA[Reply to FOP2 websocket in Chrome - latest release issues on Mon, 26 Sep 2011 11:17:55 GMT]]>I update the Chrome version to 14.0.835.186, but the problem persist.
And, Yes, the fop2 is working with other browsers.
I use fop2 on intranet, we don´t have filters to this network.

]]>http://localhost:4567/post/3962http://localhost:4567/post/3962Mon, 26 Sep 2011 11:17:55 GMT<![CDATA[Reply to FOP2 websocket in Chrome - latest release issues on Sat, 24 Sep 2011 02:33:02 GMT]]>Ok, lets try to not confuse issues. Your chrome seems kind of old? I do not think your problem is related to chrome itself.. is fop2 working with other browsers in your computer? Is port 4445 open and not filtered?

]]>http://localhost:4567/post/3961http://localhost:4567/post/3961Sat, 24 Sep 2011 02:33:02 GMT<![CDATA[Reply to FOP2 websocket in Chrome - latest release issues on Thu, 22 Sep 2011 13:02:39 GMT]]>Chrome Version: 11.0.696.68
FOP2 Version: 2.20

until 2 days ago works fine on my pc, but with others the problem existed.
yesterday i clean my browser cache and after that get this problem with Chrome.

]]>http://localhost:4567/post/3960http://localhost:4567/post/3960Thu, 22 Sep 2011 13:02:39 GMT<![CDATA[Reply to FOP2 websocket in Chrome - latest release issues on Thu, 22 Sep 2011 12:50:49 GMT]]>I am sorry, it works fine for me with the latest google chrome. If I cannot reproduce the issue, I won't be able to fix it. Post your chrome version number (Example: 15.0.874.21) and your exact fop2 version too:

/usr/local/fop2/fop2_server -v

]]>http://localhost:4567/post/3959http://localhost:4567/post/3959Thu, 22 Sep 2011 12:50:49 GMT<![CDATA[Reply to FOP2 websocket in Chrome - latest release issues on Thu, 22 Sep 2011 12:21:15 GMT]]>in some pcs i have the same problem with Chrome, but with other browsers the fop2 open.
on the java script console i see this:
wav false
set session context
formato wav
set menu
Client has HTML5 web sockets!
setLang
set menu
set menu queue
no tiene permiso chat
get cookie extensionlist
get cookie queuelist
get cookie trunklist
get cookie conferencelist
get cookie parklist
Client has HTML5 web sockets!
set session extension
fop2-variablesGENERAL.txtGET https://10.2.25.50/fop2/fop2-variablesGENERAL.txt 404 (Not Found)
Second Init after loading variables
Attempt to connect to port 4445
12
intento conectar web socket en ws://10.2.25.50:4445
11
intento conectar web socket en ws://10.2.25.50:4445
11
intento conectar web socket en ws://10.2.25.50:4445
11
intento conectar web socket en ws://10.2.25.50:4445
11
intento conectar web socket en ws://10.2.25.50:4445
11
intento conectar web socket en ws://10.2.25.50:4445
11
intento conectar web socket en ws://10.2.25.50:4445
11
intento conectar web socket en ws://10.2.25.50:4445
11
intento conectar web socket en ws://10.2.25.50:4445
11
intento conectar web socket en ws://10.2.25.50:4445
11
intento conectar web socket en ws://10.2.25.50:4445
11
intento conectar web socket en ws://10.2.25.50:4445
11
intento conectar web socket en ws://10.2.25.50:4445
11
intento conectar web socket en ws://10.2.25.50:4445
11
intento conectar web socket en ws://10.2.25.50:4445
11
intento conectar web socket en ws://10.2.25.50:4445
11
intento conectar web socket en ws://10.2.25.50:4445
11
intento conectar web socket en ws://10.2.25.50:4445
11
intento conectar web socket en ws://10.2.25.50:4445
11
intento conectar web socket en ws://10.2.25.50:4445
11
intento conectar web socket en ws://10.2.25.50:4445
error function

]]>http://localhost:4567/post/3958http://localhost:4567/post/3958Thu, 22 Sep 2011 12:21:15 GMT<![CDATA[Reply to FOP2 websocket in Chrome - latest release issues on Wed, 21 Sep 2011 00:10:32 GMT]]>What chrome version.subversion are you running? Do you have non ascii characters in button labels?

]]>http://localhost:4567/post/3957http://localhost:4567/post/3957Wed, 21 Sep 2011 00:10:32 GMT<![CDATA[Reply to FOP2 websocket in Chrome - latest release issues on Tue, 20 Sep 2011 16:50:50 GMT]]>I want to second the OP's issue. I'm using the latest version of Chrome & I'm still unable to access FOP2. After logging in, I just hang at the "One moment please, connecting to server" screen. Opening up the JavaScript debugger, I see the following:

intento conectar web socket en ws://192.168.1.5:4445
http://192.168.1.5
Invalid UTF-8 sequence in header value
ws close event
close event
on close reseteo a cero

Over and over again.

IE9 & Firefox both work fine.

]]>http://localhost:4567/post/3956http://localhost:4567/post/3956Tue, 20 Sep 2011 16:50:50 GMT<![CDATA[Reply to FOP2 websocket in Chrome - latest release issues on Tue, 20 Sep 2011 09:32:46 GMT]]>I just updated to 2.22 as FOP2 wasn't loading in Chrome anymore and all went fine for about an hour. Now after the login, the page with all buttons is shown for one second and then only a blank white page remains.

Internet Explorer 9 works (as good as IE9 can)
Firefox 6 works as well

though it's interesting to see, that DND icons are green in IE and Chrome, but red in Firefox... :?

EDIT: clearing Chrome's cache helped here.

]]>http://localhost:4567/post/3955http://localhost:4567/post/3955Tue, 20 Sep 2011 09:32:46 GMT<![CDATA[Reply to FOP2 websocket in Chrome - latest release issues on Sun, 18 Sep 2011 20:49:23 GMT]]>Update to FOP 2.22 that supports websockets-hiby-10 used by the latest google chrome.

]]>http://localhost:4567/post/3954http://localhost:4567/post/3954Sun, 18 Sep 2011 20:49:23 GMT