Error: LetsEncrypt account registration 400

[mindflame]

Hi All,

I have a linode VPS with VestaCP installed and some websites on it. The letsencrypt certificate works fine on some domains and their sub-domains, when installed via GUI. But for some domains, it throws Error: LetsEncrypt account registration 400 error. Soi tried to execute it via CLI, which throws "openssl:Error: "pkey" is an invalid command" error.

I would like to say that 70% of the websites are facing this problem?

What could be wrong?

Thank you.

[DJ_Ironic]

Hi.

I can confirm I have tha same issue even in the web GUI. Just getting

Code: Select all

"Error: LetsEncrypt account registration 400"

. Now I tried CLI in SSH and Got the

Code: Select all

openssl:Error: 'pkey' is an invalid command.

I am running VestaCP on Debian 8 64-bit with all system updates installed.

[ScIT]

The problem is, that let's encrypt has changed/disabled their api on 13. february. Serghey (the main dev of this project) has pushed already new scripts, but still have NOT pushed new packages to deploy this on the systems.

The best way is to download the scripts directly, so you could just run the commands below. After that, let's encrypt should work again:

Code: Select all

# Download new files
wget https://raw.githubusercontent.com/serghey-rodin/vesta/master/bin/v-add-letsencrypt-domain -O /usr/local/vesta/bin/v-add-letsencrypt-domain
wget https://raw.githubusercontent.com/serghey-rodin/vesta/master/bin/v-add-letsencrypt-user -O /usr/local/vesta/bin/v-add-letsencrypt-user
wget https://raw.githubusercontent.com/serghey-rodin/vesta/master/bin/v-update-letsencrypt-ssl -O /usr/local/vesta/bin/v-update-letsencrypt-ssl

# Remove
rm -fr /usr/local/vesta/bin/v-check-letsencrypt-domain
rm -fr /usr/local/vesta/bin/v-sign-letsencrypt-csr

# Set permission
chmod +x /usr/local/vesta/bin/v-add-letsencrypt-domain
chmod +x /usr/local/vesta/bin/v-add-letsencrypt-user
chmod +x /usr/local/vesta/bin/v-update-letsencrypt-ssl

I'm just a mod here, without any access to the core functionality like repository and so on - that's the reason I created with a few other members a fork of vesta called HestiaCP (https://github.com/hestiacp/hestiacp) with a new own and most secure infrastructure - also to handle my own server infrastructe, to keep them up to date and alive.

[alexcy]

+1 for HestiaCP. I consider this fork as the "continuation" of Vesta legacy, since (at least for me that I had the nightmare of trying to install VestaCP on Ubuntu 18.04 for ages) .

HestiaCP has solved all of my problems. Thanks guys.