search

outroll / vesta

VESTA Control Panel
http://vestacp.com
GNU General Public License v3.0
2.95k stars 1.03k forks source link

Let's Encrypt Error 400 #1908

Open aleksandarstojkovski opened 5 years ago

aleksandarstojkovski commented 5 years ago

Operating System (OS/VERSION):

Centos 7

VestaCP Version:

0.9.8-24 (latest version as of today)

Installed Software (what you got with the installer):

bash vst-install.sh --nginx yes --phpfpm yes --apache no --named yes --remi yes --vsftpd yes --proftpd no --iptables yes --fail2ban yes --quota yes --exim yes --dovecot yes --spamassassin yes --clamav yes --softaculous yes --mysql yes --postgresql no

Steps to Reproduce:

After installation: Login with admin user -> Web -> Edit -> SSL Support -> Let's Encrypt Support -> Save

Related Issues/Forum Threads:

//

Other Notes:

Fresh installation

mikhailnov commented 5 years ago

+1. Existing certificates failed to renew because of this.

mikhailnov commented 5 years ago 

  "type": "urn:ietf:params:acme:error:rejectedIdentifier",
  "detail": "Error creating new order :: Invalid character in DNS name",
  "status": 400
++ grep HTTP/1.1
}'```

It is with an IDN domain written in cyrillic letters.
mikhailnov commented 5 years ago

For me it was fixed in https://github.com/serghey-rodin/vesta/pull/1867 To apply this fix:

wget https://github.com/serghey-rodin/vesta/raw/master/bin/v-add-letsencrypt-domain -O /usr/local/vesta/bin/v-add-letsencrypt-domain

chmod +x /usr/local/vesta/bin/v-add-letsencrypt-domain
edudele commented 5 years ago

Another affected. With a Debian 9 just installed, the same thing happens. I have tried the solution of mikhailnov ha , jumps the same error 400.

edudele commented 5 years ago

Goodnight, I found a solution in Debian 9, possibly for Centos 7 also work. After installation it does not set the path correctly in the folder: /usr/local/vesta/bin/ for the execution of all vestaCP commands. So run:

After the restart everything worked correctly.

I hope it is helpful for everyone.

mikhailnov commented 5 years ago

@edudele it is not needed, PATh is set by a script in /etc/profile.d/, exporting a variable in shell before reboot will have no effect, you just have to relogin so that a script in /etc/profile.d/ is ran and sets PATH

edudele commented 5 years ago

@edudele no es necesario, PATh se establece mediante un script en /etc/profile.d/, exportar una variable en el shell antes del reinicio no tendrá ningún efecto, solo tiene que volver a iniciar sesión para que un script en /etc/profile.d / se ejecuta y establece el PATH

I correct the entrance then. Thanks for the clarification