Plesk Issues After Upgrade (Horde Webmail Showing Default Plesk Page)

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, October 11, 2008

Follow me on Twitter as @mattiasgeniar

After a Plesk upgrade, it’s possible that some services don’t do what they’re supposed to be doing (and have done right, before the update). It could be a Horde Webmail that is displaying a default Plesk page, instead of the webmail-client, or it could be something entirely different.

One of the easiest things to try, and one that solves a lot of Plesk issues, is running the command that will re-configure all services on the server, according to the Plesk internal database. That database contains all settings for mailboxes, DNS-records, web-users, additional settings, …

Here’s how to run it

/usr/local/psa/admin/bin/websrvmng -av

It’s harmless – as your services installed should always be configured with the latest Plesk Database Information (this normally happens automatically).

If that doesn’t do the trick to get Horde Webmail back, you could try reading up on Common Problems With Horde Webmail and Plesk.



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.