Applicable to:
- Plesk for Linux
- Plesk for Windows
Question
Domain example.com is secured by valid certificate. Why is SSL privacy warning shown when accessing Plesk panel UI using customer's domain name at https://example.com:8443?
CONFIG_TEXT: Your connection is not private
or:
CONFIG_TEXT: NET::ERR_CERT_COMMON_NAME_INVALID
or:
CONFIG_TEXT: Connection not secure
Answer
Plesk interface on port 8443 is different service and is secured by an SSL issued to the server hostname. Domain example.com at default pot 443 has its own certificate issued for this particular domain name. So https://example.com will show valid SSL issued for example.com, while https://example.com:8443 will detect that SSL for example.com is not the same as for the server hostname.
To avoid the privacy warning, access Plesk using main server hostname URL secured by Let's Encrypt. For example, if the hostname is hostname.com, the link will be https://hostname.com:8443.
The link may be used by any customer, domain owner, reseller, or administrator.
Alternatively, issue the UCC SSL certificate covering several domains from any convenient SSL authority. After that install this certificate using instructions.
Additional information
How to use different SSL certificates for Plesk UI (over port 8443)?
Comments
Despite this problem, the default landing page installed for every new domain continues to have a link to https://example.com:8443 and results in the inevitable SSL eror that link will produce. You cannot even change the html on the default page because it is produced by a javascript file loaded from the Plesk server. Please change the javascript file so that the link points to https://hostname.com:8443
Please sign in to leave a comment.