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.
M
m.kriebel
@m.kriebel
Posts
-
Now I can't open FOP2 with Chrome. -
Now I can't open FOP2 with Chrome.Ugh, this works for Firefox, but Chrome is still reluctant.
-
Now I can't open FOP2 with Chrome.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
-
Now I can't open FOP2 with Chrome.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?
-
Extension Privacy override based on logged in userOur customer would like to give access to FOP2 to most of their users, but wants privacy on all extensions except for some privileged users. This seems like a reasonable idea, but as implemented it looks like privacy is set per-button, and there is no way for a user account to over-ride this. Might this be an easy patch? Is there a workaround? A plugin that does this?