Viewing 11 posts - 1 through 11 (of 11 total)
  • Author
    Posts
  • #86921
    Will
    Guest

    Hi BoldGrid,

    It looks like there’s an error being thrown on our website by your plugin. We’re hoping you can help us troubleshoot. Below is the error response. It implies an issue with file permissions. We want to be sure that this is from your plugin and nothing nefarious before making changes. Your help would be appreciated.

    Thank you,
    Will

    component
    : 
    "WordPress Core"
    file
    : 
    "wp-admin/includes/class-wp-filesystem-direct.php"
    key
    : 
    "11c7331adc31ea73c6ebe7f1ae3f39cf"
    line
    : 
    529
    message
    : 
    "touch(): Unable to create file /opt/bitnami/wordpress/1639238237.txt because Permission denied"
    stack
    : 
    (8) ['touch()', 'WP_Filesystem_Direct->touch()', 'Boldgrid_Backup_Admin_Test->is_writable()', 'Boldgrid_Backup_Admin_Test->get_is_abspath_writable()', 'Boldgrid_Backup_Admin_Test->run_functionality_tests()', 'Boldgrid_Backup->define_admin_hooks()', 'Boldgrid_Backup->__construct()', 'run_boldgrid_backup()']
    type
    : 
    "warning"
    #86926
    Brandon C
    Keymaster

    Hi Will,

    Thanks for reaching out and thank you for using Total Upkeep for WordPress!

    This error is related to the file permissions on your server. Normally when you see this it means your System Administrator disabled write permissions on the root of your website, and only allows the user to write to the wp-content directory rather than the core WordPress files.

    You’ll need to log into your cPanel and change your user permissions in order for the backup to complete. Your Web Host can help with this if you’re unsure of how to do so, I also located a guide that you might find useful.

    I hope this helps. Please let us know if there’s anything else we can answer for you!

    #86931
    Will
    Guest

    Thanks for getting back so soon, Brandon!

    As far as I can tell, all the folders have the recommended permission of 755. See here:

    https://blogvault.net/wordpress-permissions/

    Is something else recommended for Total Upkeep?

    #86933
    Will
    Guest

    Hi Brandon,

    Thanks for the quick help! From what I can tell, the file permissions are correctly set. Can you tell me the correct permissions?

    #86936
    Brandon C
    Keymaster

    Thanks Will, and you’re very welcome,

    Your permissions seem to be correct. Is this your first time creating a backup with Total Upkeep? You should create a sanity check just to verify that you are able to create backups on your server.

    You can also try changing your your backup file compressor type to see if that resolves the issue. You can do so by navigating to Total Upkeep > Settings > Backup Process. If System Zip is available, choose that option. System Zip is significantly faster than the PclZip or ZipArchive libraries, and may use fewer resources.

    #86949
    Will
    Guest

    Hi Brandon,

    That’s what is strange: We have been using Total Upkeep successfully for nearly a year. I did update file permissions recently, but I did it according to WordPress Best practices. Attached is an image of our WP Security plugin, which is what guided us to update a few of the file permissions.

    If I change the WordPress directory to 775, it works. Is this a safe file permission?

    Also, it looks like Total Upkeep wants /usr/sbin to be 775. Is this correct? See attached.

    Thanks again for your help,
    Will

    Screenshots of the above on our Google Drive:
    https://drive.google.com/drive/folders/1aubhcynl9FDtQfRoKA5X2jnD8UxuQ5u8?usp=sharing

    #87037
    Brandon C
    Keymaster

    Hi Will,

    That set of permissions (775) may not be the safest but it isn’t totally unsafe. The difference is it will give read, write, execute access at the server level instead of based on an individual user.

    If you’re only changing the permissions for one file I’d say go for it but I wouldn’t recommend it for all files. Another option is to exclude the problematic file and try running the backup without it if that works for you.

    #88116
    Will
    Guest

    Thanks, Brandon — Switching to 775 worked.

    A similar error is occurring with the /usr/sbin directory. Should it be 775, too?

    According to Preflight Check, the User home directory is /usr/bin (755)

    
    touch(): Unable to create file /usr/sbin/719259088.txt because Permission denied	
    
    wp-admin/includes/class-wp-filesystem-direct.php:529
    touch()
    wp-admin/includes/class-wp-filesystem-direct.php:529
    WP_Filesystem_Direct->touch()
    /bitnami/wordpress/wp-content/plugins/boldgrid-backup/admin/class-boldgrid-backup-admin-test.php:346
    Boldgrid_Backup_Admin_Test->is_writable()
    /bitnami/wordpress/wp-content/plugins/boldgrid-backup/admin/class-boldgrid-backup-admin-test.php:884
    Boldgrid_Backup_Admin_Test->is_homedir_writable()
    /bitnami/wordpress/wp-content/plugins/boldgrid-backup/admin/class-boldgrid-backup-admin-core.php:2857
    Boldgrid_Backup_Admin_Core->page_backup_test()
    wp-includes/class-wp-hook.php:308
    do_action('total-upkeep_page_boldgrid-backup-test')
    wp-admin/admin.php:259
    #88127
    Brandon C
    Keymaster

    Hi Will,

    You can try taking the same approach with this .txt file or exclude the file from your backup as linked aboved.

    Let us know if you still need our assistance!

    #88130
    Will
    Guest

    Thank you, Brandon! It is showing /usr/sbin as 775 now, but User home directory is still not writable. Will this conflict with backups at all? Does it need to be?

    #88134
    Brandon C
    Keymaster

    Hi Will,

    I would definitely recommend excluding the file from your backup instead of changing the file permissions. It’s not generally a good practice to change file permissions.

Viewing 11 posts - 1 through 11 (of 11 total)
  • The topic ‘PHP AJAX error related to Total Upkeep’ is closed to new replies.