We are happy to announce that Vesta is back under active development as of 25 February 2024. We are working on v1 candidate and expect to engage more with the community over the coming months. We are committed to open source, and we encourage contributors to help us build the future of Vesta.
NET::ERR_CERT_COMMON_NAME_INVALID
NET::ERR_CERT_COMMON_NAME_INVALID
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
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
Re: NET::ERR_CERT_COMMON_NAME_INVALID
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
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
Re: NET::ERR_CERT_COMMON_NAME_INVALID
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
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