Facebook
Twitter-
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 The old plesk server name link still works
- Thread starter Julianos
- Start date
Do you mean if you open https://old-link.tld:8443
If yes then anything that points to the server IP (over the DNS) will open Plesk.
Or if you mean https://old-link.tld then probably you set "All domains and subdomains that resolve to the server IP address but are not used for hosting" over Tools & Settings > Customize Plesk URL
If yes then anything that points to the server IP (over the DNS) will open Plesk.
Or if you mean https://old-link.tld then probably you set "All domains and subdomains that resolve to the server IP address but are not used for hosting" over Tools & Settings > Customize Plesk URL
Hi .That's it. But this subdomain and others are not added to the dns records, does not exist. The page that is not there should show a 404 error.
My configuration: In Tools -> plesk link settings: No custom urls. Only https: // <server-IP- or-hostname>: 8443. In theory, therefore, it shouldn't select every subdomain to open a dialog, so here: https: //docs.plesk.com/en -US / obsidian / deployment -guide / plesk-install-and-update-on-one-server / customize-plesk-url.76455 /
And according to my configuration, you must login via IP or hostname. This is not the case, I can log in from any subdomain that is not added to my Plesk account. Do I get it wrong?
Last edited:
Yes, you do.
plesk listens on port 8443, on any IP the server responds to (0.0.0.0:8443). This is different from the domains that are actually hosted on that server as those only listen on the assigned IP. (Though it would be nice if apache would not listen on the external IP when the domain is configured to use nginx as proxy.)
That means, plesk will respond on any domain that resolves to any of the server's IPs. Those don't even need to be in your DNS, e.g. the name your hoster assigned to the machine, like server42.rack7.rz10.provider.com. It does not even use the domain information from SNI at all, as sw-cp-server is configured to serve plesk as ip_default for any IP.
learning_curve
Golden Pleskian
@Julianos Plesk do have an article on that specific subject; How to configure a redirect from the domain name/IP address to the server hostname on port 8443 in Plesk for Linux? If the resultant untrusted certificate warning is an issue for you then THIS post might help you work around that. The link that is contained in it, goes to another thread that has an informative answer from a Plesk staff member on this subject. Both of the threads are initially about a slightly different subjects, but the answer mentioned is relevant to the Plesk article / your question.
First, understand it is intentional that plesk listens on all IPs and doesn't care about domains. Changing this has great potential to shoot yourself in the foot & lock yourself out of the admin panel.
If you still want to do that: Changing sw-cp-server's config will not last for long as plesk will change it back on updates. So the only lasting way I can think of is to put the domain you want plesk to respond to on a separate IP, then block port 8443 for all other IPs in the firewall. It will still respond when using that IP instead of the domain, but at least it will be blocked on all other IPs/domains.
