Cert failure when running certbot

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: n2ajo.info

I ran this command: certbot --nginx

It produced this output:
Certbot failed to authenticate some domains (authenticator: nginx). The Certificate Authority reported these problems:
Domain: n2ajo.info
Type: unauthorized
Detail: 76.223.105.230: Invalid response from https://n2ajo.info/.well-known/acme-challenge/9eKjcjObmM__PEc1czbAOFDqVDWLrNrmvBZdzdM4xQU: 404

Hint: The Certificate Authority failed to verify the temporary nginx configuration changes made by Certbot. Ensure the listed domains point to this nginx server and that it is accessible from the internet.

Some challenges have failed.
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.

My web server is (include version): wordpress 6.7

The operating system my web server runs on is (include version): Operating System: Debian GNU/Linux 12 (bookworm)
Kernel: Linux 6.6.74+rpt-rpi-v8

My hosting provider, if applicable, is: godaddy

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

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

2

That's not a web server, but a web application which runs on a web server.

Also, there's no website visible on your hostname. Only some kind of "parking lander" page which doesn't show anything in my webbrowser (visible parts probably blocked by my privacy plugins). And this parking page is actually HTTPS secured by a GoDaddy certificate.

Please make sure you have a working website before attempting to get a certificate.

1 Like
3

You must have enabled GoDaddy Domain Forwarding after your first post. Because your DNS records now point to their parking page.

Your DNS A record must be the public IP address for your server. In the first post you show an IP address that belongs to Amazon AWS. How is AWS related to this?

Removing Domain Forwarding is well explained here: I got This error - #6 by Geno11x11

Requests to your domain now show this page:

image
image1701×1218 146 KB

1 Like