Page 2 of 3

Re: Error: Let's Encrypt new auth status 400

Posted: Tue Feb 26, 2019 4:46 pm
by alexcy
I sincerely hope that you have better luck than me..

Re: Error: Let's Encrypt new auth status 400

Posted: Sun Mar 03, 2019 7:37 am
by plutocrat
imperio wrote:
Tue Feb 26, 2019 8:54 am
Lets Encrypt v2 already done, and will be in the next release 0.9.8-24.
I have a few domains SSL certs expiring soon. Is there a way to grab the relevant files from github if it starts getting urgent? And if there is, which files would we need to replace?

Re: Error: Let's Encrypt new auth status 400

Posted: Sun Mar 03, 2019 4:40 pm
by realjumy
alexcy wrote:
Tue Feb 26, 2019 4:46 pm
I sincerely hope that you have better luck than me..
I understand that they are very busy. And it's complicated when this is free and it's not something they make a living from, as they have to prioritise other stuff. The only thing that we can do is just try to help them in what we can, and be patient.

Re: Error: Let's Encrypt new auth status 400

Posted: Sat Apr 06, 2019 2:46 am
by dsystem
imperio wrote:
Tue Feb 26, 2019 9:13 am
IPv6 support not in demand
I love this panel and did not want to trade it.

Unfortunately it seems to have no demand at all!!! -> viewtopic.php?f=10&t=18446

Re: Error: Let's Encrypt new auth status 400

Posted: Tue May 07, 2019 9:06 am
by canoodle
Hello all,

update: i do do not know what the "400" is supposed to mean. but it definitely has something to do with a domain name, if you have multiple domain names, try to reduce the list to one domain, see if it works then.

i also really love vestacp - its simplicity is just great. (i do not need more features, yes ipv6 would be nice, but if what is there works and stays working and updated i am pretty happy already)

i am getting this error now too BUT ONLY ON ONE DOMAIN! (my main domain).

Let's Encrypt works on other domains!

Let's Encrypt worked pretty fine the last time i tested it, but now it throws that error.

backup your files and database concerning the domain that throws the 400 error and recreate it, maybe that helps?
(or a clean reinstall of vestacp)

this gives me hope.

basically can you not get around the ipv6 problem, by running it in a virtual machine or container and forward the traffic? (just an idea)

ps: https://caddyserver.com/ is a pretty cool proxy with massive forwarding capabilities.

yes another software - more complexity. i know not great but well.

Re: Error: Let's Encrypt new auth status 400

Posted: Thu May 09, 2019 2:46 am
by viraladmin
dsystem wrote:
Sat Apr 06, 2019 2:46 am
imperio wrote:
Tue Feb 26, 2019 9:13 am
IPv6 support not in demand
I love this panel and did not want to trade it.

Unfortunately it seems to have no demand at all!!! -> viewtopic.php?f=10&t=18446
Your a funny dude. You realize that this "high demand" you think is taking place... is all in your head correct?

IPv6 is over 7 years old and still only 13.9% of all websites (as of May 2019) hosted on the internet actually use ipv6? https://w3techs.com/technologies/detail ... v6/all/all

The IT people you seem to know, are NOT setting trends.

Re: Error: Let's Encrypt new auth status 400

Posted: Tue May 14, 2019 7:45 pm
by canoodle
argh!

seems to be similar problem: viewtopic.php?t=14817

had to reinstall anyway... and now i want to add a domain with special character: ö

and the evil "Error: Let's Encrypt new auth status 400" is back! WHAT DOES "status 400" actually mean?

Code: Select all

 Static hostname: webserver2.vm
         Icon name: computer-vm
  Operating System: CentOS Linux 7 (Core)
       CPE OS Name: cpe:/o:centos:centos:7
      Architecture: x86-64
files probably involved:

Code: Select all

/usr/local/vesta/bin/v-add-letsencrypt-domain
/usr/local/vesta/bin/v-add-cron-letsencrypt-job
/usr/local/vesta/bin/v-add-letsencrypt-user
/usr/local/vesta/bin/v-delete-letsencrypt-domain
/usr/local/vesta/bin/v-list-letsencrypt-user
/usr/local/vesta/bin/v-schedule-letsencrypt-domain
/usr/local/vesta/bin/v-update-letsencrypt-ssl

/usr/local/vesta/data/queue/letsencrypt.pipe
when do it "manual terminal mode":

how it is supposed to be called:

/usr/local/vesta/bin/v-add-letsencrypt-domain admin domain.com www.domain.com,www.alias1.com,www.alias2.com no

# Argument definition
user=$1
domain=$2
aliases=$3
$4=no is not processed!?

Code: Select all

Error: Let's Encrypt new auth status 400
modified line 122 to output the full $answer:

Code: Select all

check_result $E_CONNECT "Let's Encrypt new auth status $status"
-> check_result $E_CONNECT "Let's Encrypt new auth status $status $answer"
and the answer reads like:

Code: Select all

Error: Let's Encrypt new auth status 400 HTTP/1.1 100 Continue
Expires: Tue, 14 May 2019 20:26:33 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache

HTTP/1.1 400 Bad Request
Server: nginx
Content-Type: application/problem+json
Content-Length: 142
Boulder-Requester: 56757960
Link: <https://acme-v02.api.letsencrypt.org/directory>;rel="index"
Replay-Nonce: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Expires: Tue, 14 May 2019 20:26:34 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache
Date: Tue, 14 May 2019 20:26:34 GMT
Connection: close
{
  "type": "urn:ietf:params:acme:error:malformed",
  "detail": "Error creating new order :: Invalid character in DNS name",
  "status": 400
}
so there you have it: "Invalid character in DNS name"

will try to delete the special-character-domain.com and replace it with "escaped" version generated by: https://www.netim.com/domain-name/accented-domains.html

PS: Escpaed version of url does not work either.... so there is definitely something wrong with how VestaCP now handles let's encrypt requests with special chars (used to work before)

special chars could be: öäü

Re: Error: Let's Encrypt new auth status 400

Posted: Tue Jun 11, 2019 6:24 pm
by cvondra
Has anyone found a resolution to this?

Re: Error: Let's Encrypt new auth status 400

Posted: Sun Jul 21, 2019 2:34 pm
by canoodle
it's just a theory: (untested) Let's Encrypt problem with special chars in domain names happens (possibly) when vestacp installer is customized before installation to not include the DNS system.

guess the vestacp people do not have the time to test every combination.

did not decide to install the DNS system because less software the better the safer and so on.

but now i have this problem.

can anyone confirm this?

PS: If you need to move a wordpress installation (also between domain names) this is a very nice and free plugin: https://wordpress.org/plugins/duplicator/

Re: Error: Let's Encrypt new auth status 400

Posted: Tue Jul 23, 2019 5:47 am
by siavash82ir
imperio wrote:
Tue Feb 26, 2019 8:54 am
alexcy, we are working under new release, it's means that project is continue.
Lets Encrypt v2 already done, and will be in the next release 0.9.8-24, after that we have plans to implemented new feature multiple php, most of bugs also will be fixed

ثبت دامنه طراحی سایت
I have a few domains SSL certs expiring soon.
Is there a way to grab the relevant files from github if it starts getting urgent?
if there is, which files would we need to replace?