File permissions control which users can read, write, or execute files on your website. Incorrect permissions can stop uploads, break updates, expose private files, or leave the site writable in places it should not be.
Common Signs of a Permission Problem
- WordPress, Joomla, or another CMS cannot upload media.
- Plugin, theme, or extension updates fail while downloading or extracting files.
- The site shows a 403 Forbidden error for files that should be public.
- Cache, logs, or temporary files are not being written.
- An application reports that a directory is not writable during installation.
Check the Exact File or Directory
Start with the path named in the error message. If there is no clear path, check the application log and the website error log first. Do not change the whole website recursively unless you understand what the application expects.
In Enhance, open the website, then use File Manager or SFTP to inspect the relevant file or folder. For uploads and cache directories, the application usually needs write access. For normal PHP files, broad write access is usually unnecessary.
Avoid 777 Permissions
Setting files or folders to 777 makes them writable by everyone on the system. It may appear to fix an installer or upload problem, but it is not a safe long-term fix.
Use the narrowest permission that works for the application. A common pattern is:
- Files: readable by the web server and writable only where the application genuinely needs to update them.
- Directories: executable so they can be entered, with write access only for upload, cache, session, or storage paths.
- Configuration files: not publicly writable after installation.
Check Ownership Too
Permissions and ownership work together. If files were uploaded by a different user, copied from another account, or restored from a backup, the permission numbers may look reasonable while the owner is still wrong.
If a restore or migration leaves files owned incorrectly, open a support ticket with the affected website, path, and error message. Ownership fixes should be handled carefully so private files do not become exposed.
After Changing Permissions
- Retry the exact action that failed.
- Check the website error log for a new message.
- Remove any temporary installer files.
- Confirm configuration files are not left broadly writable.
- Take a fresh backup once the site is working normally.
Rule of thumb: permissions should solve a specific error, not be used as a blanket fix. If the only fix seems to be 777, stop and check ownership, paths, and logs first.