-
Notifications
You must be signed in to change notification settings - Fork 663
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
MQTT with TLS not working #3211
Comments
So you should remove these parts from configuration / documentation. |
According to #2625 (comment) it should work. Can you test if it works with TLS 1.2? |
My server (I use traefik as TLS proxy to Mosquitto) supports TLS 1.2 and to be sure I just verified it with a modified Python example. Possible other causes I want to check:
|
OK I checked the behavior of the client with a simple TCP/IP honeypot server. The client doesn't send any data at all and just terminates the connection. Which means it doesn't even try to start TLS negotiation. Could it be that certificate in PEM format is not supported and you have to provide DER format? ESP32 documentation says
|
@LordGuilly Can you provide some documentation how you generated your certificate? This seems not to be clear. I looked at https://tasmota.github.io/docs/TLS/#implementation-notes but there is a lot of information and not all seems to apply to our ESP32. |
when I added this, I used mutual TLS, so used both server and client certs, connecting to AWS. I don't remember doing any strange formatting for the certs, so I guess the standard Amazon root CA should be a reference for the file format (https://docs.aws.amazon.com/iot/latest/developerguide/server-authentication.html and looks like PEM is ok). |
The Problem
I have configured MQTT with TLS however the connections fails without a useful error:
My server is configured correctly. TLS Connection with a simple Python script works:
Version
15.7.0
Logfile
Expected Behavior
No response
Screenshots
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: