Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

FOP2 Community Forum

  1. Home
  2. Support
  3. Chrome 16 - Not Connecting to fop2 2.23

Chrome 16 - Not Connecting to fop2 2.23

Scheduled Pinned Locked Moved Support
34 Posts 15 Posters 198 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • G
    G
    gregc
    wrote on last edited by
    #18

    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.

    1 Reply Last reply
    0
    • N
      N
      nicolas
      wrote on last edited by
      #19

      [quote]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).[/quote]

      Did you try with fop 2.24?

      1 Reply Last reply
      0
      • G
        G
        gregc
        wrote on last edited by
        #20

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

        1 Reply Last reply
        0
        • D
          D
          d_aniel
          wrote on last edited by
          #21

          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.

          1 Reply Last reply
          0
          • N
            N
            nicolas
            wrote on last edited by
            #22

            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,

            1 Reply Last reply
            0
            • D
              D
              d_aniel
              wrote on last edited by
              #23

              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.

              1 Reply Last reply
              0
              • N
                N
                nicolas
                wrote on last edited by
                #24

                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"

                1 Reply Last reply
                0
                • K
                  K
                  krtapas
                  wrote on last edited by
                  #25

                  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

                  1 Reply Last reply
                  0
                  • N
                    N
                    nicolas
                    wrote on last edited by
                    #26

                    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.

                    1 Reply Last reply
                    0
                    • E
                      E
                      Elijah Lynn
                      wrote on last edited by
                      #27

                      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!

                      1 Reply Last reply
                      0
                      • K
                        K
                        krtapas
                        wrote on last edited by
                        #28

                        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

                        1 Reply Last reply
                        0
                        • N
                          N
                          nicolas
                          wrote on last edited by
                          #29

                          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 ?

                          1 Reply Last reply
                          0
                          • K
                            K
                            krtapas
                            wrote on last edited by
                            #30

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

                            Javascript console output

                            http://pastebin.com/6Umpbb2M

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

                            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

                            (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 = http://www.asternic.org
                            ;web_dir = /var/www/fop2

                            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.

                            http://pastebin.com/NfqGqd0a

                            1 Reply Last reply
                            0
                            • N
                              N
                              nicolas
                              wrote on last edited by
                              #31

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

                              1 Reply Last reply
                              0
                              • S
                                S
                                skri11a
                                wrote on last edited by
                                #32

                                I'm having the same problem with all browsers.

                                I just upgraded to the latest Elastix version (2.2.20?) and couldn't connect to Fop 2.23.
                                I upgraded to 2.24 and restarted the fop2 service. I also cleared the cache on all browsers (IE, Chrome and FF).

                                On Chrome it tries 15 attempts and says System Unavailable.
                                IE and FireFox both stay at Attempt 1 and never progress.

                                This was a pre-existing install of FOP2 so I'm not using the new FOP2 installation from the add-ons page (although, is it possible to get FOP2 re-integrated with the add-ons page?)

                                1 Reply Last reply
                                0
                                • K
                                  K
                                  krtapas
                                  wrote on last edited by
                                  #33

                                  I had a non-ascii character at the end of my buttons.cfg. I was created a queue with a label "Entrante Cápsula", but the text editor did change "á" for another character. Later, I cleaned my cache and finally I've access to my panel. Thanks a lot and sorry for had not pay attention to this detail.

                                  1 Reply Last reply
                                  0
                                  • N
                                    N
                                    nicolas
                                    wrote on last edited by
                                    #34

                                    I'm having the same problem with all browsers.

                                    I just upgraded to the latest Elastix version (2.2.20?) and couldn't connect to Fop 2.23.
                                    I upgraded to 2.24 and restarted the fop2 service. I also cleared the cache on all browsers (IE, Chrome and FF).

                                    On Chrome it tries 15 attempts and says System Unavailable.
                                    IE and FireFox both stay at Attempt 1 and never progress.

                                    This was a pre-existing install of FOP2 so I'm not using the new FOP2 installation from the add-ons page (although, is it possible to get FOP2 re-integrated with the add-ons page?)

                                    I think we fixed your problem via the live help. FOP1 was re-enabled when upgrading Elastix, disabling FOP1 fixed the issue.

                                    1 Reply Last reply
                                    0

                                    Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                                    Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                                    With your input, this post could be even better đź’—

                                    Register Login
                                    Reply
                                    • Reply as topic
                                    Log in to reply
                                    • Oldest to Newest
                                    • Newest to Oldest
                                    • Most Votes


                                    • Login

                                    • Don't have an account? Register

                                    • Login or register to search.
                                    Powered by NodeBB Contributors
                                    • First post
                                      Last post
                                    0
                                    • Categories
                                    • Recent
                                    • Tags
                                    • Popular
                                    • World
                                    • Users
                                    • Groups