Page 1 of 1

Error: Let's Encrypt validation status 400 on hostname or VestaCP hostname

Posted: Tue Feb 18, 2020 9:25 am
by castris
Hi.

I've installed a server with Ubuntu 18, nginx

When try update hostname domain with letsencrypt support get

Error: Let's Encrypt validation status 400

my.hostname.com resolve well to server.
Not cloudflare

If use certboot work fine but other issues with mail.

Any ideas?

Code: Select all

==> /var/log/nginx/domains/my.hostname.com.log <==
66.133.109.36 - - [18/Feb/2020:10:21:51 +0100] "GET /.well-known/acme-challenge/CwXH0i0uoQK-z4qHzzxxLL1vc83h1ivU6XK347IphXg HTTP/1.1" 404 732 "-" "Mozilla/5.0 (compatible; Let's Encrypt validation server; +https://www.letsencrypt.org)"

==> /var/log/nginx/domains/my.hostname.com.error.log <==
2020/02/18 10:21:51 [error] 4228#4228: *7322 open() "/home/admin/web/my.hostname.com/public_html/.well-known/acme-challenge/CwXH0i0uoQK-z4qHzzxxLL1vc83h1ivU6XK347IphXg" failed (2: No such file or directory), client: 34.222.229.130, server: my.hostname.com, request: "GET /.well-known/acme-challenge/CwXH0i0uoQK-z4qHzzxxLL1vc83h1ivU6XK347IphXg HTTP/1.1", host: "my.hostname.com"

==> /var/log/nginx/domains/my.hostname.com.log <==
34.222.229.130 - - [18/Feb/2020:10:21:51 +0100] "GET /.well-known/acme-challenge/CwXH0i0uoQK-z4qHzzxxLL1vc83h1ivU6XK347IphXg HTTP/1.1" 404 732 "-" "Mozilla/5.0 (compatible; Let's Encrypt validation server; +https://www.letsencrypt.org)"

Re: Error: Let's Encrypt validation status 400 on hostname or VestaCP hostname

Posted: Sat May 02, 2020 3:06 pm
by SPEC1AL1ST
same error. vestacp dying?

Re: Error: Let's Encrypt validation status 400 on hostname or VestaCP hostname

Posted: Thu Jun 04, 2020 1:30 pm
by SdeSergi
Same error here, on clean server with Ubuntu 18:04.4 and Vesta CP (Apache + nginx)

Re: Error: Let's Encrypt validation status 400 on hostname or VestaCP hostname

Posted: Thu Jun 04, 2020 2:18 pm
by SdeSergi
SdeSergi wrote:
Thu Jun 04, 2020 1:30 pm
Same error here, on clean server with Ubuntu 18:04.4 and Vesta CP (Apache + nginx)
solved by waiting a couple of hours