Failed to authenticate

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. https://crt.sh/?q=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: n8nofad.online

I ran this command:
It produced this output:

sudo certbot --nginx -d n8nofad.online
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Requesting a certificate for n8nofad.online

Certbot failed to authenticate some domains (authenticator: nginx). The Certificate Authority reported these problems:
Domain: n8nofad.online
Type: unauthorized
Detail: 84.32.84.32: Invalid response from http://n8nofad.online/.well-known/acme-challenge/_fIhPyZm-gJyERYoqNLvylOjmHfT2NSk6yzIpv91jAc: 500

My web server is (include version):

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

My hosting provider, if applicable, is: hostinger

I can login to a root shell on my machine (yes or no, or I don't know): i dont 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):

1 Like

Welcome @iamapsproper

I think the IP address in your DNS is probably wrong. There is a server identifying as hcdn replying to your domain. That is a Hostinger service. And, it replies to HTTP requests with an HTTP status 500 (Server Error).

That IP should be the public IP for your nginx server so that is the first thing to check.

A test request to your domain sees (note the Server= from the response header):

Request to: n8nofad.online/84.32.84.32, Result: [Address=84.32.84.32,Address Type=IPv4,Server=hcdn,HTTP Status=500

The https://letsdebug.net test site is helpful when setting up new systems. It shows this same problem.

5 Likes