Some challenges have failed

I used this repo to create nginx reverse proxy and request ssl before.
But I don't know why recently I has. ACME error althought every setup in domain, router (port forward 80/443) are corrected.
Please help me or suggest me something.
Thanks!
Repo:

Creating dummy certificate for sd.lamkhatinh.com ...

Generating a RSA private key
.............++++
...........................++++
writing new private key to '/etc/letsencrypt/live/sd.lamkhatinh.com/privkey.pem'

Starting nginx ...

[+] Running 0/0
⠋ Container a7d7feeb3ef8_nginx-certbot-nginx-1 Recreate 0.0s
Error response from daemon: Conflict. The container name "/a7d7feeb3ef8_nginx-certbot-nginx-1" is already in use by container "a7d7feeb3ef8c824470c6a40a5c0b3eea2dc6a162689a0ac6ff0fb2cdb1c4fb4". You have to remove (or rename) that container to be able to reuse that name.

Deleting dummy certificate for sd.lamkhatinh.com ...

Requesting Let's Encrypt certificate for sd.lamkhatinh.com ...

Saving debug log to /var/log/letsencrypt/letsencrypt.log
Requesting a certificate for sd.lamkhatinh.com

Certbot failed to authenticate some domains (authenticator: webroot). The Certificate Authority reported these problems:
Domain: sd.lamkhatinh.com
Type: connection
Detail: 116.109.1.156: Fetching http://sd.lamkhatinh.com/.well-known/acme-challenge/F0EiM_FWGhFSZcfmvhXMXCWoVhx5WSsNWokRhxSKRZY: Connection refused

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

Some challenges have failed.

Is that normal? If not you should post an issue on the github for that script

As for this error, it means the Let's Encrypt server sent the HTTP challenge (port 80) to your domain but the connection was refused. Most likely because there is no host or container handling port 80 properly.

It seems you are changing things frequently which makes it hard to say anything else. One minute a test HTTP request gets redirected to HTTPS. The next minute it fails with "no route to host". HTTPS requests are using a self-signed cert for "localhost".

This seems like a server / container configuration problem which is best handled by the group that manages that script.

3 Likes

This looks like the obvious culprit here.

2 Likes

Sorry, I just remove container and re-run the script.

Starting nginx ...

[+] Running 1/1
:heavy_check_mark: Container nginx-certbot-nginx-1 Started 0.1s

Deleting dummy certificate for drive.lamkhatinh.com ...

Requesting Let's Encrypt certificate for drive.lamkhatinh.com ...

Saving debug log to /var/log/letsencrypt/letsencrypt.log
Requesting a certificate for drive.lamkhatinh.com

Certbot failed to authenticate some domains (authenticator: webroot). The Certificate Authority reported these problems:
Domain: drive.lamkhatinh.com
Type: connection
Detail: 116.109.24.84: Fetching http://drive.lamkhatinh.com/.well-known/acme-challenge/m6VxWjsxxAUT7KMigR3YF1MHbhzf3gmYoBvdhZQVkFs: Connection refused

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

Some challenges have failed.

I realize in docker-compose file. I have command
./data/certbot/www:/var/www/certbot

But I checked in ./data/certbot/www, no file to ACME use, is it normal ?
Or may be I miss something, please help me1

Really thanks for your support.

1 Like

Is that the correct IP?
Why are the ACME HTTP requests being refused?

2 Likes

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