-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
DNS challenge fails with SERVFAIL on Lets Encrypt #3809
Comments
I have the exact same issue and can’t figure it out. |
Same for me. |
I switched to use https://github.com/Djelibeybi/homeassistant-acme.sh-addon and this one works one, so I deleted the lets encrypt one as my cert expired yesterday. |
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 believe this is because Porkbun recently changed the URL for their API: If so, this can be fixed by updating the addon to use the new version 0.9.1 of certbot-dns-porkbun This pull request will fix the porkbun api issue: |
Describe the issue you are experiencing
Sometime in the last three months Lets Encrypt is no longer able to communicate to DNS properly
The canonical DNS servers for my network are internal (and my router forces all DNS requests for outbound services to them). However. the acme.sh program is capable of running DNS TLS certificate issues (which it does on all my other services).
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.2.3
Steps to reproduce the issue
...
System Health information
System Information
Home Assistant Community Store
AccuWeather
Home Assistant Cloud
Home Assistant Supervisor
Dashboards
Recorder
Anything in the Supervisor logs that might be useful for us?
Anything in the add-on logs that might be useful for us?
Additional information
This obviously worked at some point in the past as I have had a valid DNS challenge issued TLS certificate for over a year. No changes have been made to my local networking in that time (and acme.sh was able to renew other certs this AM using DNS)
The text was updated successfully, but these errors were encountered: