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

Question SSL certificate for *.com is OK, but how to create a let's encrypt certificate for the server IP adress.

erpo1205

New Pleskian
My domain (podico.com) SSL certificate is fine .
But how can I install the same certificate on the server itself ? (http://) lvps92-51-163-168.dedicated.hosteurope.de/
does not appear as having a valid certificate
I would like to have a lests encrypt certificate on 92.51.163.168 ( lvps92-51-163-168.dedicated.hosteurope.de) as I have on podico.com
 
You cannot create an SSL certificate for an IP address. Certificates can only be made out to a domain name. In that case that could be your generic hostname. However, I strongly recommend to set your own domain host name instead of using the generic name from the data center. You can also not use a certificate that covers one domain name for another. The domain name is integral part of the certificate, so that the certificate only protects exactly the domain(s) that are listed in that certificate. Luckily, with the free SSLIt extension and Let's Encrypt you can easily create separate certificates to protect your host (your Plesk :8443 graphical user interface).
 
Thanks Peter. I got also this advice with these how-tos: On detail seems important : Enter the 8443 port
please follow these two how-tos. First change your server hostname and afterwards you can secure your new hostname by performing the steps of the Plesk knowledge base article:

This article will you inform about steps needed to change your own server's hostname. This changes are necessary for a stable mail service.
Hostnamen des Servers ändern - Schritt für Schritt

How to secure a Plesk hostname on port 8443 with an SSL certificate (Let's Encrypt / other certificate authorities)
https://support.plesk.com/hc/en-us/...-Let-s-Encrypt-other-certificate-authorities-
 
Back
Top