Resolved Let's Encrypt Securing the Plesk Panel option missing

[Microbolt]

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

 

[IgorG]

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.

 

[Microbolt]

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!

 

[Edi Duluman]

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.

 

[UFHH01]

Hi Edi Duluman,

did you consider to use another browser as well?

Both URLs ( https://datingfabrikken.com/ and https://datingfabrikken.com:8443/ ) are configured to use a valid certificate from Let's encrypt ( issued 31.10.2016 ).

 

[Edi Duluman]

Hi @UFHH01

Tried with different browser. I updated my post as I needed to restart the server for the changes to have effect.