Are you using FOP 2.11? You should upgrade if you want to use modern/recent OS and Browsers. In version 2.11 websockets cannot be disabled on the fop2 server side, for example, etc.
Somehow I managed to get a mix of 2.11 and 2.26 in place :oops: My apologies
Getting everything to 2.26 solved the issue.
Question: where did you run wireshark? on the desktop machine? on the server? somewhere in between?
On the desktop machine.
Question: Can you connect from other machines? This thread was hijacked with many people thinking they have the same problem but it is not the same problem. For example, using FOP 2.11 with the latest chrome is a recipe for problems, you MUST upgrade fop2 as well as you upgraded your browser.
The same effects occured everywhere as it was server related. However, Chromium on a Linux desktop still goes "Snap!" immediately (can't even log in). This is not an issue for me (Chromium is not used at my customer's site).
And finally, if the connection is established, as it seems it is, but then the application is tuck on "Connection to server X", it most probably means you have some non ASCII characters in your button labels, and the button config file or mysql for autoconfiguration is not sending the data encoded in UTF8. Again, this is NOT RELATED at all with the original post on this thread.
This was not an issue, there are no non ASCII characters (or all is UTF8 as I don't ever accept any other encoding wherever I see it, UTF8 rulez).
