Bobcares

Why the Main WordPress Directory not Writable?

by | Nov 19, 2024

If you’ve encountered the “Main WordPress Directory Not Writable” error, don’t worry—it’s a common issue. Bobcares, as a part of our WordPress Support Services offers solutions to every query that comes our way.

Overview
  1. Understanding “Main WordPress Directory Not Writable” Error
  2. Why This Error Happens?
  3. Steps to Fix the Error
  4. Conclusion

Understanding “Main WordPress Directory Not Writable” Error

The error usually means WordPress can’t modify or create files in its core directory, affecting plugin installations, theme updates, and content uploads. Here’s a quick and straightforward guide to fix it.

the main wordpress directory not writable

Why This Error Happens?

1. Incorrect File Permissions: WordPress needs specific permissions for files and folders to function correctly. Permissions generally should be:

755 for folders
644 for files

2. Ownership Issues: The web server user (like www-data for Apache or nginx for Nginx) needs ownership of the WordPress directory. If WordPress is installed by a different user, it might not have the access it needs.

3. File System Restrictions (open_basedir): Some hosts restrict PHP access outside a specific path (via open_basedir), limiting WordPress’s ability to write files.

4. Server Configuration: Hosting environments, especially shared hosting, sometimes restrict access to certain directories.

Steps to Fix the Error

1. Check and Adjust File Permissions

i. Using FTP:

Connect to the site via FTP (e.g., FileZilla).

Right-click on the WordPress root directory, select “File Permissions.”

Set directories to 755 and files to 644.

ii. Using SSH:

If we have SSH access, run:

find /path/to/wordpress/ -type d -exec chmod 755 {} \;
find /path/to/wordpress/ -type f -exec chmod 644 {} \;

Replace /path/to/wordpress/ with the WordPress installation path.

2. Ensure Correct Ownership

i. Make sure the WordPress directory is owned by the web server user:

sudo chown -R www-data:www-data /path/to/wordpress

ii. Replace /path/to/wordpress with the WordPress directory path and www-data with the server’s web user if different.

3. Disable open_basedir Restrictions

i. In the hosting control panel (e.g., cPanel), Look for the open_basedir setting.

ii. If it’s restricting access, disable it for WordPress, or we can ask the hosting provider for assistance.

4. Force Direct Access in wp-config.php

i. In the wp-config.php file, add this line to allow WordPress to write files directly:

define('FS_METHOD', 'direct');

ii. This skips the need for FTP and allows WordPress to write directly to the server.

5. Check Server Disk Space: Low disk space can sometimes cause this error, especially on shared hosting. Check available disk space through the hosting control panel, and free up space if needed.

6. Try a Different Browser: Occasionally, browser cache or cookies can interfere. Try accessing the site from a different browser or device to rule out this issue.

[Looking for a solution to another query? We are just a click away.]

Conclusion

By following these steps, we should be able to resolve the “Main WordPress Directory Not Writable” error quickly. With the correct permissions, ownership, and a few configuration tweaks, WordPress should be back to functioning smoothly, allowing us to update plugins, themes, and manage content effortlessly.

 

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF