• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved Plesk custom url does not work

mrqwerty1980

New Pleskian
Server operating system version
centos 7
Plesk version and microupdate number
Product: Plesk Obsidian 18.0.59 Update #2
Hi,

The Plesk custom URL setting doesn't work. When I try to change this to any of the settings, I can still access the control panel from any domain on port 8443. This needs to be fixed as it's failing a cyber scan for the domains hosted on the server. The control panel needs to be closed for all other domains except the domain the certificate is configured for.
 
The Plesk custom URL setting doesn't work. When I try to change this to any of the settings, I can still access the control panel from any domain on port 8443.
That's correct behavior. Using a custom URL does not disable access on port 8443. If you want to block access on port 8443 you'll have to create a custom firewall rule to do this.
 
Hi, I don't want to block access to port 8443 for the correct encrypted subdomain. I just want to block all the hosted domains from having access to the control panel on 8443. Is this possible with a firewall rule? If so how?
 
Back
Top