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

Internet Ports

E

edcarriere

Guest
Plesk Panel is a good hosting control panel but it lacks in simplicity of information. I would suggest that a file be created that details each and every port that must be kept open behind firewalls to allow all of the Plesk Panel scripts to connect to the Internet locations they require to connect to.

Every portion or service of the Plesk Panel requires access to the Internet using different ports. The licensing port 5224, admin login port 8443/8440, the migration script 22 and many more... By having a file detailing these ports, it would make life easier for everyone.

This file should be placed in the documentation menu item of the main website as a separate item and not included in other items as it is easier to have it seen quickly then having to search for something.

I recently found out that port 22 is required for migration but other ports are also required.

Comments?
 
With the exception of the lisencing port, I'd say everything else is mostly self-evident.

Having to have SSH port 22 open for the Migration Manager is a good "gotcha" though, and I agree that this should be made clear in the screen where you enter the login details for the server you want to migrate from.

This is not to say that having a list of ports that Plesk typically uses would not be a bad idea though! 2 minutes adding the list to the manual (and KB) might save a lot of people a lot of time in the future, so it has my vote.
 
I know of many normal hosting ports.

20-21 - FTP
22 - SSH
25 - SMTP
53 - DNS
80 - HTTP
110 - POP
143 - IMAP
443 - HTTPS
465 - SMTP over SSL
554 - Real Time Streaming Protocol (RTSP)
587 - e-mail message submission (SMTP)
783 - SpamAssassin spamd daemon
989-990 - FTPS Protocol (data/control): FTP over TLS/SSL
993 - Internet Message Access Protocol over SSL (IMAPS)
995 - Post Office Protocol 3 over TLS/SSL (POP3S)
3306 - MySQL database system (not necessary to be open ?)
5224 - Plesk Licensing Port
8334 - Plesk Control Panel Secure

There are other ports for mail servers and such but they do not need to be open to work. If anyone sees a port missing, send me a quick reply and I will add it...
 
I would not open:

783 - SpamAssassin spamd daemon
989-990 - FTPS Protocol (data/control): FTP over TLS/SSL
554 - Real Time Streaming Protocol (RTSP

Unless you had a very good reason to.

3306 should also be closed under normal circumstances - you don't usually want remote systems trying to access your MySQL server.
 
Back
Top