Chrome 16 - Not Connecting to fop2 2.23

scubes13 · December 2011

Today, I had clients begin to call saying they could not connect to the fop2 server. It times out after inserting user/pass.

On examination, they were all using Chrome which updated to version 16.

I was able to access using version 15. I updated my machine to version 16 and it stopped working as well.

Any thoughts?

Synapticx · December 2011

I'm seeing the same issue-
When I inspect using the JavaScript console I see:
"Error during WebSocket handshake: 'Sec-WebSocket-Accept' header is missing"

tekach · December 2011

Exactly same behaviour / error in our case (FOP 2.23 vs Chrome 16.x).

marvinhorst · December 2011

I have this problem also. I updated to the chrome 17 (the dev version) hoping that the problem would be resolved, but it has persisted

nicolas · December 2011

Please try with version 2.24 and let me know how it goes. I have also included a flag in presence.js to disable websockets and default to flash xmlsockets that will not have issues. But again, it is working ok for me with the latest chrome, perhaps I did not update the debial tarballs correctly for version 2.23..

tekach · December 2011

Can someone please point me to the fop 2.24 download location? It seems there's only 2.23 in download section.

Thanks a lot.

Francisco.yebra · December 2011

Versions 2.23 , 2.21 and 2.21 beta are affected by Google Chrome update to v16 (we don't use 2.22)
Old versions, like 2.11, work fine 8)

nicolas · December 2011

Version 2.24 is being tested. I am about to release it as final.

I used 2.23 and 2.24 with chrome 16 and 17 and they worked fine. In any case, I have added a switch in 2.24 to disable websockets support (the source of the incompatibility) if you still have issues. Websockets are faster than flash xmlsockets, but is still in development, the specification changes every week.

Old versions of fop2 are not affected because they do not support websockets at all.

tompdillon · December 2011

I had the same problem. Just updated to fop2 2.24 and it now works fine in Chrome 17.

Was killing me using Firefox as I got myself hooked on Chrome.

Thanks for the attention to the problem.

mtk · December 2011

I had the same problem. Just updated to fop2 2.24 and it now works fine in Chrome 17.

Was killing me using Firefox as I got myself hooked on Chrome.

Thanks for the attention to the problem.

I've just upgraded to chrome 17 to test this out, and I'm still not able to connect. (Firefox works fine).

nicolas · December 2011

I had the same problem. Just updated to fop2 2.24 and it now works fine in Chrome 17.

Was killing me using Firefox as I got myself hooked on Chrome.

Thanks for the attention to the problem.

I've just upgraded to chrome 17 to test this out, and I'm still not able to connect. (Firefox works fine).

What fop2 version?

mtk · December 2011

I had the same problem. Just updated to fop2 2.24 and it now works fine in Chrome 17.

Was killing me using Firefox as I got myself hooked on Chrome.

Thanks for the attention to the problem.

I've just upgraded to chrome 17 to test this out, and I'm still not able to connect. (Firefox works fine).

What fop2 version?

2.23

njackson · December 2011

How soon do you anticipate 2.24 being available? Or is there a link I can download it from?

taphawane · December 2011

I have the same issue, where can I find fop2 2.24, because when I go to the download center I am just seeing 2.23

nicolas · December 2011

You can get it from here:

tompdillon · December 2011

I think you may have misunderstood my post.

Upgrading Chrome did not help me.

I had to upgrade fop2 to 2.24 from 2.23. Then Chrome works fine.

mtk · December 2011

thanks!
this seem to work now...

gregc · December 2011

I've upgraded to 2.24 but am having issues. At first, Chrome would connect but there would be a gray box at the bottom of the screen with what looks like some code in it. But everything else was functional.

Was unable to access the phonebook, so I went into the fop2 freepbx module and did a fop2 permissions update (hadn't don't before, did it individually in the users module before). Now, unable to connect to the panel using chrome at all. It is at the "One Moment Please" screen with the little circle rotating. No attempts.

I did a service fop2 restart, but that didn't work either.

IE8 works fine.

nicolas · December 2011

I had the same problem. Just updated to fop2 2.24 and it now works fine in Chrome 17.

Was killing me using Firefox as I got myself hooked on Chrome.

Thanks for the attention to the problem.

I've just upgraded to chrome 17 to test this out, and I'm still not able to connect. (Firefox works fine).

Did you try with fop 2.24?

gregc · December 2011

Thanks to Nicolas's help, a simple emptying of the browser cache fixed my problem.

d_aniel · December 2011

I've upgraded FOP2 to 2.24 but I am unable to access the phonebook and recordings. I see only "You do not have permissions to access this resource". I've cleared the browser cache but this not fixed my problem. I've tried Chrome 16 and other browsers.

nicolas · December 2011

To access the phonebook you must have working php sessions, that is unrelated to the fop2 version you use. You also must log into fop2 using the standard directory /fop2 . If you have it in some custom location, be sure to update all the proper files.

Best regards,

d_aniel · December 2011

I've restored setvar.php file from 2.23 version and now phonebook works fine. I'm not sure that is good resolution, but works.

nicolas · December 2011

Did you restart the fop2 daemon? You cannot run the phonebook from 2.24 over a running 2.23 version. Checking the version with -v is not enough, you must restart the running process: "service fop2 restart"

krtapas · December 2011

Hi, I've Chrome 16.0.912.63 m, fop2_server version 2.24, Debian 32 bits and I still having troubles to get connected. I'm attaching log code. Thanks in advance.

HTML5 Web Socket Connection

190.xx.xx.xx => HTTP/1.1 101 Switching Protocols
Upgrade: WebSocket
Connection: Upgrade
Sec-WebSocket-Accept: JpGZhdGP1t1+yIhmANj0931kW/E=

** MAIN AMI event received...
** MAIN Processing command received from flash clients...

190.xx.xx.xx <= <msg data="GENERAL|contexto|1|" />

-- PROCESS_FLASH_COMMAND origen GENERAL accion contexto destino 1 password

190.xx.xx.xx => { "btn": "0", "cmd": "key", "data": "mLPqEeJYVMONtS1v61fn7PkMztp3SKhj", "slot": "" }

190.xx.xx.xx => { "btn": "0@GENERAL", "cmd": "version", "data": "2.24!!1", "slot": "" }

** MAIN New client connection 127.0.0.1

** MAIN AMI event received...
** MAIN Processing command received from flash clients...

127.0.0.1 <= <msg data="GENERAL|contexto|1" />

-- PROCESS_FLASH_COMMAND origen GENERAL accion contexto destino 1 password

127.0.0.1 => { "btn": "0", "cmd": "key", "data": "AiGERYDOflWe7zQkdb6fgne", "slot": "" }

127.0.0.1 => { "btn": "0@GENERAL", "cmd": "version", "data": "2.24!!1", "slot": "" }

** MAIN AMI event received...
** MAIN Processing command received from flash clients...

127.0.0.1 <= <msg data="GENERAL|checkauth|admin|67440750e174215cf7323303aa0f989c" />

-- PROCESS_FLASH_COMMAND origen GENERAL accion checkauth destino admin password 67440750e174215cf7323303aa0f989c

** CLEAN SOCKET connection lost removing socket IO::Socket::INET=GLOB(0xd6325ac)
** CLEAN SOCKET flash client connection lost

Flash clients connected: 1

Use of uninitialized value in array element at script/fop2_server.pl line 11840.
Use of uninitialized value in concatenation (.) or string at script/fop2_server.pl line 11841.
190.xx.xx.xx:2843 IO::Socket::INET=GLOB(0xd0a9648),

** MAIN AMI event received...
** MAIN Processing command received from flash clients...

190.xx.xx.xx <= <msg data="1|auth|admin|8ce6421734abdb3d80e082362dc2d0e0" />

-- PROCESS_FLASH_COMMAND origen 1 accion auth destino admin password 8ce6421734abdb3d80e082362dc2d0e0

** RECEIVING AUTH REQUEST for admin

TRYING TO VALIDATE USER admin

VALIDAR USUARIO admin@GENERAL

VALIDAR USUARIO admin OK con clave regular (190.xx.xx.xx)

** SENDING BUTTONS from GENERAL to client at 190.xx.xx.xx

mi perm all = 0 (0)

190.xx.xx.xx => { "btn": "0@GENERAL", "cmd": "preferences", "data": "e30=", "slot": "" }

190.xx.xx.xx => { "btn": "0@GENERAL", "cmd": "vmailpath", "data": "/var/spool/asterisk/voicemail", "slot": "" }

190.xx.xx.xx => { "btn": "0@GENERAL", "cmd": "permit", "data": "YWxs", "slot": "" }

190.xx.xx.xx => { "btn": "0@GENERAL", "cmd": "permitbtn", "data": "YWxsITA=", "slot": "" }

190.xx.xx.xx => { "btn": "8@GENERAL", "cmd": "zbuttons", "data": "hc7PSsNAEAbwe5+ieYJ2/+kp0CQOGoiTahNojxFXEcpWzS546Mv6JoZqYd0us9eZb775sdUtIDwWzfHJWXswxwy2HeCmbjFnS7bMqrsCEZp8U68Xp8F9UTdluz1tV8/6ZXB7mzVFOWXgy2ozvh3M/JzEi/Nut4Zcn4NZ1WI3fcyHV22sHmec9rDQw3wPozws5mEpj6A9PPRw38MpD495eMojaY8IPcL3CMojYh6R8ijaI0OP9D2S8siYR6Y8V7RHhR7lexTlUTGPSnmuLzx/1cZ+DlNiXn2/j24//Ct/6KGHRY1l2+PN74cPp52e/QA=", "slot": "" }

** MAIN AMI event received...
** MAIN Processing command received from flash clients...

190.xx.xx.xx <= <msg data="1|ping||" />

-- PROCESS_FLASH_COMMAND origen 1 accion ping destino password

190.xx.xx.xx => { "btn": "0", "cmd": "pong", "data": "IAogICAgICAgIHZhciB6aCA9IGZpbmRIaWdoZXN0WigpOwogICAgICAgIHZhciBmb290ID0gJCgiZm9vdGVyIik7CiAgICAgICAgdmFyIHRlbXBsYXRlID0gQmFzZTY0LmRlY29kZSgiUEdScGRpQnBaRDBpSTN0cFpIMGlQanhoSUdoeVpXWTlJbWgwZEhBNkx5OTNkM2N1Wm05d01pNWpiMjBpUGtaUFVESThMMkUrSUMwZ1ZtVnljMmx2YmlBOGMzQmhiaUJwWkQwaVptOXdkbVZ5YzJsdmJpSStJM3QyWlhKemFXOXVmVHd2YzNCaGJqNGdMU0JNYVhSbElGWmxjbk5wYjI0Z0xTQk1hVzFwZEdWa0lIUnZJREUxSUdWNGRHVnVjMmx2Ym5NZ0xpQkNkWGtnYVhRZ1BHRWdhSEpsWmowaWFIUjBjRG92TDNkM2R5NW1iM0F5TG1OdmJTOWlkWGt1Y0dod0lqNXViM2M4TDJFK0lHWnZjaUIxYm14cGJXbDBaV1FnWlhoMFpXNXphVzl1Y3k0Z1NXWWdlVzkxSUdGc2NtVmhaSGtnYUdGMlpTQmhJR052WkdVZ1pXNTBaWElnYVhRZ1BHRWdhSEpsWmowaUl5SWdiMjVEYkdsamF6MGljbVZuYVhOMFpYSW9LVHNnY21WMGRYSnVJR1poYkhObE95SSthR1Z5WlR3dllUNDhMMlJwZGo0PSIpOwoKICAgICAgICBpZihjdXJyZW50cmVsZWFzZSAhPT0gIiIpIHsKICAgICAgICAgICAgaWYoZGVtb3ZlcnNpb24gPT0gIjAiKSB7CiAgICAgICAgICAgICAgICBkb2N1bWVudC50aXRsZSA9ICJGbGFzaCBPcGVyYXRvciBQYW5lbCAyIjsKICAgICAgICAgICAgICAgIGZvb3QudXBkYXRlKG5ldyBUZW1wbGF0ZSh0ZW1wbGF0ZSkuZXZhbHVhdGUoe3ZlcnNpb246IGN1cnJlbnRyZWxlYXNlLCBsaWNlbnNlOiBjdXJyZW50bGljZW5zZX0pLCAiYWZ0ZXIiICk7CiAgICAgICAgICAgIH0gZWxzZQogICAgICAgICAgICBpZihkZW1vdmVyc2lvbiA9PSAiMSIpIHsKICAgICAgICAgICAgICAgIGRvY3VtZW50LnRpdGxlID0gIkZsYXNoIE9wZXJhdG9yIFBhbmVsIDIiOwogICAgICAgICAgICAgICAgZm9vdC51cGRhdGUobmV3IFRlbXBsYXRlKHRlbXBsYXRlKS5ldmFsdWF0ZSh7dmVyc2lvbjogY3VycmVudHJlbGVhc2UsIGxpY2Vuc2U6IGN1cnJlbnRsaWNlbnNlfSksICJhZnRlciIgKTsKICAgICAgICAgICAgfSBlbHNlCiAgICAgICAgICAgIGlmKGRlbW92ZXJzaW9uID09ICIyIikgewogICAgICAgICAgICAgICAgZG9jdW1lbnQudGl0bGUgPSAiRmxhc2ggT3BlcmF0b3IgUGFuZWwgMiI7CiAgICAgICAgICAgICAgICBmb290LnVwZGF0ZShuZXcgVGVtcGxhdGUodGVtcGxhdGUpLmV2YWx1YXRlKHt2ZXJzaW9uOiBjdXJyZW50cmVsZWFzZSwgbGljZW5zZTogY3VycmVudGxpY2Vuc2V9KSwgImFmdGVyIiApOwogICAgICAgICAgICB9CiAgICAgICAgICAgIGZvb3Quc3R5bGUudmlzaWJpbGl0eSA9ICJ2aXNpYmxlIjsKICAgICAgICAgICAgZm9vdC5zdHlsZS5kaXNwbGF5ID0gImJsb2NrIjsKICAgICAgICAgICAgZm9vdC5zdHlsZS5iYWNrZ3JvdW5kID0gIiNBQUEiOwogICAgICAgICAgICBmb290LnN0eWxlLmNvbG9yID0gIiMwMDAiOwogICAgICAgICAgICBmb290LnN0eWxlLmJvdHRvbSA9ICIwIjsKICAgICAgICAgICAgZm9vdC5zdHlsZS5sZWZ0ID0gIjAiOwogICAgICAgICAgICBmb290LnN0eWxlLnBhZGRpbmdUb3AgPSAiM3B4IjsKICAgICAgICAgICAgZm9vdC5zdHlsZS53aWR0aCA9ICIxMDAlIjsKICAgICAgICAgICAgZm9vdC5zdHlsZS5wb3NpdGlvbiA9ICJmaXhlZCI7CiAgICAgICAgICAgIGZvb3Quc3R5bGUuekluZGV4ID0gIiIremg7CiAgICAgICAgfQogICAg", "slot": "" }

** MAIN closing 190.xx.xx.xx

** CLEAN SOCKET connection lost removing socket IO::Socket::INET=GLOB(0xd0a9648)
** CLEAN SOCKET flash client connection lost
** CLEAN SOCKET user admin logged off
No flash clients connected

nicolas · December 2011

The log seems normal, you are validating and everything is going well according to that capture. Try disabling websockets altogether in /var/www/html/fop2/js/presence.js (set disableWebsockets to true). Then try again.. but anyways, the log seems ok.

Elijah Lynn · December 2011

I've upgraded to 2.24 but am having issues. At first, Chrome would connect but there would be a gray box at the bottom of the screen with what looks like some code in it. But everything else was functional.

I had the exact same issue after our provider just upgraded us from 2.23 to 2.24 in Chrome 16, grey box at bottom w/javascript error/text and afterwards got the "one moment screen". Thanks to the subsequent comment, cleared browser cache in Chrome and all is working great now!!!

FOP2 is Rocking!!!

Thanks Nicolas!

krtapas · December 2011

Hmm, I'd set disableWebsockets to true, removed browser cache and the trouble continues. I'm attaching my log again, thanks Nicolás.

nicolas · December 2011

Hmm, I'd set disableWebsockets to true, removed browser cache and the trouble continues. I'm attaching my log again, thanks Nicolás.

http://pastebin.com/jqJhfhuW

The server log is fine, in any case you should open the javascript console in google chrome. The problem is fixed, either you are still loading fop 2.23 or older client pages (perhaps you are not using the standard /fop2 directory, or you have elastix or freepbx with a custom .php index page that is not updated), or you are still running fop 2.23 server. Did you restart the fop2_server after upgrade? Are you using Elastix and installed fop2 via its marketplace/rpm ?

krtapas · December 2011

[color=#FF0000:2wnmtl3b]The server log is fine, in any case you should open the javascript console in google chrome.[/color:2wnmtl3b]

Javascript console output

According to some posts, when fop2-variablesGENERAL.txt is not present, doesn't affect system operation.

[color=#FF0000:2wnmtl3b]The problem is fixed, either you are still loading fop 2.23 or older client pages[/color:2wnmtl3b]

I'm using fop 2.24, not upgraded, fresh installed.
# /usr/local/fop2/fop2_server -v
fop2_server version 2.24

[color=#FF0000:2wnmtl3b](perhaps you are not using the standard /fop2 directory, or you have elastix or freepbx with a custom .php index page that is not updated), or you are still running fop 2.23 server.[/color:2wnmtl3b]

I'm usign standard directory and I had installed asterisk from sources, without FreePBX or Elastix.
; Daemon definitios
;listen_port = 4445
;restrict_host =
;web_dir = /var/www/fop2

[color=#FF0000:2wnmtl3b]Did you restart the fop2_server after upgrade? Are you using Elastix and installed fop2 via its marketplace/rpm ?[/color:2wnmtl3b]

I had restarted service and server itself. I'm using Debian 32 bits. I'm attaching my installation process.

nicolas · December 2011

Does your buttons.cfg file contains any non ascii chars? Can you send your buttons file to me privately?

Chrome 16 - Not Connecting to fop2 2.23

Comments