<![CDATA[Chrome Version 84.0.4147.89 Breaks FOP2 https Connections]]>Hello, as of the latest Google Chrome update (version 84), we can no longer load https connections to the FOP2 web page. Http is still working normally. We believe this is related to the large list of depricated items in this update, as we are able to load the FOP2 website normally via https on older versions of Chrome from the same location.

Thanks!

]]>http://localhost:4567/topic/2873/chrome-version-84.0.4147.89-breaks-fop2-https-connectionsRSS for NodeTue, 27 Oct 2026 01:47:43 GMTTue, 21 Jul 2020 15:42:58 GMT60<![CDATA[Reply to Chrome Version 84.0.4147.89 Breaks FOP2 https Connections on Thu, 23 Jul 2020 19:53:01 GMT]]>Well...yes...the fact is that FOP2 versions 2.31.27 and lower support only TLS v 1.X that Chrome just removed from its new version. And FOP2 2.31.28 and upcoming supports TLS v2.X.
TLS support it is always suggested, but mostly when you visit the site (in this case FOP2) from WAN.
If you use FOP2 on LAN only, then you can remove TLS support for FOP2 and still connect fine without the need to upgrade it.

]]>http://localhost:4567/post/12019http://localhost:4567/post/12019Thu, 23 Jul 2020 19:53:01 GMT<![CDATA[Reply to Chrome Version 84.0.4147.89 Breaks FOP2 https Connections on Wed, 22 Jul 2020 13:55:26 GMT]]>Hey, just wanted to chime in again to say that agudino's recommended fix to get a new annual maintenance license and upgrade to the latest release worked like a charm for us, and https access is back up in Chrome now. Thanks again!

]]>http://localhost:4567/post/12018http://localhost:4567/post/12018Wed, 22 Jul 2020 13:55:26 GMT<![CDATA[Reply to Chrome Version 84.0.4147.89 Breaks FOP2 https Connections on Wed, 22 Jul 2020 05:11:34 GMT]]>Fixed my issue instantly... silly thing is, the main website has a banner about this issue - I didn't check the main website I came straight to the forum 😉 oops! all better - thanks Nicolas! (& agudino!)

]]>http://localhost:4567/post/12017http://localhost:4567/post/12017Wed, 22 Jul 2020 05:11:34 GMT<![CDATA[Reply to Chrome Version 84.0.4147.89 Breaks FOP2 https Connections on Tue, 21 Jul 2020 21:03:44 GMT]]>Thanks everyone for the confirmation and tips! We are going to look into renewing licensing on our end so that we can update FOP2 and will let you know how it goes. 🙂

]]>http://localhost:4567/post/12016http://localhost:4567/post/12016Tue, 21 Jul 2020 21:03:44 GMT<![CDATA[Reply to Chrome Version 84.0.4147.89 Breaks FOP2 https Connections on Tue, 21 Jul 2020 17:03:07 GMT]]>PS Additional note. The same change seemed to affect a recent version of firefox. It too suffered from broken secure websockets with fop2 after their recent update however at the time I thought maybe it was a "them" thing instead of an "us" thing. Now that the same effect has happened in Chrome perhaps the issue is how the secure sockets are set up in fop2?

]]>http://localhost:4567/post/12015http://localhost:4567/post/12015Tue, 21 Jul 2020 17:03:07 GMT<![CDATA[Reply to Chrome Version 84.0.4147.89 Breaks FOP2 https Connections on Tue, 21 Jul 2020 16:28:58 GMT]]>Same issue here. http is a work around for the moment. https was working in chome prior to this update.

]]>http://localhost:4567/post/12014http://localhost:4567/post/12014Tue, 21 Jul 2020 16:28:58 GMT<![CDATA[Reply to Chrome Version 84.0.4147.89 Breaks FOP2 https Connections on Tue, 21 Jul 2020 16:21:43 GMT]]>Chrome Users!
The latest Chrome update (version 84) disabled/deprecated TLS version 1. FOP2 version 2.31.27 or older won't work with Chrome 84 via HTTPS. You must upgrade FOP2 to at least version 2.31.28 to get it working over HTTPS with latests versions of Chrome. You can upgrade FOP2 with one command. If your license is older than a year, you should purchase the annual software maintenance for the upgrade to work.

]]>http://localhost:4567/post/12013http://localhost:4567/post/12013Tue, 21 Jul 2020 16:21:43 GMT<![CDATA[Reply to Chrome Version 84.0.4147.89 Breaks FOP2 https Connections on Tue, 21 Jul 2020 16:05:48 GMT]]>I am having the same problem. The strange thing is, the problem doesn't seem to be across the board. My Chrome is running 84.0.4147.89 but I can access FOP2 fine. However, a few of our clients on the same version of chrome are running into the ssl problem.

]]>http://localhost:4567/post/12012http://localhost:4567/post/12012Tue, 21 Jul 2020 16:05:48 GMT