Hello, I have a certificate for the domain bvergnaud.fr that I initially generated by hand, interactively, with certbot. I’m trying to renew it now using DNS challenges, so that I can automate the renewal. My domain is hosted by OVH. In case it is relevant, DNSSEC and ANYCAST are enabled for this…

[image] kRYOoX: -d *.bvergnaud.fr This requires quotes: -d "*.bvergnaud.fr"

Indeed, good catch. It doesn’t fix the problem, however.

Sorry, I should have been clearer. The problem remains exactly as is. No change.

What version of certbot are you running?

From my time working with Lexicon, the error to me indicates that the domain can’t be found in your OVH account’s DNS zones. My other theory is that Lexicon is mishandling the wildcard. Can you tell me, if you run Certbot with --staging and without the *. wildcard, does it succeed?

@rg305 certbot 0.27.1. @_az Looks like it’s no better: root@eae8e4993084:/$ certbot certonly --renew-by-default --staging --dns-ovh --dns-ovh-credentials /config/dns-conf/ovh.ini --manual-public-ip-logging-ok --rsa-key-size 4096 -m "me@kry.wtf" --no-eff-email --agree-tos -d "bvergnaud.fr" Saving …

[image] kRYOoX: As for it not finding the domain in my account, I assume it could be from invalid credentials in my ovh.ini file ? I don’t think I made a mistake there but I’ll triple check just to be safe :slight_smile: I think that the error would be different if the credentials were wrong. …

I get the following: { "errorCode": "NOT_GRANTED_CALL", "httpCode": "403 Forbidden", "message": "This call has not been granted" } Which, I presume, is why Lexicon is unhappy. Here are the rules available for those credentials: [ { method: "GET" path: "/domain/zon…

I just passed * as the path in the token creation interface for that script with a short validity. We only want to determine whether your account actually contains that domain. Edit: But I guess you can also alter the script to use /zone/ instead of /zone which should match your rules.

DNS challenge failing

Help

rg305 November 8, 2018, 10:39pm 4

Did it “change” the problem?

Topic		Replies	Views
Duckdns Unable to determine zone identifier for {0} using zone names: {1} Help	1	108	November 8, 2024
Error DNS problem: NXDOMAIN looking up TXT - Plugin dns-ovh Help	6	1665	March 18, 2019
Renewal failed: DNS challenges fail (No TXT record found) Help	2	1099	March 24, 2021
Certbot with certbot-dns-ovh fails to identify subdomain zone Help	1	1091	October 8, 2023
Dns-ovh renew : Zone xxxx is not deployed error Help	8	18596	November 18, 2023

DNS challenge failing

Related topics