Error: Let's Encrypt validation status 400

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:
separs.ampr.org
I ran this command:
Via Vestacp clicked on ssl support and Letsencrypt
It produced this output:
Error: Let’s Encrypt validation status 400
My web server is (include version):
apache2
2.4.25 (debian)
The operating system my web server runs on is (include version):
Debian 9
My hosting provider, if applicable, is:

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):
yes VESTACP
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot): no

I had letsencrypt and separs.ampr.org on another machine and I had to move it. I moved the certificates, and got the error. So I removed the certificates hoping I could start from scratch. No luck

Hi @separs

Vestacp is a closed world. Checking your config there is the typical Vestacp-result ( https://check-your-website.server-daten.de/?q=separs.ampr.org ):

Domainname Http-Status redirect Sec. G
http://separs.ampr.org/
44.135.179.28 200 1.427 H
https://separs.ampr.org/
44.135.179.28 -2 1.673 V
ConnectFailure - Unable to connect to the remote server No connection could be made because the target machine actively refused it 44.135.179.28:443
http://separs.ampr.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
44.135.179.28 200 0.453
Visible Content: check-your-website-dot-server-daten-dot-de.JQLt74goodVDq4o54MVdcxy3HBdY3Jp9hMlc8sEVb3g

Checking a file in /.well-known/acme-challenge/random-filename the content is:

random-filename . hash value of the public key of your Letsencrypt account

That's the result Letsencrypt expected.

But if Vestacp doesn't work, you should ask your hoster. Perhaps your installation is buggy or a Vestacp-update is required.

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