Certbot certificate creation error with nginx windows

[san1]

1: Enter a new webroot
2: D:\serverA\nginx\html

---

Select the appropriate number [1-2] then [enter] (press 'c' to cancel): 2

Certbot failed to authenticate some domains (authenticator: webroot). The Certificate Authority reported these problems:

Domain: adssmart.in
Type: connection
Detail: 117.248.104.119: Fetching http://adssmart.in/.well-known/acme-challenge/Cza4aegjb5QQdjZsnZuv3W1eqqO30d5A_SeI9o
Ewhq0: Connection reset by peer

Domain: www.adssmart.in
Type: connection
Detail: During secondary validation: 117.248.104.119: Fetching http://www.adssmart.in/.well-known/acme-challenge/ol1Nj
_1EhJotwUriqSxtaWzJL9XyUIJ49G_sM4n686Q: Connection reset by peer

Hint: The Certificate Authority failed to download the temporary challenge files created by Certbot. Ensure that the lis
ted domains serve their content from the provided --webroot-path/-w and that files created there can be downloaded from
the internet.

←[31mSome challenges have failed.←[0m
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile C:\Certbot\log\letsencrypt.lo
g or re-run Certbot with -v for more details.

[9peppe]

It looks like your firewall doesn't like the validation server. What firewalls are you using?

I noticed it's a secondary validation failure, check your IP blocklist for overbroad filters.

[san1]

@san1

ne

thank to repply
my server serve content over website of both address
Untitled-01|690x387
Untitled-02|690x387

[rg305]

Try placing a test text file in that folder: D:\serverA\nginx\html\.well-known\acme-challenge

Then see if it can be accessed from the Internet.
http://adssmart.in/.well-known/acme-challenge/[test-file-name]

[san1]

http://adssmart.in/.well-known/acme-challenge/demo-file.txt
here we upload demo test file
Screenshot_20231006-185049|250x500
Screenshot_20231006-185104|250x500

[MikeMcQ]

Thanks. That looks good.

Are you sure you do not have a firewall that is blocking certain IP addresses? Because I just tried a test with the Let's Encrypt staging system and got the expected 404 response on one of your domains but got the "reset by peer" on the other.

Also, who is your hosting service? Is it GoDaddy?

sudo certbot certonly --dry-run --webroot -w "D:\serverA\nginx\html" -d adssmart.in -d www.adssmart.in

Certbot failed to authenticate some domains (authenticator: webroot). The Certificate Authority reported these problems:
  Domain: adssmart.in
  Type:   connection
  Detail: 117.248.104.119: Fetching http://adssmart.in/.well-known/acme-challenge/6MwuZHnUTGO5sijB_9ZRp1FJi9czuLuTijmoiNQuZww: 
  Connection reset by peer

  Domain: www.adssmart.in
  Type:   unauthorized
  Detail: 117.248.104.119: Invalid response from http://www.adssmart.in/.well-known/acme-challenge/XFYmeWjxkYx7fD9gWVOwon7Ld8JyNbUJYsNwiCx4YpU: 
  404 (Not Found)

[san1]

@MikeMcQ

is

bro very very thanks for that
here secondary validation problem after removing www.adssmart.in
this will success.
once again thanks for help.

[MikeMcQ]

That does not fix the problem it was just helping to define better what was causing it. And, your www will not validate without a cert that includes its name.

The cert you got for just the adssmart.in name is not setup right in nginx. I think you are using the cert.pem file instead of fullchain.pem file in your nginx server block.

See the cert validation error at a site like this

https://decoder.link/sslchecker/adssmart.in/443