- Server operating system version
- Ubuntu 20.04
- Plesk version and microupdate number
- 18.0.52.3
Hi guy's
We use multiple Plesk servers, and we did change from dedicated certificates to Let's encrypt ones
On all servers except one it did work like a charm.
We did the change like this:
Tools & Settings -> SSL/TLS Certificates and choosed for securing Plesk & Mail the Lets Encrypt certificate pool.
But on the default site on plesk.domain it still shows the old certificate
(We then tried to use the Make default on the new Lets encrypt with the result that all vhosts nginx configs got deleted as opposed to the hint "securing connections to newly created websites"...
So we had to run plesk repair on all vhosts ..... is this behaviour to be expected ?)
Anyways i found that on Tools & Settings -> IP addresses -> "Ip-addr" -> There is still the old certificated to this ip
Strangely we have this diffrent on multiple servers, but also on the ones with old certificates
the Plesk default page has a valid Let's encrypt certificate.
Therefore i dont know what might be the issue with this server,
plesk repair web -server -n
did also not show any issues
We use multiple Plesk servers, and we did change from dedicated certificates to Let's encrypt ones
On all servers except one it did work like a charm.
We did the change like this:
Tools & Settings -> SSL/TLS Certificates and choosed for securing Plesk & Mail the Lets Encrypt certificate pool.
But on the default site on plesk.domain it still shows the old certificate
(We then tried to use the Make default on the new Lets encrypt with the result that all vhosts nginx configs got deleted as opposed to the hint "securing connections to newly created websites"...
So we had to run plesk repair on all vhosts ..... is this behaviour to be expected ?)
Anyways i found that on Tools & Settings -> IP addresses -> "Ip-addr" -> There is still the old certificated to this ip
Strangely we have this diffrent on multiple servers, but also on the ones with old certificates
the Plesk default page has a valid Let's encrypt certificate.
Therefore i dont know what might be the issue with this server,
plesk repair web -server -n
did also not show any issues