• 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 Let's Encrypt with shared ip address

Brandon Turpin

Basic Pleskian
Looking at the Plesk documentation. It states that a dedicated IP address is not needed for every website that uses a Let's Ecrypt SSL. (SSL and Shared IP Addresses)

I am running on Ubuntu 18.04. I assume there is no issue with this version. The issue I am having, is once the SSL is assigned, it is valid, but it has the little warning that states that it is not secure because it is using a shared IP address. From the documentation it seems like this would not be an issue, so I am not sure what else I need to do to get it to work successfully.
 
Where are you seeing this little warning? Can you share the domain?
 
Back
Top