Web interface using different ssl certificate? Topic is solved

Questions regarding the Web Interface
GUI
prxbl
Posts: 14
Joined: Fri Aug 14, 2015 5:28 pm

Web interface using different ssl certificate?

Postby prxbl » Mon Apr 03, 2017 3:12 pm

I've recently installed a Comodo SSl certificate and I've switched my main domain to HTTPS.
However the web interface of vesta does not use the new certificate and is still giving me the error message
"Your connection is not private"

I am using Vesta 0.9.8 r17 on Ubuntu 14.04
How can I fix this, so that the vesta web interface makes use of the same certificate?

Thanks

skurudo
VestaCP Team
Posts: 7783
Joined: Fri Dec 26, 2014 2:23 pm
Location: Moscow
Contact:

Re: Web interface using different ssl certificate?

Postby skurudo » Tue Apr 04, 2017 10:40 am

Quick answer - yes, different.
-> DigitalOcean competition - please, support us
-> fix for phpmyadmin - nice and sweet now

prxbl
Posts: 14
Joined: Fri Aug 14, 2015 5:28 pm

Re: Web interface using different ssl certificate?

Postby prxbl » Tue Apr 04, 2017 11:10 am

How can I fix this?

skurudo
VestaCP Team
Posts: 7783
Joined: Fri Dec 26, 2014 2:23 pm
Location: Moscow
Contact:

Re: Web interface using different ssl certificate?  Topic is solved

Postby skurudo » Tue Apr 04, 2017 11:15 am

You have two ways to do this:
1) via web... SERVER -> configure -> Vesta SSL

2) vesta-nginx -> /usr/local/vesta/nginx/conf/nginx.conf and add path to your cettificate:

Code: Select all

    ssl_certificate      /home/admin/conf/web/ssl.domain.ru.pem;
    ssl_certificate_key  /home/admin/conf/web/ssl.domain.ru.key;
-> DigitalOcean competition - please, support us
-> fix for phpmyadmin - nice and sweet now

prxbl
Posts: 14
Joined: Fri Aug 14, 2015 5:28 pm

Re: Web interface using different ssl certificate?

Postby prxbl » Tue Apr 04, 2017 11:34 am

Method 1 would have been nice but it did not work, I was getting this error "Error: Certificate Authority not found", even though there we're only 2 fields: SSL Certificate and SSL Key which I was copy and pasting from the domain config tab.

Method 2 worked and it successfully solved the issue.
Thank you!

techforusnews
Posts: 1
Joined: Tue Apr 04, 2017 1:42 pm

Re: Web interface using different ssl certificate?

Postby techforusnews » Tue Apr 04, 2017 1:46 pm

prxbl wrote:I've recently installed a Comodo SSl certificate and I've switched my main domain to HTTPS.
However the web interface of vesta does not use the new certificate and is still giving me the error message
"Your connection is not private"

I am using Vesta 0.9.8 r17 on Ubuntu 14.04
How can I fix this, so that the vesta web interface makes use of the same certificate?

Thanks


The point is that if you use another sub-domain for Vesta cpanel and turn HTTPS, then you will definitely get the "Your connection is not private" error as the SSL certificate is only valid for one URL. It's not a wildcat SSL, I think.

If you want to use HTTPS for all sub-domain, buy a wildcat SSL certificate or use Let's Encrypt.

Updated: Try this one to bypass the Your connection is not private error in Google Chrome temporarily.
Last edited by techforusnews on Sat Apr 08, 2017 5:38 am, edited 1 time in total.

skurudo
VestaCP Team
Posts: 7783
Joined: Fri Dec 26, 2014 2:23 pm
Location: Moscow
Contact:

Re: Web interface using different ssl certificate?

Postby skurudo » Tue Apr 04, 2017 2:48 pm

techforusnews wrote:If you want to use HTTPS for all sub-domain, buy a wildcat SSL certificate or use Let's Encrypt.


Nope, it's not it. You have two different nginx instanses: for sites and for Vesta. ;)
-> DigitalOcean competition - please, support us
-> fix for phpmyadmin - nice and sweet now


Return to “Web Interface”



Who is online

Users browsing this forum: Bing [Bot] and 2 guests