Certbot failed to authenticate some domains

i've made it 100 times but now i get 404 on .well-known/acme-challenge.
please help me

(base) lev@MacBook-Pro-Lev speedcheck % curl -Ii4 lev-4-ek.online

HTTP/1.1 200 OK
Server: nginx/1.24.0 (Ubuntu)
Date: Mon, 05 Aug 2024 19:36:39 GMT
Content-Type: text/html
Content-Length: 1131
Last-Modified: Mon, 05 Aug 2024 18:39:53 GMT
Connection: keep-alive
ETag: "66b11c79-46b"
Accept-Ranges: bytes

(base) lev@MacBook-Pro-Lev speedcheck % curl -Ii6 lev-4-ek.online
HTTP/1.1 200 OK
Server: nginx/1.24.0 (Ubuntu)
Date: Mon, 05 Aug 2024 19:36:45 GMT
Content-Type: text/html
Content-Length: 1131
Last-Modified: Mon, 05 Aug 2024 18:39:53 GMT
Connection: keep-alive
ETag: "66b11c79-46b"
Accept-Ranges: bytes

My domain is: lev-4-ek.ru and lev-4-ek.online

I ran this command: certbot --nginx -d www.lev-4-ek.online -d lev-4-ek.online

It produced this output:

Certbot failed to authenticate some domains (authenticator: nginx). The Certificate Authority reported these problems:
Domain: lev-4-ek.online
Type: connection
Detail: 91.122.105.95: Fetching http://lev-4-ek.online/.well-known/acme-challenge/0vE_N-qQSpibsueke4l_qYIP-T2vLT_Kqefc5c08BNY: Timeout during connect (likely firewall problem)

Domain: www.lev-4-ek.online
Type: connection
Detail: 91.122.105.95: Fetching http://www.lev-4-ek.online/.well-known/acme-challenge/etRXFZ684gF5-gaqxGvL5_0byfvjEJFLz_yFXbnk8wI: Timeout during connect (likely firewall problem)

My web server is (include version): nginx version: nginx/1.24.0 (Ubuntu)

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

My hosting provider, if applicable, is: myself

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

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

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

Hi @lev4ek0, and welcome to the LE community forum :slight_smile:

You need to try that from the other side of the firewall [from the Internet].

4 Likes

Welcome @lev4ek0

Are those curl from your local network? Because I never see a successful test from the public internet. The Let's Debug server can't see you, Let's Encrypt itself times out, and I timeout with both HTTP and HTTPS from my own test server.

3 Likes

thanks a lot)) i'm sorry. checked from dns DNS Checker - DNS Check Propagation Tool and thought its working

1 Like

im i same network, thats why it was ok, sorry

2 Likes

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.