Search results

Well, not really... Turns out webmailmng --remove doesn't remove the database named `horde`. If you try to drop the database manually, the backup will fail again, just like described in my original post. So there are two problems here: * uninstalling horde doesn't clean up the database *...

It helped, thanks, Igor!

I removed Horde using autoinstaller a while ago, and left only AtMail as the only option for web mail for all of my domains. I have checked all the domains to make sure they all have AtMail as their web mail option. However, when I run a backup, it fails with a bunch of repeating messages...

Likely a watchdog/psa-monit issue, see http://brablc.com/2013/09/21/plesk-watchdog-nginx-shutdown-problem/ The Plesk's self-monitoring system is so clever it restarts itself to ensure it's always running. Except when the server is shutting down, the brave die-hard self-monitoring system keeps...

One caveat though: when deleting users, make sure you delete both the Panel and E-Mail users: they are separate entities in the system. Overall, all these changes in Plesk 10.x make no sense other than making server management more and more difficult. What next?

Looks like I found a solution. Create a new Role "E-Mail User" without any permissions: make sure all permission switches are set to "Denied". For existing email users: create a new Panel User, choose "Use an external e-mail address" option and specify a user's existing email address. Even...

Yes, waiting for the solution. This is a show stopper, as email users are unable to change their passwords, let alone manage their forwarding and other options.

No, IgorG, this is what actually worked for me:

Ok, I've found the problem, it was a PHP bug in that file - messages_en-US.php. I can't believe you released this package without even testing whether it works with PHP 4+ or not. The problem is that starting from PHP 4 (I believe) you can't merge arrays using +. What I see in that file is a...

I upgraded my Plesk 8.0 to 8.1 and when I tried to open the admin control panel via the 8443 port (i.e. https://myhost:8443/) it redirected to login.php3 and showed an empty page. I enabled PHP error reporting as described in your Knowledge Base and I got the following error: Fatal error...

The upgrade went through smoothly this time, but the server still doesn't start! I need this to be fixed urgently. Please, please.

I'm able to start a rescue shell from RAM, from where I see everything on my disks. The error message in the upgrade log was: Database integrity check failed: duplicate values of (upgrade_date) exist in table upgrade_history I managed to start mysqld and httpd in the rescue shell, then...

I'm running Plesk 7.5.2 on RH9. Recently the auto-upgrader suggested to download and install 7.5.3. After some time I received an email saying that the upgrade procedure has failed. I tried to log in to the control panel as admin, but after validating the password, the panel brought an empty...