Plesk 10 Update: Update/Autoinstaller Port Change & Plesk Panel Port Redirection on Virtuozzo

Want to help support this blog? Try out Oh Dear, the best all-in-one monitoring tool for your entire website, co-founded by me (the guy that wrote this blogpost). Start with a 10-day trial, no strings attached.

We offer uptime monitoring, SSL checks, broken links checking, performance & cronjob monitoring, branded status pages & so much more. Try us out today!

Profile image of Mattias Geniar

Mattias Geniar, November 15, 2010

Follow me on Twitter as @mattiasgeniar

Here are 2 annoying changes on the new Plesk 10 panel.

Plesk Panel on Virtuozzo can will take control of port 8443 (Plesk Controlpanel), where this was usually managed by your underlying Virtuozzo Hardware Node. The solution is to disable the VZPP-Plesk Port Redirection (8443), and to keep the VZPP Port Redirection (4643) active. See the “Operating Inside Parallels Container” topic.

vzctl set CT_ID –offline_management yes –offline_service vzpp –save

An alternative would be to run the Plesk Panel on an alternative port (say 18443).

Plesk Panel updates on Plesk 10 will now redirect you to the autoinstaller running in port 8447. Keep this in mind in your firewall config, to allow that port to be accessed. For a complete list of all “recommended” Plesk (8-9-10) ports, see the article “Which ports need to be opened for all Plesk services to work with a firewall?”.

And @Parallels: Don’t change these ports, as it’s not fun to keep changing firewall configs. This causes clients to upgrade and suddenly lock themselves out, because the new ports aren’t allowed by default in the firewall.

Humpf.



Want to subscribe to the cron.weekly newsletter?

I write a weekly-ish newsletter on Linux, open source & webdevelopment called cron.weekly.

It features the latest news, guides & tutorials and new open source projects. You can sign up via email below.

No spam. Just some good, practical Linux & open source content.