• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Resolved secure Plesk hostname on port 8443 with an SSL certificate Let's Encrypt ERROR

Butcher

New Pleskian
Server operating system version
CentOS Linux 7.9.2009 (Core)
Plesk version and microupdate number
Version 18.0.51
My situation is like this:

1. I have subdomain ex: plesk.mydomain.com that points to IP addres of plesk obsidian (record A shows good IP - checked)

2. I want to acces plesk plesk.mydomain.com:8443 - and secure that with SSL

3. So I do what I supposed to do according to this:

4. but when I do step 3 - Click Let's Encrypt.
I got Error message:
Error: Could not find valid hostname

I have looked but can not find the reason and do not know how to make it work.

I work on:


VersionPlesk Obsidian v18.0.51_build1800230310.09 os_CentOS 7
OSCentOS Linux 7.9.2009 (Core)

Note:
currently in Tools and settings -> SLL Certificates I see default certificate with details like this:


A self-signed certificate is an identity certificate signed by its own creator. If you use such a certificate, it means that you yourself verify your sites' identity. Although self-signed certificates allow the usage of SSL/TLS, they are trusted less, and considered as less secure.

Bits

2048

Country

Switzerland

State or province



Location (city)

Schaffhausen

Organization name (company)

Plesk

Organization department or division name



Domain name

Plesk

Email

[email protected]

Upload the certificate files​

 
You mean in Server Settings.
And no it was not !
WELL DONE thank you very much - works like charm now.

By the way it would be good if it was mentioned in PLESK tutorial to check that setting.
 
Back
Top