You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 17, 2020. It is now read-only.
Ran into an issue where my server running https would fail to connect while localhost would connect fine, finally figured out it was due to loading websockets over WSS. It appears to be an issue in Firefox only, as Chromium seems to load and work fine.
The related Mozilla Bugzilla issue is 1187666. The apparent solution is to load the websocket application directly (not sure if this applies) and accept the certificate. This is a valid certificate on this site however, and Firefox does not throw any invalid certificate errors on other pages, so unless websockets use the default ssl certificate (The shared server's one, which is not in my hostname) instead of the one installed to the site, this should not be happening.
Perhaps fixing issue #1 will fix this issue as well. Until then, HTTPS will need to use Chrome(ium) or maybe IE, or load with HTTP.
The text was updated successfully, but these errors were encountered:
I'm not sure what's happening. I decided to revisit this bug only to find that everything loads fine. Sometimes it takes a couple of seconds, but everything loads. Firefox still throws an error to the console about not being able to connect to the websocket server, but until things stop working I'm not sure there's anything to fix anymore.
Ran into an issue where my server running https would fail to connect while localhost would connect fine, finally figured out it was due to loading websockets over WSS. It appears to be an issue in Firefox only, as Chromium seems to load and work fine.
The related Mozilla Bugzilla issue is 1187666. The apparent solution is to load the websocket application directly (not sure if this applies) and accept the certificate. This is a valid certificate on this site however, and Firefox does not throw any invalid certificate errors on other pages, so unless websockets use the default ssl certificate (The shared server's one, which is not in my hostname) instead of the one installed to the site, this should not be happening.
Perhaps fixing issue #1 will fix this issue as well. Until then, HTTPS will need to use Chrome(ium) or maybe IE, or load with HTTP.
The text was updated successfully, but these errors were encountered: