• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • Our UX team believes in the in the power of direct feedback and would like to invite you to participate in interviews, tests, and surveys.
    To stay in the loop and never miss an opportunity to share your thoughts, please subscribe to our UX research program. If you were previously part of the Plesk UX research program, please re-subscribe to continue receiving our invitations.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Resolved Let's Encrypt: Install certificate for Plesk Panel fails

gbotica

Regular Pleskian
Hello,

I'm using Plesk Onyx Version 17.5.3 Update #43 on CentOS 7.4.

I have been trying to install a Let's Encrypt certificate for the Plesk Panel, but I get the following error:

SSL TLS Certificates.png

My Plesk Panel uses a subdomain URL like: https://subdomain.domain.nz (the main domain, 'domain.nz' is hosted on an entirely different server). I read something about using a subdomain for Plesk Panel being an issue in the past, but thought it was resolved?

Could it be something wrong with the URL that Let's Encrypt is fetching, i.e. it ends with:

...domain.nz:8443.well-known/acme-challenge...

Shouldn't there be a slash after 8443? If so, how would I resolve it?

Thanks in advance for any help you can provide.
 
I've managed to work around this by adding a Administrator owned subscription for my Plesk Panel's URL and then using an .htaccess rule to redirect to the actual panel URL i.e. ...:8443.

Once I'd done that I could successfully install a Let's Encrypt certificate for the panel.
 
Back
Top