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
TLS stopped working with websockets #2020
Milestone
Comments
Thanks for the good report, I've pushed a fix for this to the |
Built from the fixes branch and TLS with websockets is working again. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Spent the last several days going around in circles trying to find the right configuration to get a web browser to connect to a web socket port with TLS enabled. Took quite a while since TLS works fine on the normal port and my Python scripts were able to do TLS without any issues. I had to do some deep digging to find out that it was just the websocket port that was broken.
Using the openssl command line tool for testing I found that on the websocket port it wasn't sending a certificate at all. Discovered it worked on an older version and ran a git bisect and it looks like it just got broken right when I started to work on enabling TLS support for my project! What timing! ;-)
To test if TLS is working on websockets, enable TLS on the websocket port:
After starting the mosquitto broker:
No subject= information will be printed since no certificate is sent from the mosquitto broker.
Here's the first commit where it broke:
The text was updated successfully, but these errors were encountered: