I am seeing this too. Suddenly today, the 7th of February. Up-to-date Chrome, but also Firefox and Edge, are failing to connect with Web Sockets. The retro IE version that is still on 2019 Server works flawlessly, though. Does anyone know what changed? Is there a patch to FOP2?
OK, narrowed this down to an issue with the web socket using TLS 1.0, which Chrome won't use. I'll try to see if there's a newer binary available, and then if I'm desperate, look at putting it behind a reverse proxy.
It's the same with us. After updating chrome, fop2 stopped connecting to webscocket with encryption. Even with up-to-date certificates. Works great without encryption. Same thing with firefox and and edge.
Browser deprecation of TLS v1.0 and v1.1 finally kicked in it seems. If you need to connect via https to FOP2, you must use version 2.31.28 (released more than one year and a half ago), that includes support for TLS v1.2
If your FOP2 license is older than a year, and your version is less that 2.31.28, in order to upgrade FOP2 to the latest version you will need to upgrade your license first. The annual software maintenance is $20, can be purchased from here:
If you cannot or do not want to upgrade FOP2, then you will need to either install an older web browser, or use http instead of https that will work fine no matter the versions you have of browsers/fop2.
Comments
I am seeing this too. Suddenly today, the 7th of February. Up-to-date Chrome, but also Firefox and Edge, are failing to connect with Web Sockets. The retro IE version that is still on 2019 Server works flawlessly, though. Does anyone know what changed? Is there a patch to FOP2?
I'm also having the same problem. I noticed that it was after a Windows 10 update, in previous versions of Windows the failure does not occur.
Use Opera Browser...
I've actually gotten this fixed, at least as fixed as modern security snobs will allow. Step one, get a valid cert for your web server. Step two, put the same cert in place with FOP2's web socket, as documented here: https://www.fop2.com/docs/faq.php#IcannotconnecttoFOP2whileusingHTTPS/SSL
Ugh, this works for Firefox, but Chrome is still reluctant.
OK, narrowed this down to an issue with the web socket using TLS 1.0, which Chrome won't use. I'll try to see if there's a newer binary available, and then if I'm desperate, look at putting it behind a reverse proxy.
It's the same with us. After updating chrome, fop2 stopped connecting to webscocket with encryption. Even with up-to-date certificates. Works great without encryption. Same thing with firefox and and edge.
Browser deprecation of TLS v1.0 and v1.1 finally kicked in it seems. If you need to connect via https to FOP2, you must use version 2.31.28 (released more than one year and a half ago), that includes support for TLS v1.2
If your FOP2 license is older than a year, and your version is less that 2.31.28, in order to upgrade FOP2 to the latest version you will need to upgrade your license first. The annual software maintenance is $20, can be purchased from here:
https://www.fop2.com/buy.php?hint=annualupgrade
After upgrading the license, you can upgrade FOP2 to the latest version (2.31.31 at time of this post) with the command:
wget -O - http://download.fop2.com/upgrade_fop2.sh | bashIf you cannot or do not want to upgrade FOP2, then you will need to either install an older web browser, or use http instead of https that will work fine no matter the versions you have of browsers/fop2.