Page 1 of 1

Problem with panel SSL

Posted: Mon May 22, 2017 2:05 pm
by azafor
I've been using vestaCP and the latest version installed. I've been trying to install SSL in CentOS panel, In my case the panel url is panel.mydomain.tld:8083. When I'm trying to login my panel, the address bar is red with "not secure" message.

I'know it's because SSL not installed in panel.mydomain.tld:8083, But I also don't know how to install SSL in panel.mydomain.tld:8083.

Can you guys help me on this?

Re: Problem with panel SSL

Posted: Mon May 22, 2017 2:27 pm
by Phogo
I just added the panel.mydomain domain to the admin account and clicked SSL support. Worked for me. I did need to restart the vesta service though.

Re: Problem with panel SSL

Posted: Sun May 28, 2017 3:22 am
by BBuchanan1013
Are you running Apache? Nginx?

Re: Problem with panel SSL

Posted: Sun May 28, 2017 5:34 am
by azafor
BBuchanan1013 wrote:Are you running Apache? Nginx?
Both. Apache for Application back end and Nginx for front end (Nginx Reverse Proxy)..

Re: Problem with panel SSL

Posted: Thu Jun 01, 2017 7:01 pm
by BBuchanan1013
Ok, to install the SSL into the Panel or backend is very simple. Your gonna need a few things before you get started:

The Cert location (cert, privkey, chain(just in case))
SSH
SFTP or FTP with root access

For this example I'm going to use the SSL certs I get from LetsEncrypt (the github version, not the built in. Info should be similar):
1. SFTP or FTP into the server then goto the directy: /usr/local/vesta/nginx/conf/
2. Edit nginx.conf

Code: Select all

....~
 ssl                  on;
 ssl_certificate      /usr/local/vesta/ssl/certificate.crt;
 ssl_certificate_key  /usr/local/vesta/ssl/certificate.key;
 ssl_session_cache    shared:SSL:10m;
 ssl_session_timeout  10m;
We need to change the cert and the key, my example:

Code: Select all

....~
ssl_certificate    /etc/letsencrypt/live/accounts/domain.tld/cert.pem
ssl_certificate_key /etc/letsencrypt/live/accounts/domain.tld/privkey.pem
SpoilerShow
there is no difference between a .pem and .crt. They only changed the extension after the period so you can rename a .crt to a .pem without issue most times.
Once that file is edited to match the cert and key, all we need to do is save it and restart vesta with:

Code: Select all

user@server: service vesta restart
panel should now be secure with your ssl

Re: Problem with panel SSL

Posted: Sat Jun 03, 2017 10:42 am
by ScIT
viewtopic.php?f=19&t=13057

In my point of view the best solution to add lets encrypt to vesta.