• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Question Read write permissions for WordPress backup buddy affected by quota?

Cliffsta

New Pleskian
Hi,

One of my domains recently went over resource usage in regards to disk usage. I have reset this quota to make the allotment larger. However, backup buddy within wordpress is complaining of not having correct folder permissions in WP-Content. I checked via ftp and all the folder permissions are correct. My question is, do I need to restart some server process in order to "reset" the limits? It seems like plesk may have locked down the uploading of further data etc according to the quota.

The specific error shown is : Error #9002d: BackupBuddy directory `/var/www/vhosts/firedog.co.uk/httpsdocs/wp-content/uploads/pb_backupbuddy/` is indicated as NOT being writable.

I have contacted ithemes the reseller of this app and they concur its a server config issue. This error only really started after the disk quota was exceeded.

Cliff
 
For the permission problem use:
Code:
plesk repair web YOURDOMAIN.COM -y

And for the wordpress-error have a look here.
 
Hi thank you,
Repair showed nothing wrong. Also for the wordpress error, I ssh'd and set all folder permissions to 775 and files to 664 as suggested. But still getting error.
So now I have uninstalled the Backup Buddy and interestingly when I look to upload a plugin via WP I get "Unable to create directory wp-content/uploads/2018/11. Is its parent directory writable by the server?", even though it looks like the file has successfully uploaded.

Perhaps there is an issue with the fact that the folders are with the incorrect owner (which does not have executable permissions) or the system user for the domain has insufficient permissions...

I wonder if these kind of permissions get set when a quota is exceeded and somehow it hasn't reverted back?

Cliff
 
Folder and file permissions are correct throughout. I used putty and set all folders to rwx rwx r-x and files to rw- rw- r-- and recursed to subdirectories too.
I don't believe it is folder permissions. the owner in the column is the "systemuser" and the group is "psacln" as expected.
 
Hi appreciate your help!
- It didnt fix the error, but I note that there were some errors resolved:

Checking virtual hosts' file system

There are incorrect permissions on some items in the root directory
of the domain 'firedog.co.uk' ..................................... [ERROR]
To see more details, run the command in the verbose mode: plesk repair fs -ver bose
Repairing incorrect permissions ................................. [FIXED]

There are incorrect permissions on some items in the WWW root
directory of the domain 'firedog.co.uk' ........................... [ERROR]
To see more details, run the command in the verbose mode: plesk repair fs -ver bose
Repairing incorrect permissions ................................. [FIXED]

There are incorrect permissions on some items in the system
directory for the domain 'firedog.co.uk' .......................... [ERROR]
To see more details, run the command in the verbose mode: plesk repair fs -ver bose
Repairing incorrect permissions ................................. [FIXED]

Error messages: 3; Warnings: 0; Errors resolved: 3
 
Could you please post the output of:

Code:
ls -l

in the directory?

Best regards
 
Sure :
total 288
drwxrwxr-x 6 fd_adminnew psacln 4096 Oct 19 05:05 10years
drwxrwxr-x 5 fd_adminnew psacln 4096 Nov 6 08:49 clients
drwxrwxr-x 2 fd_adminnew psacln 4096 Jul 22 2011 css
-rw-rw-r-- 1 fd_adminnew psacln 17542 Jul 22 2011 favicon.ico
-rw-rw-r-- 1 fd_adminnew psacln 26176 Aug 27 06:38 ___.htaccess.old
drwxrwxr-x 5 fd_adminnew psacln 4096 Jul 22 2011 img
-rw-rw-r-- 1 fd_adminnew psacln 9060 Jul 22 2011 index.html
-rw-rw-r-- 1 fd_adminnew psacln 418 Aug 27 02:45 index.php
-rw-rw-r-- 1 fd_adminnew psacln 14 Aug 24 09:04 i.php
-rw-rw-r-- 1 fd_adminnew psacln 19935 Aug 28 00:00 license.txt
drwxrwxr-x 2 fd_adminnew psacln 4096 Jul 22 2011 mt_images
drwxrwxr-x 2 fd_adminnew psacln 4096 Jul 22 2011 picture_library
-rw-rw-r-- 1 fd_adminnew psacln 7413 Aug 28 00:00 readme.html
drwxrwxr-x 3 fd_adminnew psacln 4096 Oct 3 2012 subdomains
drwxrwxr-x 11 fd_adminnew psacln 4096 Jul 22 2011 test
-rw-rw-r-- 1 fd_adminnew psacln 0 Aug 27 03:52 test.html
-rw-rw-r-- 1 fd_adminnew psacln 5447 Aug 27 02:46 wp-activate.php
drwxrwxr-x 9 fd_adminnew psacln 4096 Aug 24 09:07 wp-admin
-rw-rw-r-- 1 fd_adminnew psacln 364 Aug 27 02:46 wp-blog-header.php
-rw-rw-r-- 1 fd_adminnew psacln 1627 Aug 27 02:46 wp-comments-post.php
-rw-rw-r-- 1 fd_adminnew psacln 3359 Aug 27 04:50 wp-config.php
-rw-rw-r-- 1 fd_adminnew psacln 2853 Aug 28 00:00 wp-config-sample.php
drwxrwxr-x 7 fd_adminnew psacln 4096 Nov 7 00:00 wp-content
-rw-rw-r-- 1 fd_adminnew psacln 3286 Aug 27 02:46 wp-cron.php
drwxrwxr-x 18 fd_adminnew psacln 12288 Aug 26 07:09 wp-includes
-rw-rw-r-- 1 fd_adminnew psacln 2422 Aug 27 02:46 wp-links-opml.php
-rw-rw-r-- 1 fd_adminnew psacln 3301 Aug 27 02:46 wp-load.php
-rw-rw-r-- 1 fd_adminnew psacln 34337 Aug 28 00:00 wp-login.php
-rw-rw-r-- 1 fd_adminnew psacln 8048 Aug 27 02:46 wp-mail.php
-rw-rw-r-- 1 fd_adminnew psacln 16200 Aug 27 02:46 wp-settings.php
-rw-rw-r-- 1 fd_adminnew psacln 29924 Aug 27 02:46 wp-signup.php
-rw-rw-r-- 1 fd_adminnew psacln 4513 Aug 27 02:46 wp-trackback.php
-rw-rw-r-- 1 fd_adminnew psacln 3065 Aug 24 09:05 xmlrpc.php


Note the system user fd_adminnew
 
drwxrwxr-x 7 fd_adminnew psacln 4096 Nov 7 00:00 wp-content
Code:
chmod 766 -R wp-content
 
Back
Top