• 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

Question How to disable access to plesk panel by <domain.com>: 8443?

I may have a "moronitis" attack, but I'm not getting what you mean:

a) make the Plesk panel accessible only under https://<FQDN_of_the_hostname>:8443 (and not under the names of the hosted domains)
b) make the Plesk panel accessible only under https://www.example.com:8443 (and not https://example.com:8443) (why?)
c) do not make the Plesk panel accessible at all (why using Plesk, then?)​

N.B.: when citing domain names as examples it is best practice to always use example.(com | org | net) (see: IANA — IANA-managed Reserved Domains): domain(dot)com is a valid, privately registered domain name.
 
Yea, I'm not following. How DO you actually want Plesk accessed or not at all?
 
There was an error when I typed the title. Please, ask a moderator to change to: "How to enable access to plesk panel via <example.com>:8443"?

What I want is this. Currently Plesk is accessible and working normally through the following address: "https://<FQDN_of_the_hostname>:8443". However I noticed that when I access port 8443 via HTTPS from any domain that is hosted on my Plesk server I simply get a security warning saying that the certificate is invalid.

How can I solve this?
 
Hello,
I ended up changing my mind and really saw that redirection can not be considered an option. I noticed that most of my clients access Plesk through Central of client /WHMCS, since in comparison to cPanel, for example, Plesk does not have the easy-to-decorate address, like adding "/ cpanel" at the end of the URL.

How can I disable access to <example.com>:8443 and make access only available to my <hostname>:8443 ?
 
I would also like to know.
It looks horrible for the clients to see a broken certificate error as only accessing the plesk panels via the hostname has a valid certificate.
Redirecting is not a good solution as it only happens post-cert validation.
 
Back
Top