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. Fop2 not working since chrome version 36 update

Fop2 not working since chrome version 36 update

Scheduled Pinned Locked Moved Support
4 Posts 2 Posters 133 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.
  • R
    R
    rookie01
    wrote on last edited by
    #1

    Hi Guys,

    Fop2 has been working fine for our 200 customers but since the google chrome update to version 36 in the last couple days n-one can now access Fop2. The few computers that havnt automatically updated and are still on version 35 are working fine.

    Do you know if there will be an update so fop2 will work on Chrome version 36? or a fix? or other browsers that work fine?

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

      I had other reports of issues with Chrome today. The problem is that I am using OSX, and my Chrome version is now 38.0.2960 and it works just fine. My suggestion for you is to enable or disable websockets in /var/www/html/fop2/js/presence.js , not sure if you have it enabled or not, in any case, change it so it uses the other mode (fop2 supports both flash xmlsockets and html5 websockets). Perhpas the chrome change affects one of those methods (for example flash), and not websockets, or viceversa.

      In any case, I have to see what Chrome version does windows have and check from there to find out myself, as the OSX version has a higher release number and works fine (With websockets at least).

      Also, be always sure to use the latest FOP2 release.

      1 Reply Last reply
      0
      • R
        R
        rookie01
        wrote on last edited by
        #3

        Hi,

        Thanks for your reply, we are also using MAC OSX but our latest version is only 36.

        I checked the file /var/www/html/fop2/js/presence.js and disablewebsocket was set to false so i set it to true and now its working fine.

        Thanks again.

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

          The last chrome update denies non secure websockets connections over https, so to fix it you have to disable websockets in fop2 (as you did), or upgrade to fop2 2.27 that includes support for secure websockets and configure the ssl certificates in fop2.cfg for it.

          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