WordPress cannot install or update a plugin or theme because it “could not create directory.”
You do not have to become a server administrator because one part of your website stopped cooperating. Start with the checks that stay inside WordPress. If the problem moves into hosting or server configuration, I will show you where the risk begins—and where it may make more sense to hand the headache to me.
Start with the checks inside WordPress
- Check whether the hosting account is out of storage.
- Use Tools → Site Health → Info to review filesystem permissions.
- Try installing one small, trusted plugin so you know whether every installation fails.
After each change, test the same action again. Change one thing at a time so you know what helped and what did not.
A good place to pause
When this leaves normal WordPress editing
Could not create directory means WordPress cannot make or write to a server folder. The repair usually involves storage, ownership, permissions, or the temporary upgrade directory—not the Install button.
If you inherited the website, took over after parting ways with a developer, or normally use WordPress only to add photographs and text, you may have never opened cPanel before. That is normal, but if you are new to backend server configuration, you need to proceed with caution. This is where you can break your site.
You also do not need to end up with more damage than you bargained for just to solve one aggravating problem. The standard repair is $149.00 if you would rather hand it off.
If you are comfortable with backend server configurations, continue with the technical steps below.
Technical checks
- Check disk space and inode usage for the correct hosting account.
- Confirm wp-content/upgrade exists and is writable by the PHP user.
- Verify ownership and permissions on wp-content and the destination plugin directory.
- Check the PHP temporary directory and the server log for the failed installation.
Proceed with caution
Do not use 777 permissions or change ownership recursively across the whole site. Those shortcuts create larger security and stability problems.
Test the repair without making a second problem
- Keep a note of the original setting or filename before you change it.
- Make one change, clear only the relevant cache, and repeat the exact test.
- Check both the public page and the WordPress dashboard.
- If the error changes, stop and record the new message before continuing.
You can hand this off
If these checks have taken you beyond the part of WordPress you normally use, you can stop. I can trace the cause, make the repair, test the site, and tell you what was changed without turning one problem into your new full-time job.