unable to write to any directory after WordPress backup restoration

  • saeedwaqas

    (@saeedwaqas)


    3 weeks ago

    Hello

    I have recently migrated my website to a new Ubuntu host and WordPress backup has been restored successfully and website has started working but I am currently getting below mentioned errors. I am still learning Linux so not sure how to securely make directory permission related changes. Please can someone guide.

    Errors are as under.

    I am unable to upload any media file – “xxxx.JPG” has failed to upload.
    Unable to create directory wp-content/uploads/2025/02. Is its parent directory writable by the server?

    I am not able to install any new plugins – Installation failed: Could not create directory. /home/myRHPWXK8nBPXeQt/xxxxxxx/public_html/wp-co ntent/upgrade/akismet.5.3.6

    I am also not able to update any pluging – Could not create directory. /home/myRHPWXK8nBPXeQt/xxxx/public_html/wp-content/upgrade/gn-publisher.1.5.20

    WordPress Site health tool is showing below mentioned errors.

    The wp-content/upgrade-temp-backup/plugins directory exists but is not writable. This directory is used to improve the stability of plugin updates. Please make sure the server has write permissions to this directory.

    Shows whether WordPress is able to write to the directories it needs access to.

    The main WordPress directory Not writable
    The wp-content directory Not writable
    The uploads directory Not writable
    The plugins directory Not writable
    The themes directory Not writable
    The fonts directory Not writable
    The must use plugins directory Not writable

Viewing 1 replies (of 1 total)
  • Shubham Patil

    (@iamshubhamsp)

    Hello @saeedwaqas
    It seems like you have not given permissions to your folders to write. You can try with this commands to give permission to folders and files
    sudo find /path/to/your/wordpress/directory -type d -exec chmod 755 {} \;
    sudo find /path/to/your/wordpress/directory -type f -exec chmod 644 {} \;

    And then restart your apache once.

Viewing 1 replies (of 1 total)
  • You must be logged in to reply to this topic.