Unable to obtain certificate

Help
1

[ANotWorking]

lets debug shows following error

mapp.factnet.co.in has an A (IPv4) record (117.232.109.61) but a request to this address over port 80 did not succeed. Your web server must have at least one working IPv4 or IPv6 address.

My domain is: mapp.factnet.co.in

I ran this command: sudo certbot --nginx

My web server is (include version): nginx

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

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

but port 80 is opend for this site can be accessed with browser

2 
❯ curl -IL mapp.factnet.co.in
HTTP/1.1 200 OK
Server: nginx
Date: Fri, 06 Sep 2024 06:13:49 GMT
Content-Type: text/html
Content-Length: 7746
Last-Modified: Wed, 04 Sep 2024 14:33:34 GMT
Connection: keep-alive
ETag: "66d86fbe-1e42"
Accept-Ranges: bytes


~
❯ curl -IL mapp.factnet.co.in/.well-known/acme-challenge/123
curl: (28) Failed to connect to mapp.factnet.co.in port 80 after 31847 ms: Couldn't connect to server

Some part of your system is filtering requests to that path. It could be some fortinet firewall blocking acme or some misconfigured web server. (Block everything starting with a dot?)

1 Like
3

That is not possible with this error. It fails already before a TCP connection can be made and thus the path has not been send to the webserver yet.

For me it was VERY slow to connect to the webserver. I think some connections might work by chance, some fail with a timeout.

Is the webserver running on a RPi Pico or something? (Which is a joke, I doubt nginx can work on a Pico..)

1 Like
4

Very weird indeed.

$ curl -IL mapp.factnet.co.in/.well-known/acme-challenge/123
HTTP/1.1 404 Not Found
Server: nginx
Date: Fri, 06 Sep 2024 06:39:48 GMT
Content-Type: text/html
Content-Length: 146
Connection: keep-alive
2 Likes