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

Default Container firewall access rules

Fronobulax

New Pleskian
Greetings,
If I setup the container firewall in "Normal" mode I have a list of standard rules I can apply. There is a named "Access to Plesk Control Panel" which allows me to access the control panel. However, on the control panel the option for Server->Plesk->Updates and Upgrades is not available as it defaults to port 8447. I have to manually add the port to ipchains (and it periodically resets itself)...

My question is this. Are these rules and the default ports standard out of the box defaults, and if so shouldn't there be a rule that would allow me to access Updates and Upgrades?

If this is something that has been altered by my VPS provider I can go back to them, but their response was that I needed to bring up the issue with Parallels.
 
Back
Top