-
-
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
Lets Encrypt: Namecheap unable to determine zone identifier #3927
Comments
This looks the same, like I have seen from other dns plugins from the certbot version 2 area. Looking at the source of the namecheap plugin, it seams to share the same lack of maintainence like mijn-host and websupport. Could you please open an issue in the namecheap plugin repo? |
I don't have much experience with github. I've tried searching but I'm not quite sure where/which repo I need to post the issue to. I'd be glad to do it but from what I've seen, there's nothing on the official certbot repo. Do you have some guidance? |
namecheap repo is here: https://github.com/knoxell/certbot-dns-namecheap/issues |
Thank you, I've got an issue open with them as well. |
Describe the issue you are experiencing
Hello,
I ran Lets Encrypt 3 months ago and it worked and it installed my certificate. I went to renew and I can't get it to work at all. All of my research seems to point towards and issue with certbot. I've verified my settings and everything looks correct. I've posted the error in the section below.
I also tried the latest dev version but it gives the same error.
DNS Provider: Namecheap
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?
Dev 5.3.1 and 5.2.12
Steps to reproduce the issue
System Health information
There are currently no repairs pending
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
No response
The text was updated successfully, but these errors were encountered: