Error: Let's Encrypt validation status 400
Re: Error: Let's Encrypt validation status 400
New Server running CentOS 7
Fresh install of VestaCP
Same Issue
Fresh install of VestaCP
Same Issue
Re: Error: Let's Encrypt validation status 400
The aforementioned fix in v-add-letsencrypt-domain should address the issue. It has already been committed to the GitHub repo and will be included in the next release. Make sure you're on the latest version of VestaCP.
-
- Posts: 16
- Joined: Sun Oct 02, 2016 10:48 am
- Contact:
- Os: Ubuntu 15x
- Web: apache + nginx
Re: Error: Let's Encrypt validation status 400
moved to new server & same probleme.pepsi wrote: ↑Mon May 06, 2019 10:24 pmThe aforementioned fix in v-add-letsencrypt-domain should address the issue. It has already been committed to the GitHub repo and will be included in the next release. Make sure you're on the latest version of VestaCP.
ubuntu 16.04
Re: Error: Let's Encrypt validation status 400
I have same problem.
v-add-letsencrypt-domain file is right $domain and I did reinstallation.
The problem same
v-add-letsencrypt-domain file is right $domain and I did reinstallation.
The problem same
Re: Error: Let's Encrypt validation status 400
I also have this problem
Brand new CentOS 7 (x64) install & up2date, running in a VM.
- Tried yum reinstall vesta
- Confirmed my "v-add-letsencrypt-domain" file has proper $domain variable
- Confirmed iptables is allowing both TCP 80 and 443
- Confirmed my NAT firewall (pfSense) is allowing both TCP 80 and 443
A couple things I noticed that may or may not be relevant:
- It appears as if the ".well-known" isn't getting created. Not sure if this is normal behavior considering the "400" error.
- After messing with this for a while, I started getting the error "Let's Encrypt new auth status 429" which unfortunately is a rate limiting error. I should have used their sandbox environment for testing this, but I don't know how to configure that.
- There is no "certbot" script - is Vesta not using certbot?
I'd also love to get this sorted out, otherwise I'm going to have to abandon Vesta, as not being able to use Let's Encrypt is a showstopper for me.
Brand new CentOS 7 (x64) install & up2date, running in a VM.
- Tried yum reinstall vesta
- Confirmed my "v-add-letsencrypt-domain" file has proper $domain variable
- Confirmed iptables is allowing both TCP 80 and 443
- Confirmed my NAT firewall (pfSense) is allowing both TCP 80 and 443
A couple things I noticed that may or may not be relevant:
- It appears as if the ".well-known" isn't getting created. Not sure if this is normal behavior considering the "400" error.
- After messing with this for a while, I started getting the error "Let's Encrypt new auth status 429" which unfortunately is a rate limiting error. I should have used their sandbox environment for testing this, but I don't know how to configure that.
- There is no "certbot" script - is Vesta not using certbot?
I'd also love to get this sorted out, otherwise I'm going to have to abandon Vesta, as not being able to use Let's Encrypt is a showstopper for me.
Re: Error: Let's Encrypt validation status 400
I have exactly the same problem. Can not decide.vmSean wrote: ↑Fri May 10, 2019 10:28 pmI also have this problem
Brand new CentOS 7 (x64) install & up2date, running in a VM.
- Tried yum reinstall vesta
- Confirmed my "v-add-letsencrypt-domain" file has proper $domain variable
- Confirmed iptables is allowing both TCP 80 and 443
- Confirmed my NAT firewall (pfSense) is allowing both TCP 80 and 443
A couple things I noticed that may or may not be relevant:
- It appears as if the ".well-known" isn't getting created. Not sure if this is normal behavior considering the "400" error.
- After messing with this for a while, I started getting the error "Let's Encrypt new auth status 429" which unfortunately is a rate limiting error. I should have used their sandbox environment for testing this, but I don't know how to configure that.
- There is no "certbot" script - is Vesta not using certbot?
I'd also love to get this sorted out, otherwise I'm going to have to abandon Vesta, as not being able to use Let's Encrypt is a showstopper for me.
Did you succeed?
Re: Error: Let's Encrypt validation status 400
Nope. Had to abandon VestaCP.
-Sean
-Sean
Re: Error: Let's Encrypt validation status 400
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.