-
Notifications
You must be signed in to change notification settings - Fork 32
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
add TLS support #20
Comments
Interesting, I expose home-assistant and use node-red behind the firewall connecting to ha insecurely on the private network so I never thought of testing this ( assumed it'd work ). Sorry about that I'll take a look |
TLS works for me out of the box. I use a Let's Encrypt cert on my Home Assistant. Perhaps this is a CA root trust issue ? |
@adamcstephens Uhm, no I don't think so, my Home assistant has a Let's Encrypt cert as yours do. but this leads me to get the bigger picture. My Error could be something completely unrelated to HA being accessed via https. I'll have to do some tests in a separate environment to check my thesis but this could be the culprit:
I have this setting in my I'll check back when I've done proper tests. Thank you for taking the time to look into this. |
TLS also works out of the box for me. Node Red 0.17.5, Let's Encrypt cert on Home Assistant 0.61. |
Well it turns out that it was all my fault. It wasn't any setting that I had in this is easily reproducible by pointing to the ip address of an tls protected ha instance. I'm closing this. sorry for wasting your time. |
at the moment the node can't connect to a home assistant instance secured by TLS.
specifying the url as
https://hostname:8123
just throws a generic{error}
in Node-Red debug window.this is a
node-home-assistant
issue in fact. the version installed via NR built in palette uses axios as a client for http requests. (please advise if I have to open a separate issue)Unfortunately I can't figure out how to patch in https/tls support (axios supports it (axios/axios#12) but the documentation is not clear to me) otherwise I'd have directly sent a PR, sorry.
The text was updated successfully, but these errors were encountered: