• 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.

Resolved Incorrect SSL certificate on IPv4, but OK on IPv6

David - ECA

New Pleskian
Server operating system version
Ubuntu 24.04
Plesk version and microupdate number
18.0.63 Update #4
Hello everyone,
I'm contacting you because I'm experiencing a problem on my Plesk: Following a change of IPv4 address on my server (the IPv6 addresses haven't changed), for all the subscriptions affected by this IP change, the SSL certificate (Let's Encrypt) works correctly on IPv6, but the default certificate is used for IPv4, instead of the certificate defined on the website.
I've tried recreating the certificate, but it makes no difference.
Does anyone have any idea what is causing the problem?
Thank you in advance for your feedback.
Best regards, David
 
Hello everyone,

After talking to Plesk support (very reactive! Thanks to them!), we found the solution!

The problem came from the IP change:
The new IP is a floating IP (Openstack) linked to a private IP in NAT 1:1 (it was the first time I had this type of configuration, I had always worked with public IPs directly, until now).

And in Plesk, don't use the public IP directly! You have to configure the private IP to indicate the correct public IP (in “Tools & settings” => “IP addresses”), then assign the private IP to the relevant subscriptions, not the public IP!

Hope this helps! :)
 
Back
Top