"Certbot failed to authenticate some domains "I can't authenticate letencrypt ssl in my nginx

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: medical.org

I ran this command: certbot --nginx

It produced this output: medical.org/.well-known/acme-challenge/w3eu74WgXk18T20gtNCdsG_xxBG2yWT5wYn9P_4b2nk: Connection reset by peer

My web server is (include version): Windows Server

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

My hosting provider, if applicable, is:

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):

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

2

You have a firewall or similar device blocking the first request from a specific IP. Let's Encrypt servers use a variety of IP addresses so they are being blocked.

Let me explain as I can reproduce this from my own test server. My first request from a fresh IP address to your domain failed with "reset by peer". A request right after succeeded. But, if I waited several minutes I again got a "reset by peer". This pattern repeats.

We have seen this before and I don't have a good suggestion. It is likely a problem with your ISP network routing or some firewall device.

You should consider using a DNS Challenge instead. Or, correct the network or firewall problem causing the "reset by peer".

Here is sample

# Works (I made a previous attempt which got "reset by peer")
date: Thu Feb  8 03:33:49 UTC 2024
curl -i http://medical.ssbmm.org
HTTP/1.1 200 OK
Server: nginx/1.18.0
Date: Thu, 08 Feb 2024 03:33:53 GMT
X-Powered-By: ASP.NET
(data omitted)

# Fails 8 minutes later
date: Thu Feb  8 03:41:52 UTC 2024
curl -i http://medical.ssbmm.org
curl: (56) Recv failure: Connection reset by peer

# Works right after
date: Thu Feb  8 03:41:59 UTC 2024
curl -i http://medical.ssbmm.org
HTTP/1.1 200 OK
Server: nginx/1.18.0
Date: Thu, 08 Feb 2024 03:42:01 GMT
3 Likes
3

Thanks for your reply, i will troubleshoot with my firewall device

2 Likes
5

Error have been solved , thanks for you repsonse.

firewall is block my nginx ssl.

3 Likes
6

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