• 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 Securing the Plesk Panel option missing

Microbolt

Microbolt

New Pleskian
Hello

I have a fresh install of Plesk Onyx on a Windows Server 2016 box. I've been reading through the steps to use a Let's Encrypt certificate to secure the actual Plesk panel on port 8443. Based on the KB article and from when I've read on GitHub I need to create a domain name with the same name as the Plesk panel URL (which I have done) and then request a cert for that newly created domain. The problem I'm running into is I do not have the option to choose "Use this certificate to secure connections to Plesk" that is shown in step 4 of the KB article.

Did Plesk 17 change the way we need to perform this?

Here is my setup:

Plesk URL: https://pleskwin.domain.tld:8443
Plesk Hostname: pleskwin.domain.tld
Subscription Domain: pleskwin.domain.tld
​
Thanks in advance for any help someone can provide!

Here is the KB article and I was referencing:
https://kb.plesk.com/en/129861

And the GitHub thread:
https://github.com/plesk/letsencrypt-plesk/issues/11#issuecomment-166916633
 
If you already installed LetsEncrypt certificate for this domain, go to Tools&Settins -> SSL/TLS Certificates and click Change for option "Certificate for securing Plesk".
I hope it will help.
 
That worked perfect. I even looked at that screen and figured since all I saw was Default Certificate that it wouldn't work. Thanks for helping out! :)
 
Might be something wrong with mine ?

Got Web PRO edition, 17.0.17, went to tools & settings > SSL/TLS certificates, chose the one for securing plesk ( as Let's Encrypt for my main hostname -- domain used for super user ).
What should I do now ? Refreshing the page, certificate used is still the one from Plesk.

Started incognito window, same thing. Main website with HTTPS works fine, while panel does not.

Any ideas ? Tried uninstalling / reinstalling Let's Encrypt.

Later edit: had to restart the server in order for it to be refreshed.
 
Last edited:
You must log in or register to reply here.

Similar threads

M
Issue Let's Encrypt Bulk Domain Renewal
Replies
4
Views
504
MacGyver
M
S
Issue Let's Encrypt/SSL It! empty domain name error
Replies
8
Views
1K
SilentWarrior
S
D
Resolved Let's Encrypt Certificate missing domain name
Replies
2
Views
439
davorg
D
C
Resolved Plesk Extensions does not appear
Replies
2
Views
369
conor
C
R
Issue Let's Encrypt Error 400 on every domain
Replies
1
Views
763
Sebahat.hadzhi
Sebahat.hadzhi
Back
Top