You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On multiple Home Assistant installs (both fresh installs and updates from older versions) I have run into an issue when setting up the ssl_peer_certificate in the configuration.yaml of Home Assistant.
When this value is set, it seems that the other containers managed by supervisor are no longer able to connect to the home assistant core container. (See error log). I can reproduce and fix the errors only by removing or adding above value to the configuration.yaml.
Steps to reproduce
Set up external reverse proxy (NGINX)
Port forward traffic to local home assistant
Create self-signed certificates using openssl package (debian) and place in /ssl/ folder
Add the following configuration to configuration.yaml:
I just ran into the exact same issue today. I wanted to make it so only my reverse proxy could talk directly to HA but I forgot all the addons go through supervisor to get to core via the supervisor/core API. Everything broke dramatically when I added this option and I had to reboot the host to revert the config change (HA kept saying it was busy when I tried to just reboot core).
Would be nice if there was a way to provide supervisor with a client certificate to use when talking to HA. Also a certificate authority to use for validating the certificate HA is presenting since it has to be self-signed with a local address like homeassistant. I assume supervisor is just not validating that certificate currently.
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Describe the issue
On multiple Home Assistant installs (both fresh installs and updates from older versions) I have run into an issue when setting up the ssl_peer_certificate in the configuration.yaml of Home Assistant.
When this value is set, it seems that the other containers managed by supervisor are no longer able to connect to the home assistant core container. (See error log). I can reproduce and fix the errors only by removing or adding above value to the configuration.yaml.
Steps to reproduce
Enviroment details
Supervisor logs
Supervisor logs
System Information
System Information
The text was updated successfully, but these errors were encountered: