-
Notifications
You must be signed in to change notification settings - Fork 466
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
wss connection interrupted error in firefox, works in chrome #231
Comments
I have the exact same issue. But it should probably be fixed. |
This seems to be an issue with the |
any updates to this, I also was able to fix in firefox by setting "network.http.spdy.websockets" to FALSE in about:config. I saw Roger, one of the mosquitto maintainers, plans on moving away from libwebsockets. However, another fix is to remake libwebsockets but without http2 support. I have yet to do this however, and have never built a dependency from source so it should be interesting haha. |
Fast forward a year later... any news on this? The issue apparently still persists. I can't rely on users changing their config settings 😅 What did you guys do to resolve the issue? |
I resolved it as posted here: eclipse-mosquitto/mosquitto#1211 (comment) Thus, by installing a |
I'm using the latest paho-mqtt.js from master and i'm testing it against the server at test.mosquitto.org on port 8081. In chrome, everything works fine, but in firefox I get:
The connection to wss://test.mosquitto.org:8081/mqtt was interrupted while the page was loading.
I've tried putting the connection kickoff at window onload instead of via a connect button, but got the same error in firefox.
Curiously, if I change to an http server instead of https and change the code to not use "useSSL" in the connect options (along with switching to port 8080), then everything works fine in firefox. It is only when https / wss is being used that I keep getting this error and can't get any connect / subscription to work in firefox.
This is using Firefox 78.4.1esr (32-bit)
The text was updated successfully, but these errors were encountered: