Replies: 2 comments 2 replies
-
each OS/Platform has different TLS stack, can you provide more details? And I would not disable all certification checks, instead control which ones you need with your MqttSettings (btw, do you have the source available?) |
Beta Was this translation helpful? Give feedback.
2 replies
-
I'm still experiencing this issue and would appreciate any advice on how to resolve this. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm testing 3 scenarios,1 with an lets encrypt server certificate (8886), 1 with an expired server certificate (8887) and the other with a proper one (8883).
If I run the test with either the expired server certificate or lets encrypt first, the proper one will fail will this error
The remote certificate was rejected by the provided RemoteCertificateValidationCallback.
But if I run them separately it won't fail. What could be the issue? I am already creating a new client for each test:
I'm using the
test.mosquitto.org
servers:8883 : MQTT, encrypted, unauthenticated
8886 : MQTT, encrypted, unauthenticated
8887 : MQTT, encrypted, server certificate deliberately expired
this is my code for building the TLS options:
When I log the certificate validation errors, the same errors appear for 8887 (expired cert) and 8883 (valid cert)
For 8884
For 8883
Beta Was this translation helpful? Give feedback.
All reactions