-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
External network access Let's Encrypt certificate not applied until reboot #3512
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Anyone? |
I encountered the same issue recently. I'm also running Home Assistant OS, in my case on Yellow hardware. I wonder if this is potentially an issue with certificate handling in Home Assistant OS or the frontend application, and if so, would opening an issue there would get more eyes on it? (I didn't look closely enough at the issue before I rebooted to fix it.) |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Describe the issue you are experiencing
When using external network access with a TLS certificate provided by the Let's Encrypt add-on, renewed certificate doesn't get applied until after reboot.
Restarting Home Assistant isn't enough.
What type of installation are you running?
Home Assistant OS
Which operating system are you running on?
Home Assistant Operating System
Which add-on are you reporting an issue with?
Let's Encrypt
What is the version of the add-on?
5.0.15
Steps to reproduce the issue
System Health information
System Information
Home Assistant Community Store
Home Assistant Cloud
Home Assistant Supervisor
Dashboards
Recorder
Spotify
Anything in the Supervisor logs that might be useful for us?
No response
Anything in the add-on logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: