-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem with Let's Encrypt SSL: openssl:Error: 'pkey' is an invalid command. #1825
Comments
same error on centos 7 |
I was getting the following error and resolved it by removing '/usr/local/vesta/data/users/$USER/ssl/user.key' file where $USER was the username having the $DOMAIN. The problem was the generated user.key file was blank for some reason, so by removing it vestacp generated it again and it worked [root@host ~]# v-add-letsencrypt-domain $USER $DOMAIN
unable to load key
140331863979920:error:0906D06C:PEM routines:PEM_read_bio:no start line:pem_lib.c:707:Expecting: ANY PRIVATE KEY
unable to load Private Key
140162426619792:error:0906D06C:PEM routines:PEM_read_bio:no start line:pem_lib.c:707:Expecting: ANY PRIVATE KEY
unable to load key file
140522184501136:error:0906D06C:PEM routines:PEM_read_bio:no start line:pem_lib.c:707:Expecting: ANY PRIVATE KEY
Error: LetsEncrypt account registration 400
[root@host ~]#```
|
The problem is that LetsEncrypt have changed their API. VestaCP doesn't support at the moment the new API. Make yourself a favor and give HestiaCP (a VestaCP fork) a try. It is being developed by several VestaCP members as the continuation of Vesta which has been updated for ages. Just look for it at GitHub. |
Is there any option to migrate clients from Vesta to Hestia? I will give it a try, but I need to migrate all the stuff there including IP settings. |
Vesta’s backups are fully compatible with Hestia. That means that you should backup your Vesta users through the v-backup-users script (or through Vesta Panel) and then restore them with the v-restore-user script in Hestia. |
In the next release will be support for LE api 2. |
When the update will be published @anton-reutov ? |
When will this be released? I have numerous domains expired now? |
Operating System (OS/VERSION):
Debian 8 64-bit
VestaCP Version:
0.9.8
Installed Software (what you got with the installer):
PHP-FPM, apache, NGINX. Ioncube, Softacolous
Steps to Reproduce:
I Tried to add the Let's Encrypt certificate to a freshly added domain (with automatic LE). I got an error. Then I tried the CLI in SSH and I got the same error, but with more details.
This is what I got in the webGUI:
Error: LetsEncrypt account registration 400
An here is what I got in CLI (censored domain name and user):
Related Issues/Forum Threads:
Yes, I found several posts talking about error 400, but they are outdated or inactive for months.
Other Notes:
Yes, I checked that domain has a valid email address and I update the whole system via apt-get and then even tried
v-update-sys-vesta-all
This issue is here for about a month now and there is no public solution for hat.
The text was updated successfully, but these errors were encountered: