-
guidolin
- Posts: 9
- Joined: Tue Mar 14, 2017 12:39 pm
Error Code: 15 — SSL — Lets Encrypt
Hello,
We are trying to add the Lets Encrypt to a domain, which already had the Lets Encrypt set up, and when trying to save, it complains the Error Code: 15
We’ve tried a few options, but nothing works.
Could they help us? VestCp is updated in the latest version. We use Apache without Nginx.
Thank you.
-
guidolin
- Posts: 9
- Joined: Tue Mar 14, 2017 12:39 pm
Re: Error Code: 15 — SSL — Lets Encrypt
Post
by guidolin » Tue Apr 16, 2019 2:09 pm
Code: Select all
v-add-letsencrypt-domain admin tattooja.com.br www.tattooja.com.br yes
Error: Let's Encrypt validation status 400
Last edited by imperio on Tue Apr 16, 2019 2:38 pm, edited 1 time in total.
Reason: added tag code
-
guidolin
- Posts: 9
- Joined: Tue Mar 14, 2017 12:39 pm
Re: Error Code: 15 — SSL — Lets Encrypt
Post
by guidolin » Tue Apr 16, 2019 2:10 pm
Code: Select all
[root@node22167-vesta-k7 bin]# v-add-letsencrypt-domain admin tattooja.com.br www.tattooja.com.br no
Error: Let's Encrypt validation status 400
[root@node22167-vesta-k7 bin]# v-add-letsencrypt-domain admin tattooja.com.br www.tattooja.com.br yes
Error: Let's Encrypt new auth status 429
[root@node22167-vesta-k7 bin]# v-add-letsencrypt-domain admin tattooja.com.br www.tattooja.com.br yes
Error: Let's Encrypt new auth status 429
Last edited by imperio on Tue Apr 16, 2019 2:38 pm, edited 1 time in total.
Reason: added tag code
-
imperio
- VestaCP Team
- Posts: 6991
- Joined: Sat Dec 01, 2012 12:37 pm
- Contact:
Re: Error Code: 15 — SSL — Lets Encrypt
Post
by imperio » Tue Apr 16, 2019 2:37 pm
Hi,
What OS, web stack and vestacp version on your server ?
-
guidolin
- Posts: 9
- Joined: Tue Mar 14, 2017 12:39 pm
Re: Error Code: 15 — SSL — Lets Encrypt
Post
by guidolin » Tue Apr 16, 2019 2:46 pm
[root@node22167-vesta-k7 bin]# v-list-sys-vesta-updates
PKG VER REL ARCH UPDT DATE
— — — —- —- —-
vesta 0.9.8 24 x86_64 yes 2019-04-16
vesta-php 0.9.8 23 x86_64 yes 2018-10-18
vesta-nginx 0.9.8 24 x86_64 yes 2019-04-16
vesta-ioncube 0.9.8 24 x86_64 yes 2019-04-16
vesta-softaculous 0.9.8 24 x86_64 yes 2018-11-28
[root@node22167-vesta-k7 bin]# cat /etc/*-release
CentOS Linux release 7.5.1804 (Core)
NAME=»CentOS Linux»
VERSION=»7 (Core)»
ID=»centos»
ID_LIKE=»rhel fedora»
VERSION_ID=»7″
PRETTY_NAME=»CentOS Linux 7 (Core)»
ANSI_COLOR=»0;31″
CPE_NAME=»cpe:/o:centos:centos:7″
HOME_URL=»https://www.centos.org/»
BUG_REPORT_URL=»https://bugs.centos.org/»
CENTOS_MANTISBT_PROJECT=»CentOS-7″
CENTOS_MANTISBT_PROJECT_VERSION=»7″
REDHAT_SUPPORT_PRODUCT=»centos»
REDHAT_SUPPORT_PRODUCT_VERSION=»7″
CentOS Linux release 7.5.1804 (Core)
CentOS Linux release 7.5.1804 (Core)
-
imperio
- VestaCP Team
- Posts: 6991
- Joined: Sat Dec 01, 2012 12:37 pm
- Contact:
Re: Error Code: 15 — SSL — Lets Encrypt
Post
by imperio » Tue Apr 16, 2019 2:54 pm
Can you provide access to your server? We will check it
-
imperio
- VestaCP Team
- Posts: 6991
- Joined: Sat Dec 01, 2012 12:37 pm
- Contact:
Re: Error Code: 15 — SSL — Lets Encrypt
Post
by imperio » Tue Apr 16, 2019 3:24 pm
Code: Select all
v-add-letsencrypt-domain admin tattooja.com.br www.tattooja.com.br
for le2 wildcard, nameservers should be working on vestacp
for ex.
Code: Select all
ns1.tattooja.com.br
ns2.tattooja.com.br-
guidolin
- Posts: 9
- Joined: Tue Mar 14, 2017 12:39 pm
Re: Error Code: 15 — SSL — Lets Encrypt
Post
by guidolin » Tue Apr 16, 2019 3:28 pm
nameservers:
ns2.gpja.com.br
ns1.gpja.com.br
[root@node22167-vesta-k7 ~]# v-add-letsencrypt-domain admin tattooja.com.br www.tattooja.com.br
Error: Let’s Encrypt validation status 400
-
guidolin
- Posts: 9
- Joined: Tue Mar 14, 2017 12:39 pm
Re: Error Code: 15 — SSL — Lets Encrypt
Post
by guidolin » Tue Apr 16, 2019 6:26 pm
Error code 15 is why the SSL limit has been reached, right? Why not let Lets Encrypt Support be selected?
-
rus2lan
- Posts: 1
- Joined: Wed Apr 17, 2019 7:14 am
- Os: Ubuntu 15x
- Web: apache
Re: Error Code: 15 — SSL — Lets Encrypt
Post
by rus2lan » Wed Apr 17, 2019 7:15 am
The same problem.. Error 400 after upgrade from .23 to .24 version.
Error code 15 triggers in VestaCP during Let’s Encrypt SSL installation due to several reasons. The most common reasons include lack of updated repositories, using a force-https template, etc.
As a part of our Server Management Services, we help our Customers to fix SQL related errors regularly.
Today, let us discuss the possible causes and fixes for this error.
What causes the error code 15 in VestaCP?
Generally, while installing Let’s Encrypt SSL in VestaCP, sometimes error code 15 triggers. For instance, the error appears as shown below:
Here are the major reasons for this error to occur.
- Repositories not updated
- Adding another domain to hosting with let’s encrypt enabled, caused a bug to switch off “proxy support”
- If a force-https template for Nginx is used in let’s encrypt, “nginx.domain.com.conf_letsencrypt” is missing
How to fix error code 15 in VestaCP?
Now let’s take a look at how our Support Engineers resolve this error to our customers.
1. Updating and upgrading the repositories
We execute the below commands to update and upgrade the repositories.
apt-get update
apt-get upgrade2. For sites that use Apache with Nginx proxy (hosting & force-https template), switching off LE support and saving, then going back in and switching on generally fixes the issue.
We suggest not to disable Nginx proxy support. However, select the “hosting” template for Nginx when disabling SSL. Also, log in as admin, switch user to non-admin user, and then enable proxy again. Then you can turn on SSL / Letsencrypt. The domain should clearly retain the proxy settings as originally set.
3. Include the file “nginx.domain.com.conf_letsencrypt” to the force-https template.
We suggest adding “include %home%/%user%/conf/web/*nginx.%domain_idn%.conf_letsencrypt;” in the file /usr/local/vesta/data/templates/web/nginx/force-https.tpl.
[Need any further assistance with VestaCP errors? – We’d be happy to help you]
Conclusion
Today, we saw the different causes for this VestaCP error to occur and also saw the solutions our Support Engineers provide to resolve this error.
PREVENT YOUR SERVER FROM CRASHING!
Never again lose customers to poor server speed! Let us help you.
Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.
GET STARTED
var google_conversion_label = «owonCMyG5nEQ0aD71QM»;
-
guidolin
- Posts: 9
- Joined: Tue Mar 14, 2017 12:39 pm
Error Code: 15 — SSL — Lets Encrypt
Hello,
We are trying to add the Lets Encrypt to a domain, which already had the Lets Encrypt set up, and when trying to save, it complains the Error Code: 15
We’ve tried a few options, but nothing works.
Could they help us? VestCp is updated in the latest version. We use Apache without Nginx.
Thank you.
-
guidolin
- Posts: 9
- Joined: Tue Mar 14, 2017 12:39 pm
Re: Error Code: 15 — SSL — Lets Encrypt
Post
by guidolin » Tue Apr 16, 2019 2:09 pm
Code: Select all
v-add-letsencrypt-domain admin tattooja.com.br www.tattooja.com.br yes
Error: Let's Encrypt validation status 400Last edited by imperio on Tue Apr 16, 2019 2:38 pm, edited 1 time in total.
Reason: added tag code
-
guidolin
- Posts: 9
- Joined: Tue Mar 14, 2017 12:39 pm
Re: Error Code: 15 — SSL — Lets Encrypt
Post
by guidolin » Tue Apr 16, 2019 2:10 pm
Code: Select all
[root@node22167-vesta-k7 bin]# v-add-letsencrypt-domain admin tattooja.com.br www.tattooja.com.br no
Error: Let's Encrypt validation status 400
[root@node22167-vesta-k7 bin]# v-add-letsencrypt-domain admin tattooja.com.br www.tattooja.com.br yes
Error: Let's Encrypt new auth status 429
[root@node22167-vesta-k7 bin]# v-add-letsencrypt-domain admin tattooja.com.br www.tattooja.com.br yes
Error: Let's Encrypt new auth status 429Last edited by imperio on Tue Apr 16, 2019 2:38 pm, edited 1 time in total.
Reason: added tag code
-
imperio
- VestaCP Team
- Posts: 6987
- Joined: Sat Dec 01, 2012 12:37 pm
- Contact:
Re: Error Code: 15 — SSL — Lets Encrypt
Post
by imperio » Tue Apr 16, 2019 2:37 pm
Hi,
What OS, web stack and vestacp version on your server ?
-
guidolin
- Posts: 9
- Joined: Tue Mar 14, 2017 12:39 pm
Re: Error Code: 15 — SSL — Lets Encrypt
Post
by guidolin » Tue Apr 16, 2019 2:46 pm
[root@node22167-vesta-k7 bin]# v-list-sys-vesta-updates
PKG VER REL ARCH UPDT DATE
— — — —- —- —-
vesta 0.9.8 24 x86_64 yes 2019-04-16
vesta-php 0.9.8 23 x86_64 yes 2018-10-18
vesta-nginx 0.9.8 24 x86_64 yes 2019-04-16
vesta-ioncube 0.9.8 24 x86_64 yes 2019-04-16
vesta-softaculous 0.9.8 24 x86_64 yes 2018-11-28
[root@node22167-vesta-k7 bin]# cat /etc/*-release
CentOS Linux release 7.5.1804 (Core)
NAME=»CentOS Linux»
VERSION=»7 (Core)»
ID=»centos»
ID_LIKE=»rhel fedora»
VERSION_ID=»7″
PRETTY_NAME=»CentOS Linux 7 (Core)»
ANSI_COLOR=»0;31″
CPE_NAME=»cpe:/o:centos:centos:7″
HOME_URL=»https://www.centos.org/»
BUG_REPORT_URL=»https://bugs.centos.org/»
CENTOS_MANTISBT_PROJECT=»CentOS-7″
CENTOS_MANTISBT_PROJECT_VERSION=»7″
REDHAT_SUPPORT_PRODUCT=»centos»
REDHAT_SUPPORT_PRODUCT_VERSION=»7″
CentOS Linux release 7.5.1804 (Core)
CentOS Linux release 7.5.1804 (Core)
-
imperio
- VestaCP Team
- Posts: 6987
- Joined: Sat Dec 01, 2012 12:37 pm
- Contact:
Re: Error Code: 15 — SSL — Lets Encrypt
Post
by imperio » Tue Apr 16, 2019 2:54 pm
Can you provide access to your server? We will check it
-
imperio
- VestaCP Team
- Posts: 6987
- Joined: Sat Dec 01, 2012 12:37 pm
- Contact:
Re: Error Code: 15 — SSL — Lets Encrypt
Post
by imperio » Tue Apr 16, 2019 3:24 pm
Code: Select all
v-add-letsencrypt-domain admin tattooja.com.br www.tattooja.com.br
for le2 wildcard, nameservers should be working on vestacp
for ex.
Code: Select all
ns1.tattooja.com.br
ns2.tattooja.com.br-
guidolin
- Posts: 9
- Joined: Tue Mar 14, 2017 12:39 pm
Re: Error Code: 15 — SSL — Lets Encrypt
Post
by guidolin » Tue Apr 16, 2019 3:28 pm
nameservers:
ns2.gpja.com.br
ns1.gpja.com.br
[root@node22167-vesta-k7 ~]# v-add-letsencrypt-domain admin tattooja.com.br www.tattooja.com.br
Error: Let’s Encrypt validation status 400
-
guidolin
- Posts: 9
- Joined: Tue Mar 14, 2017 12:39 pm
Re: Error Code: 15 — SSL — Lets Encrypt
Post
by guidolin » Tue Apr 16, 2019 6:26 pm
Error code 15 is why the SSL limit has been reached, right? Why not let Lets Encrypt Support be selected?
-
rus2lan
- Posts: 1
- Joined: Wed Apr 17, 2019 7:14 am
- Os: Ubuntu 15x
- Web: apache
Re: Error Code: 15 — SSL — Lets Encrypt
Post
by rus2lan » Wed Apr 17, 2019 7:15 am
The same problem.. Error 400 after upgrade from .23 to .24 version.
In a few words, please describe the issue that you’re experiencing:
Installed hestia on clean & updated debian 9:
bash hst-install.sh -w yes -o yes -k no -c no -t no
Please enter your response here (e.g. When I click on the Web tab, a blank page is displayed).
What steps did you take when the issue occured?
added a domain EXAMPLE.com
trying adding lets encrypt via gui
result:
Error: Let’s Encrypt acc registration failed
Expected behavior:
Successful creation of Lets Encrypt cert.
Operating system distribution and release:
Debian 9 (up to date)
Which version of Hestia Control Panel is currently installed?
1.0.4
Which branch are you using?
https://raw.githubusercontent.com/hestiacp/hestiacp/release/install/hst-install.sh
When did this issue occur? After a clean installation, or after an upgrade?
right after fresh install
Which of the following web server configurations are you using?
bash hst-install.sh -w yes -o yes -k no -c no -t no
Which of the following server roles are installed on your server?
bash hst-install.sh -w yes -o yes -k no -c no -t no
In order to better assist, please post any relevant log information below:
Tip: Most log files can be found under /var/log/.
/usr/local/hestia/log/error.log
2019-07-12 18:39:20 v-add-letsencrypt-user ‘admin’ [Error 15]
2019-07-12 18:39:20 v-add-letsencrypt-domain ‘admin’ ‘DOMAIN.com’ ‘www.DOMAIN.com’ » [Error 15]
Related issues or forum threads:
Additional notes:
The same domain works with VestaCP, implying that DNS is set up correctly. The domain has HSTS (from the previous install).
Error code 15 occurs in VestaCP during Let’s Encrypt SSL installation due to several reasons. The most common reasons include lack of updated repositories, using a force-https template, and so on.
Here at Ibmi Media, as part of our Server management Services, we regularly help our Customers to resolve VestaCP related errors.
In this context, we shall look into the causes of this error and its fix.
What triggers the error code 15 in VestaCP?
Generally, while installing Let’s Encrypt SSL in VestaCP, sometimes error code 15 triggers.
Here are the major reasons for this error to occur:
1. Repositories not updated.
2. Adding another domain to hosting with let’s encrypt enabled, caused a bug to switch off «proxy support».
3. If a force-https template for Nginx is used in let’s encrypt, «nginx.domain.com.conf_letsencrypt» is missing.
How to fix error code 15 in VestaCP?
To fix this error, follow the process given below:
1. Updating and upgrading the repositories
We execute the below commands to update and upgrade the repositories:
apt-get update
apt-get upgrade
2. For sites that use Apache with Nginx proxy (hosting & force-https template), switching off LE support and saving, then going back in and switching on generally fixes the issue.
We suggest not to disable Nginx proxy support. However, select the “hosting” template for Nginx when disabling SSL. Also, log in as admin, switch user to non-admin user, and then enable proxy again. Then you can turn on SSL / Letsencrypt. The domain should clearly retain the proxy settings as originally set.
3. Include the file «nginx.domain.com.conf_letsencrypt» to the force-https template.
We suggest adding «include %home%/%user%/conf/web/*nginx.%domain_idn%.conf_letsencrypt;» in the file /usr/local/vesta/data/templates/web/nginx/force-https.tpl.
[Need urgent assistance with VestaCP errors? – We’d be happy to help you. ]
using vestacp to handle our vps web hosting, problem with when activate letsencrypt ssl
its give message error 15
stuck and try to install lestencrypt manual
https://www.youtube.com/watch?v=T29GPpLbvvs
and now i got error
Can't load /root/.rnd into RNG
139662228705728:error:2406F079:random number generator:RAND_load_file:Cannot open file:../crypto/rand/randfile.c:88:Filename=/root/.rnd
google again then found link
https://www.gitmemory.com/issue/wazuh/wazuh/3395/496449901
and this solve the problem
root@panel:/usr/local/bin# cd /etc/ssl/ root@panel:/etc/ssl# cp openssl.cnf openssl.cnf.bak root@panel:/etc/ssl# nano openssl.cnf
i comment variable RANDFILE
RANDFILE = $ENV::HOME/.rnd to #RANDFILE = $ENV::HOME/.rnd
lets create again
root@panel:/etc/ssl# v-add-letsencrypt-domain admin mydomain.ddns.net
success, and now i can use vestacp web interface to create ssl
and if stil stuck, we can use manual command
Published by G3n1k
just to remember what i had known
View all posts by G3n1k
Published
August 31, 2020August 31, 2020
Итак, вас насторожили предупреждения от гугл что на сайте с такой-то версии браузера будут отображаться такие же уведомления о безопасности. Или вы просто решили обзавестись зелёным замочком в адресной строке напротив вашего сайта.
Благо VestaCP последних версий умеет самостоятельно устанавливать сертификат от Let’s Encrypt. Нужно только выбрать 2 чекбокса вверху и нажать кнопку Save.
Но, гладко было на бумаге, для больнства доменов панель мне выдавала такую ошибку.
Хотя А-записи и CNAME были настроены. Ок, пойдём другим путём, открываем консоль, набираем команду
v-add-letsencrypt-user USERВ которой USER меняете на имя пользователя для которого хотите установить сертификат. Теперь вводим:
v-add-letsencrypt-domain USER DOMAIN.COMГде так же USER это будет пользователь, а DOMAIN.COM смените на название нужного домена который есть у этого юзера в панели.
Если будут ошибки то скорее всего эта или эта
Теперь опять смотрим страницу домена в панели и видим что сертификат успешно подключен.
Обратите внимание, в панели мелким шрифтом отображается информация о сроке окончания действия сертификата.
Теперь принудительно вводим в браузере адрес с https и смотрим. Всё должно отображаться нормально.
Осталось только настроить редиректы с http на https. Важное замечание, если вы правили apache2.conf или nginx.conf в /home/user/conf/web, например, меняли open_basedir в apache2 то обратите внимание на то, что после установки сертификата, в этой директории /home/user/conf/web появятся файлы с буквой s впереди: sapache2.conf или snginx.conf в них необходимо так же внести те же самые изменения, которые были сделаны в обычных файлах а потом перезапустить апач или сделать service nginx reload если в конфиге nginx что-то правили.
Не ранее чем 2 месяца и не позднее чем через 3 необходимо обновить сертификат командой.
v-update-letsencrypt-sslУвы на данный момент сертификаты именно от Let’s Encrypt выдаются только на 3 месяца и продлить их можно не раньше чем за месяц до дня окончания, но что бы не забывать об этом действии вы можете поставить команду на CRON.
Operating System (OS/VERSION):
Ubuntu 16.04
VestaCP Version:
Version: 1.0.0 (amd64)
Release: 5
Installed Software (what you got with the installer):
apache, nginx, mysql, vsftpd
Steps to Reproduce:
- Edit an existing domain
- Remove check from SSL support
- Save form
- Go to Cloudflare and set SSL/TLS options to «Flexible» for that domain
- Back in Vesta edit domain and check SSL support
- Then check Lets Encrypt Support
- Save form
- It will load for a couple seconds and show error
- If I sent Cloudflare to Full Strict the site will not load (will show Cloudflare error: Invalid SSL certificate)
Related Issues/Forum Threads:
#2149
Other Notes:
Before the November update I used to set Cloudflare SSL/TLS to flexible then create the SSL let’s encrypt and then moved the Cloudflare to Full Strict mode. This is currently working on a Vesta Panel which didn’t update.
Loading
In a few words, please describe the issue that you’re experiencing:
Installed hestia on clean & updated debian 9:
bash hst-install.sh -w yes -o yes -k no -c no -t no
Please enter your response here (e.g. When I click on the Web tab, a blank page is displayed).
What steps did you take when the issue occured?
added a domain EXAMPLE.com
trying adding lets encrypt via gui
result:
Error: Let’s Encrypt acc registration failed
Expected behavior:
Successful creation of Lets Encrypt cert.
Operating system distribution and release:
Debian 9 (up to date)
Which version of Hestia Control Panel is currently installed?
1.0.4
Which branch are you using?
https://raw.githubusercontent.com/hestiacp/hestiacp/release/install/hst-install.sh
When did this issue occur? After a clean installation, or after an upgrade?
right after fresh install
Which of the following web server configurations are you using?
bash hst-install.sh -w yes -o yes -k no -c no -t no
Which of the following server roles are installed on your server?
bash hst-install.sh -w yes -o yes -k no -c no -t no
In order to better assist, please post any relevant log information below:
Tip: Most log files can be found under /var/log/.
/usr/local/hestia/log/error.log
2019-07-12 18:39:20 v-add-letsencrypt-user ‘admin’ [Error 15]
2019-07-12 18:39:20 v-add-letsencrypt-domain ‘admin’ ‘DOMAIN.com’ ‘www.DOMAIN.com’ » [Error 15]
Related issues or forum threads:
Additional notes:
The same domain works with VestaCP, implying that DNS is set up correctly. The domain has HSTS (from the previous install).
Loading
using vestacp to handle our vps web hosting, problem with when activate letsencrypt ssl
its give message error 15
stuck and try to install lestencrypt manual
https://www.youtube.com/watch?v=T29GPpLbvvs
and now i got error
Can't load /root/.rnd into RNG
139662228705728:error:2406F079:random number generator:RAND_load_file:Cannot open file:../crypto/rand/randfile.c:88:Filename=/root/.rnd
google again then found link
https://www.gitmemory.com/issue/wazuh/wazuh/3395/496449901
and this solve the problem
root@panel:/usr/local/bin# cd /etc/ssl/ root@panel:/etc/ssl# cp openssl.cnf openssl.cnf.bak root@panel:/etc/ssl# nano openssl.cnf
i comment variable RANDFILE
RANDFILE = $ENV::HOME/.rnd to #RANDFILE = $ENV::HOME/.rnd
lets create again
root@panel:/etc/ssl# v-add-letsencrypt-domain admin mydomain.ddns.net
success, and now i can use vestacp web interface to create ssl
and if stil stuck, we can use manual command
Published by G3n1k
just to remember what i had known 
View all posts by G3n1k
Published
August 31, 2020August 31, 2020