• 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 Lets Encrypt Does Not Work On Different IP

spcan

New Pleskian
Hey folks,

Here is my issue I have several shared IPs on one server. The Lets Encrypt certificates work fine for websites hosted on the main IP however when I host a website with a different shared IP (not the main IP) the website is served with a self signed certificate (not secure) and if I switch back the website to be hosted on the main IP then all works fine. Can you please help me figure this out?

Thanks a lot
 
It is the correct behaviour. SSL certificate is assigned for specific IP address and is not actual for another IP address. So, you have to issue the new certificate for your site on another IP address.
 
Maybe I haven't been clear enough. I have Plesk installed with 2 shared IPs let's call them IP1 (main IP) and IP2. Domain1 is hosted on IP2 and the Lets Encrypt certificate was installed (issued?) on Domain1 (hosted on IP2) already therefore it should be assigned to IP2 right?

issue the new certificate for your site on another IP address
As far as I can tell the Lets Encrypt module installs certificates based on domains not IPs
 
Back
Top