Error: Let's Encrypt validation status 400

[desolator]

Hey,

Am facing some similar issues. Am using vesta with nginx + php-fpm (Centos 7) and am adding the domain in vesta and when i try to generate the letsencrypt ssl it fails.
I removed the www alias and then it works - but it's really important the ssl to cover the www alias as well

Do you have any ideas why this might happen? All steps taken are from vesta interface panel

For DNS provider am using Stackpath so am not facing the Cloudflare crypto issues - a month ago i added a domain with www and it worked fine now it seems something is off with vesta or letsencrypt

Looking forward

[desolator]

Hey,

Am facing some similar issues. Am using vesta with nginx + php-fpm (Centos 7) and am adding the domain in vesta and when i try to generate the letsencrypt ssl it fails.
I removed the www alias and then it works - but it's really important the ssl to cover the www alias as well

Do you have any ideas why this might happen? All steps taken are from vesta interface panel

For DNS provider am using Stackpath so am not facing the Cloudflare crypto issues - a month ago i added a domain with www and it worked fine now it seems something is off with vesta or letsencrypt

Looking forward

FIXED - the issue was that i was using a cname for www, i switched to A record and worked like a charm

I hope this might help somebody

[Thoros69]

Had same problem. Wait 48 hours if you changed nameserver or IP in DNS.
Step 1.
Just delete 'yourdomain.se' in Vestacp. Look so DNS records also are gone.
Step 2.
Use FTP to erease all 'yourdomain.se' in /username/conf/web/ and /username/conf/dns/.
Step 3.
Add 'yourdomain.se' again with letsencrypt option filled. Wait up to 5 minutes.

Should be working for all.

Debian 9
VestaCP nginx + apache2
php-fpm 7.0 - 7.2 - 7.3

PS. I started with PLESK, stable, easier + DNSSEC
(In VestaCP it is not happend for decades....)
PLESK small cost VS VestaCP cost when you need to reinstall every week or month

[g0r60n]

Had same problem. Wait 48 hours if you changed nameserver or IP in DNS.
Step 1.
Just delete 'yourdomain.se' in Vestacp. Look so DNS records also are gone.
Step 2.
Use FTP to erease all 'yourdomain.se' in /username/conf/web/ and /username/conf/dns/.
Step 3.
Add 'yourdomain.se' again with letsencrypt option filled. Wait up to 5 minutes.

Should be working for all.

Debian 9
VestaCP nginx + apache2
php-fpm 7.0 - 7.2 - 7.3

PS. I started with PLESK, stable, easier + DNSSEC
(In VestaCP it is not happend for decades....)
PLESK small cost VS VestaCP cost when you need to reinstall every week or month

Thanks, but with me the problem still exists :(

[sysdop]

The domain must point to the server both via www and @ and also have the Cloudflare CDN off, if the domain does not resolve or has orange clouds in Cloudflare then you will not be able to generate it.

[saosangmo]

Hello,

I get the same error after migrating my site to new server with this method https://vestacp.com/docs/#how-to-migrat ... her-server.

Please help me.

[shahidirfan]

I am facing same issue. I applied all available options on the forum. But not solved the issue. I am using latest vestacp with ubuntu 18.04 nginx and apache with default confg.

Is there a new update in vestacp to fix the problem.

[sysdop]

The problem is fixed now, try update Vesta.

[peterbkk]

The domain must point to the server both via www and @ and also have the Cloudflare CDN off, if the domain does not resolve or has orange clouds in Cloudflare then you will not be able to generate it.

This did the trick for me. I had a subdomain, hosted on a different server from the main domain name. With SSL forced I got Error 400, when i removed the forced SSL (set in apache2.conf) I got the same error but no "400".

After adding the A record for www.sub to where the DNS is managed, it then worked and SSL cert was issued.


Thanks

[hsvesta]

If you are using CDN like Cloudflare, than choose 'DNS only' instead of using a proxy for your domain. This helped me solve this problem. You can try reinstalling Vesta but make sure to take a backup. Try using Vesta through the command line by logging into the root account of your server. The CDN problem solved it for me on one of my servers. On another server I had to reinstall Vesta and than tweak the CDN settings.