-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
LetsEncrypt fails with internal ACME server and private CA #3170
Labels
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. |
I just had this exact same problem. Turns out yaml replaces newlines with spaces, when using acme_root_ca_cert: |
-----BEGIN CERTIFICATE-----
MIIBkDCCATagAwIBAgIRA...euuzpq9I=
-----END CERTIFICATE----- The GUI configuration of this addon generates |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the issue you are experiencing
I am unable to get the LetsEncrypt addon to connect to an internal ACME server running with Step-CA due to SSL validation errors. No matter the value that is provided in the configuration to trust the ACME root CA, SSL validation fails. with the following error:
If this is a certbot error, I don't have the same behavior on any other certbot install used in my environment, they all work correctly besides Home Assistant.
This still occurs even after manually adding the private root CA to the Linux trust store and the certifi trust store.
My configuration is as follows (with sensitive values replaced):
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?
4.12.9
Steps to reproduce the issue
...
System Health information
System Information
Home Assistant Cloud
Home Assistant Supervisor
Dashboards
Recorder
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?
Additional information
No response
The text was updated successfully, but these errors were encountered: