• 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!
  • 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.

Change Plesk Default TCP Port 8443

Eric Pretorious

Regular Pleskian
Is there a safe way to change the default TCP port that Plesk uses? (I'll be demonstrating Plesk at a conference this weekend and the network at the venue blocks all ports except a handful of the Well-Known Ports.) :(
 

Thanks, Igor:

After reading the KB article, I am left with the impression that the short answer [for Linux administrators] is "no".

Parallels Plesk Panel must be accessible on default ports. Port 8443 is used by external management and provisioning systems (Parallels Automation, PBA-S, Customer & Business Manager)...

If you need to make Parallels Plesk Panel accessible on custom port, it is better to add binding to PleskControlPanel website in IIS...
Would that be correct?
 
Back
Top