• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue Default Page Certificate issue (no new cert)

Bernben

New Pleskian
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 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 ?)
It appears that it is deleted, but it should be reconfigured automatically right afterwards, but will take a few minutes depending on the number of domains.

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.
A cert only protects a domain name, not an ip address. The selector should only be valid if you also set a default domain name, because then you need the appropriate certificate for it. Else it should not matter what is shown on that page.
 
Back
Top