• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • 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.

Issue How to seucre a custom plesk login url?

thinkjarvis

Basic Pleskian
Server operating system version
Ubuntu 22.04.5 LTS
Plesk version and microupdate number
Plesk Obsidian Version 18.0.63 Update #4
I have a possible security issue when setting a custom plesk URL.

We've just moved to a new office and have a new IP address. The server is supposed to be blocked so only us and a few others can reach the Plesk login screen. 8443 is therefore restricted to our IP alopng with 22 and a few other vulnerable ports.

This particular server has a custom URL set in Plesk and I could access and log in to Plesk from the new IP address that is supposed to be blocked.

My question is - When you set a custom URL in plesk - Do port restrictions still work?
 
From your post it isn't entirely clear how you've restricted access to Plesk to certain IP addresses only. In case you've used a firewall to restrict access to port 8443, Plesk can still be access when using a custom URL. As a custom URL uses the default https port (443), instead of 8443. A better method might be to use the IP Access Restriction Management option in Tools & Settings to restrict access to Plesk to whitelisted IP's only.
 
Last edited:
Back
Top