SSL config does not work with wildcard certificate #1545
Unanswered
smartathome
asked this question in
Q&A
Replies: 1 comment 1 reply
-
If the broker url starts with 'mqtts://' the ca and cert key fields will show up |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I have a MQTT broker setup to work on 1883 and 8883 with a wildcard certificate. But from within the UI, when ever I change the port from 1883 to 8883, my MQTT stops working.
I did some testing within the docker container and installed the MQTT clients. I managed to publish a message successfully but have to specify the cafile option, just having the capath does not work. I also did have to copy paste the root certificate (GlobalSign) into the ca-certificates.crt file, as just copying the original .crt root certificate into the directory and specifying the capath does not work.
Is there a way I need to specify the cafile option in the UI? The logs show the following whenever I switch on SSL:
Beta Was this translation helpful? Give feedback.
All reactions