NET::ERR_CERT_COMMON_NAME_INVALID

donat · Post by **donat** » Tue Nov 22, 2016 3:24 pm

Hi

We have vestacp with different pages all on the same ip.

Some of them are using nginx as proxy and apache2 as webserver. They are all working great also with let's encrypt.

One of them are only using apache as webserver and no proxy at all.
Those are not working with the ssl of let's encrypt because of wrong sni.

NET::ERR_CERT_COMMON_NAME_INVALID

Das Certificate is just valid for the first entry in the apache.conf. All others aren't working. So how can I manage this?

Kind regards
Don

lochness · Post by **lochness** » Tue Mar 07, 2017 1:31 pm

Hi,

I think this was a while ago but did you manage to solve this?

It has happened on my server and I am completely stumped.

Thanks

donat · Post by **donat** » Tue Mar 07, 2017 1:38 pm

My problem is solved right now. As far I can remember I had to login as admin, then from there to the user, which was hosting the server.

Then I removed all ssl certificates and disabled the icon and stored it. Then I enabled SSL again with the let's encrypt support. I think, that was the solution.

I mean the problem was changing the let's encrypt from cli to gui.

Kind regards
Don

Vesta Control Panel - Forum