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. |, so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain

I ran this command: Trying to add Let's Encrypt Certificate

It produced this output:Let's Encrypt Validation Status 400

My web server is (include version): Apache 2.4.57

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

My hosting provider, if applicable, is:N/A

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

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

This domain has been running without issues for months and then today suddenly all browsers start throwing errors about the certificate being expired and now unsecure. I've made absolutely no changes to anything that would affect DNS, IP address etc.

Your domain is showing as not secure because your Apache server is now using a self-signed cert. The cert you last got on Feb28 expired a couple hours ago. Usually Apache will just continue to use the expired cert and that's the message people see. But, for some reason your Apache started using this self-signed cert.

If you didn't make any changes you may need to ask the myVesta support what can cause that.

Certs should be setup to auto-renew with 30 days before expiration. Your Feb28 cert should have renewed around Apr28. Do you know how myVesta renews certificates?

Does the name "spinauctions" mean anything to you? Because that is the name on the self-signed cert. Someone has to make these manually. It is not related to Let's Encrypt.



Thanks Mike. yep I've learnt what needs to be done and all sorted now. Indeed it was control panel related.