WordPress 5.6.1 Some files are not writable by WordPress: wp-load.php

I have the same and I contacted my host (bluehost). The agent told me that my core files were fine and it was a false positive from the site health and it will just go away.

Thanks. I’ll just wait for it to go away.

This will not go away on its own if the permissions of the file wp-load.php were (for whatever reason, from whatever plugin etc) changed.

If you want to change it yourself, it’s trivial: Go to the cpanel file manager, locate the wp-load.php file (it should be in the root directory of your wordpress installation), and notice the number under the “permissions” column. If it’s something like 0444, it means it’s read-only (even to you).

If there is a zero as a first number, ignore it. The 2nd number means owner permissions (you), the 3rd means group permissions (if you use it), and the 4th means everyone else browsing the system.

To make the warning go away, right click the file, select “change permissions”, and then add “write” to your permissions, so that the number changes to 0644. Go back to the Site Health, repeat the check, and the warning will be gone.

• This reply was modified 3 years, 9 months ago by chrisauthor.

Thank you @chrisauthor. I contacted Blue Host and they corrected the File Permission for me and the error went away. I appreciate that you made this suggestion.

@chrisauthor thank you sir, your suggestion worked me. ??

Thanks for the answers on this question. I was also able to get bluehost to resolve my issue

@chrisauthor thanks so much – managed to change it on my own even though not particularly technically-minded!

@chrisauthor Worked like a charm. Thanks for the advice!

@chrisauthor Thank you! I was easily able to fix this on all three of my websites. I’m wondering how it happened on all three, although I do have a lot of the same plug-ins installed on all three.

Curious this. Have a lot of different installations running with the same host and this only came up on one site so far. The only difference between this site and the others I can think of is that it is in a subdirectory rather than being the main website. All fixed with a permissions change but odd how they got changed to begin with.