Error reissuing certificate

Help
1

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is: ddbikes.es

I ran this command:

It produced this output:

My web server is (include version): OVH

The operating system my web server runs on is (include version):

My hosting provider, if applicable, is: OVH

I can login to a root shell on my machine (yes or no, or I don't know):

I'm using a control panel to manage my site (no, or provide the name and version of the control panel): Plesk Obsidian 18.0.67

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):

When reissuing a certificate, the following error is thrown:

"Invalid response from https://acme-v02.api.letsencrypt.org/acme/authz/2292236936/495686834416.
Details:
Type: urn:ietf:params:acme:error:unauthorized
Status: 403
Detail: Incorrect TXT record "-jiNHbVzkBJhWNH4hiwvpZVZEGYiMqKyRXpBaU3mnhw" found at _acme-challenge.ddbikes.es"

the txt record in the DNS is "AyFFt-dDyxXt6P9IGyVYhSNBUXWtAc0FlYS-WRHBEtk" in my server.

We just redirected the domain from one server to another. Could it be that a certificate is active on the old server?

2

You have incorrect TXT record:

dig -t txt _acme-challenge.ddbikes.es

; <<>> DiG 9.18.33-1~deb12u2-Debian <<>> -t txt _acme-challenge.ddbikes.es
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41531
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;_acme-challenge.ddbikes.es.    IN      TXT

;; ANSWER SECTION:
_acme-challenge.ddbikes.es. 3600 IN     TXT     "-jiNHbVzkBJhWNH4hiwvpZVZEGYiMqKyRXpBaU3mnhw"

;; Query time: 52 msec
;; SERVER: 213.186.33.99#53(213.186.33.99) (UDP)
;; WHEN: Wed Mar 26 11:00:45 UTC 2025
;; MSG SIZE  rcvd: 111

As you can see it is -jiNHbVzkBJhWNH4hiwvpZVZEGYiMqKyRXpBaU3mnhw, but you seems need to update to AyFFt-dDyxXt6P9IGyVYhSNBUXWtAc0FlYS-WRHBEtk

3

No; Let's Encrypt doesn't care about other certificates. But the discrepancy between the DNS record you see and the DNS record Let's Encrypt sees suggests that you may not have updated the NS records for your domain to point to (new or changed, perhaps?) DNS servers. Currently, authoritative DNS for your domain is from ui-dns.com (and .org, .biz, and .de).

3 Likes
4

thanks,
So I understand that the domain redirection isn't done correctly, right? I need to be clear about this so I can file a claim with its owners.

Carlos

5

Thanks. My problem is that I don't know how to update it.

Carlos

6

I don't know what all "domain redirection" is supposed to entail, so I can't really say whether it was done "correctly" or not. But your results strongly indicate that the DNS server your ACME client is updating, and the DNS server you're checking, aren't the same. So if the "domain redirection" was supposed to update your DNS servers, perhaps that wasn't done.

5 Likes
7

Yeah I'd guess that your DNS is closely linked to your Osidian control panel (perhaps managed by it?) and your old server is still your nameserver (or vice versa).

For info, you are using DNS based domain validation to get your certs (causing the DNS check), rather than HTTP domain validation (which checks your web server before issuing a certificate).

2 Likes
8

Thank you very much. If you can confirm that I should validate via http, how should I do it please? I'm a developer, but not an administrator.

very grateful for your help

Carlos

9

I would personally figure out what's wrong with your DNS records first, get access to the actual account where they're configured, and fix that part. Not sure if HTTP validation would be easier for you—or if you should even try it—if you can't get the DNS records sorted out.

1 Like