Facebook
Twitter
Émerson Felinto
Regular Pleskian
The title is very self explanatory.
-
We value your experience with Plesk during 2024
Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
Please take this short survey:
https://pt-research.typeform.com/to/AmZvSXkx -
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.
-
We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.
Question How to disable access to plesk panel by <domain.com>: 8443?
- Thread starter Émerson Felinto
- Start date
Sergio Manzi
Regular Pleskian
I may have a "moronitis" attack, but I'm not getting what you mean:
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.
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?)
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.
Émerson Felinto
Regular Pleskian
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?
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?
You don't solve it. You redirect it.
How to redirect from the domain to the server hostname on port 8443?
How to redirect from the domain to the server hostname on port 8443?
Émerson Felinto
Regular Pleskian
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 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 ?
How to block access to Plesk for domains over port 8443
Applicable to: Plesk for Linux Plesk for Windows Question How to allow access to Plesk: from a hostname URL only (https://server.example.com:8443)? from several URLs and block access to oth...