-
Notifications
You must be signed in to change notification settings - Fork 0
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 option #1
Comments
Release v1.1 is available supporting the MQTT_USETLS option. |
Hi Peer, |
Since I'm only a stupid docker user (and have no real idea how you did the magic) I can't provide new files 😁. I only used the TLS-Version, because without it, node-red did not connect... since all other eight clients in my network work with and without encryption, I guess there might be something with the node-red thingy. Since I use Letsencrypt certificates, simply enabling TLS is sufficient. For self-signed certificates there would be more work to do. But keep it as simple as it is. Adding Thanks for your great tool |
Hi Thomas, Personally, I'm using a LetsEncrypt certificate. Checking the certificate chain of "official" CAs is implemented in the OS, therefore no additional infos are needed then. I checked the flow. |
Hey Tom,
great work! Simple and powerful. I like it, especially the easy docker deployment.
Could you maybe add the TLS option for your next release?
Corresponding flow value is "usetls", which is per default "false".
If the config-File option "MQTT_USETLS" could be set to "true", it should also work with replacements in prepare.sh.
Thanks!
P.S.: had a hard time with mosquitto and unencrypted connection. Maybe error was on me, or something between node-red and mosquitto. But as soon as I manually enabled TLS, it worked like a charm.
The text was updated successfully, but these errors were encountered: