Error: Let's Encrypt validation status 400

[davidgreams]

Very excited about this! I am on 0.2.5 and appears to have successfully registered a v2 account key. Cert is setup to the v2 account key, is a wildcard, but everytime I hit issue it says (see below). Using Google domains, I have deleted the old challenge TXT and re-added it as specified, but it continues to fail each time. Traditionally it has worked within just a few seconds of the change on Google Domains. I'll try again later but so far no luck :(

• Please add the TXT records to the domains, and retry again.
  Please check log file for more details: /tmp/acme/LE-ACME2-DOMAIN-Wildcard1/acme_issuecert.log

[rogeriotaques]

Faced the same problem today, after several attempts and two reinstalls I've fixed this error by disabling two options for my domain on CloudFlare account: "force HTTPS" and "fix HTTP" (later I've tested this steps for two other domains - all the same things). Maybe this will help someone.

The only way I managed to fix the issue was following those steps.

Additionally, if you have multiple domains (such as me) parked alongside your main domain (and also configured using Cloudflare), all the domains settings from Cloudflare should be not forcing the HTTPS and fixing the HTTP. Otherwise, it might fail.

[SanTi]

I can't add alias with ssl to domain. Sometimes ı get the same error without alias. You get 400 error but if you write this command

Code: Select all

v-list-web-domain-ssl user domain.com

to ssh terminal you will probably see ssl codes. Now you can copy and paste it on vestapanel interface by manuel. it works for me. Also I suggest you that dont create domain with ssl in beginning. You can add ssl after you add domain 5 minutes.

[adrijanx]

I faced this issue today and found the solution which was working for me.


Debian, Ubuntu & CentOs:

Code: Select all

$ wget https://dl.eff.org/certbot-auto
$ sudo mv certbot-auto /usr/local/bin/certbot-auto
$ sudo chown root /usr/local/bin/certbot-auto
$ sudo chmod 0755 /usr/local/bin/certbot-auto

[Danielru]

Ubuntu 18.04 - Both of the above methods do not work.

[nextgi]

Well, seems a bit odd. I am receiving the same issue as described by OP on a fresh install of VestaCP, today. Here is what LetsEncrypt is returning

Code: Select all

{
  "type": "urn:ietf:params:acme:error:malformed",
  "detail": "Unable to update challenge :: authorization must be pending",
  "status": 400
}

I am trying to debug `v-add-letsencrypt-domain` but there isn't clear documentation in the script.

[GoodZon]

Was the same problem. I have Error: Let's Encrypt validation status 400. Problem was that vesta when you create domain, by default put some alias like www.some-domain.com If this alias isn`t in DNS records, you will receive error 400 when try to activate Lets Encrypt Support SSL certificate.

[kenneth]

In case someone hasn't solved their issue with LE 400 status code, I managed to solve mine with this.

Code: Select all

wget https://raw.githubusercontent.com/serghey-rodin/vesta/master/bin/v-add-letsencrypt-domain -O $VESTA/bin/v-add-letsencrypt-domain
wget https://raw.githubusercontent.com/serghey-rodin/vesta/master/bin/v-add-letsencrypt-user 1 -O $VESTA/bin/v-add-letsencrypt-user
chmod +x $VESTA/bin/v-add-letsencrypt-domain
chmod +x $VESTA/bin/v-add-letsencrypt-user

Remember to backup files before modifying or replacing anything.

[youradds]

Same issue for me as well. Ubuntu 18.10. Moving domains across from another server. Domains already had LE set up on the old server, so to create a new one I added a new sub-domain. This URL works fine (what I'm seeing in the log files);

http://site.net/.well-known/acme-challe ... NelQPE6i1M

....and the log file looks ok as well:

2600:1f14:804:fd00:312d:4aad:dca:87f1 - - [12/Nov/2019:09:33:07 +0000] "GET /.well-known/acme-challenge/LMoEOieTpArq3vrDVYUrsBfQqHzBmHb49NelQPE6i1M HTTP/1.1" 404 735 "-" "Mozilla/5.0 (compatible; Let's Encrypt validation server; +https://www.letsencrypt.org)"

I'm not sure what else to try :/

[coolwebs]

What worked for me:

In Cloudflare > Crypto > SSL set to OFF & Always use HTTPS set to OFF
/usr/local/vesta/bin/v-add-letsencrypt-domain user domain > Success!
In Vesta CP > User > Rebuild Web
Wait 60 seconds.
Return CF settings to previous setting.

I just wanted to point out that I also found that this was the only solution that worked for me as I use CF to manage my DNS. An additional step I had to take was to disable the proxy settings and just use DNS settings (make orange cloud go grey in CF) whilst I ran the script in terminal.

Then turn the SSL back on in CF and also reactivate the proxies again and it worked fine for me. Such a relief!
However, tedious operating with many domain names I manage. Here's to the next three months...