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

Noam Harel

Regular Pleskian
Hi

i wanted to have plesk secured with lets encrypt.
i followed this article:
How to secure Plesk login page with Let's Encrypt certificate
which didn't work for some reason. i mean that after doing all of the steps i still get certificate error.
what i did:
1) built a sub-domain
2) pointed an A record and waited for it to propagate
3) create Lets encrypt certificate for the sub-domain
4) in - 'Certificate for securing Plesk' i choose 'Lets Encrypt certificate (server pool)'

after that still shows ssl error

domain to check is: web1.the123.co.il
plesk url: https://185.106.128.171:8443

please your thoughts.

Noam
 
Hi

i wanted to have plesk secured with lets encrypt.
i followed this article:
How to secure Plesk login page with Let's Encrypt certificate
which didn't work for some reason. i mean that after doing all of the steps i still get certificate error.
what i did:
1) built a sub-domain
2) pointed an A record and waited for it to propagate
3) create Lets encrypt certificate for the sub-domain
4) in - 'Certificate for securing Plesk' i choose 'Lets Encrypt certificate (server pool)'

after that still shows ssl error

domain to check is: web1.the123.co.il
plesk url: https://185.106.128.171:8443

please your thoughts.

Noam
Hello Noam, since the last letsencrypt extension update, it's not needed to create a sub-domain anymore.
You should find a button letsencrypt and then you will have just to choose the domain or subdomain you want to protect with a SSL certificate :

78764.png
 
Hello Noam, since the last letsencrypt extension update, it's not needed to create a sub-domain anymore.
You should find a button letsencrypt and then you will have just to choose the domain or subdomain you want to protect with a SSL certificate :

78764.png


sorry i get the same result,
 
Hi Noam Harel,

your Plesk - URL


is secured and valid. Pls. see as well:



Your IP "185.106.128.171" doesn't have a reverse entry and as a result, your IP doesn't resolve to a FQDN.

=> Reverse DNS Lookup for 185.106.128.171

( Pls. contact your IP provider, if you desire to change that! )​
thanks!
so, in conclusion: the plesk access with SSL is only with the domain name and not the IP address.
 
It's not possible de generate a SSL certificate for an IP with Let's Encrypt.
Nor is it possible with other CA's. It's deprecated and a serious security issue.
I believe there are some exceptions, but I'm convinced these don't apply on you.
 
Back
Top