-
-
Notifications
You must be signed in to change notification settings - Fork 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
Issuing wildcard certificates stopped working #3036
Comments
If this is a bug report, please upgrade to the latest code and try again: |
Quick fix for those who just need to renew their cert quickly:Insert a |
did you read this?
https://github.com/acmesh-official/acme.sh/wiki/dnsapi#74-use-ddnssde-api |
Of course. As I said, it used to work until somewhere around last month. Also, if the dns provider configuration was the problem, I don't think my "quick fix" would have worked... Edit: It also looks like #3013 is exactly the same issue, so I'm very sure this issue is independent of the DDNS provider used. |
@mod242 can you please take a look ? |
Hello, unfortunately I was away (without Internet) that's why I just had a look right now. Somehow my test-environment seems to behave differently here for ddnss.de. I get an "...is already verified, skip dns-01." for the second domain. Can you please confirm that you are still seeing this issue with ddnss.de wildcard domains? |
I have this issue with duckdns.org domains as well. |
Same problem here, but with Yandex DNS. Wildcard domain TXT entry overwrites normal domain TXT record:
When I looked up DNS entries manually, there was only the second one, obviously. Will temporarily try to fix by issuing two separate certificates, one for main domain and the other one for wildcard. |
As I mentioned in #2230 I think this is related to some change in LEs behaviour and not to the API-Implementation for the different providers. Your experience with Yandex seems to increase this impression. |
this bug is still there and has never been adressed, is anyone working on this? |
It seems that somewhere within the last 3 months Let's Encrypt started requiring a separate TXT record for the wildcard alt domain even if it's the same domain as the main domain.
This causes acme.sh's issuing procedure to fail, here's my
debug 2
log file as an example: https://pastebin.com/dJQMvvv8This is the same problem @kinslayer1982 described in #2230 (comment).
#3016 might also be a duplicate, but it's not including any relevant logs so I'm not sure...
So what happens is:
Idea how to fix:
$remaining_dns_entries
which is initially a copy of$dns_entries
txtdomain
in$remaining_dns_entries
, remove the entry and add the TXT record$remaining_dns_entries
$remaining_dns_entries
is emptyThe text was updated successfully, but these errors were encountered: