Certbot failed to authenticate some domains (authenticator: standalone). The Certificate Authority reported these problems: Domain: erpn.webeaz.com Type: connection Detail: 13.202.221.157: Fetching http://erpn.webeaz.com/.well-known/acme-challenge

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:erpn.webeaz.com

I ran this command:sudo bench setup lets-encrypt erpn.webeaz.com

It produced this output:

My web server is (include version):

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

My hosting provider, if applicable, is:

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

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

2

Your website is not accessible via HTTP (tcp port 80) from around the world, this is required to use the HTTP domain validation to prove you control the domain. Fix that and it will all work!

2 Likes
3

What directions are you following for that?

Because google links to this page which has some awful advice. One it is using certbot-auto which was obsoleted a long time ago. And, it has you scheduling a renewal on only one day a month. The recommendation is at least once per day.

Using Let's Encrypt to setup HTTPS.

I see HTTP (port 80) now reach an nginx server but I don't see that you got a cert yet. Do you still need help?

3 Likes
4

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