• We value your experience with Plesk during 2025
    Plesk strives to perform even better in 2026. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2025.
    Please take this short survey:

    https://survey.webpros.com/

backup utility stops working after upgrading to 8.0

T

timur@

Guest
Hi, i'm running plesk on CenOS 4.2 and i've got the following problem after upgrading to 8.0 from 7.5.4 version:

Code:
[root@plesk ~]# /usr/local/psa/admin/sbin/backupmng
read("/etc/psa/psa.key") failed
System error 13: Permission denied
read("/etc/psa/psa.key") failed
System error 13: Permission denied
Bad key: read init

System error 13: Permission denied
Bad key: read init

System error 13: Permission denied
backupmng: Error occured during '/usr/local/psa/admin/plib/backup/scheduled_backup.php --dump 14' execution
backupmng: Error occured during '/usr/local/psa/admin/plib/backup/scheduled_backup.php --dump 14' execution
read("/etc/psa/psa.key") failed
System error 13: Permission denied
read("/etc/psa/psa.key") failed
System error 13: Permission denied
Bad key: read init

System error 13: Permission denied
Bad key: read init

System error 13: Permission denied
backupmng: Error occured during '/usr/local/psa/admin/plib/backup/scheduled_backup.php --dump 26' execution
backupmng: Error occured during '/usr/local/psa/admin/plib/backup/scheduled_backup.php --dump 26' execution

How can if fix this ?
 
Just wanted to add to this saying I'm having the exact same problem. I didn't realize that Plesk had stopped making backups completely after I upgraded to 8.0.

I tried doing a CHMOD 444 on psa.key and when I did the error message changed. It repeated the following message for each of my domains: "backupmng: Error occured during '/usr/local/psa/admin/plib/backup/scheduled_backup.php --dump 1' execution"

So something has definately gone wrong in the Plesk 8.0 upgrade regarding the backup tools.

Anyone have an idea on a solution?
 
I got a response from support, and quickly I might add.

Vitaly Malakhov said the following:
"Look like corrupted ownership of the file, change key file ownership to
psaadm:psaadm, it should help.. We'll check this on our server and
report to developers if it is confirmed.

Thanks."

I ran: chown psaadm:psaadm /etc/psa/psa.key

That fixed it. The key was owned by root, so somehow the ownership of the key file changed to that during the update.

Hope this solution helps.
 
Back
Top