Laravel: file_put_contents() permission denied — correct storage/framework/cache permissions?
Stefan Izdrail
Founder & Senior Architect · 2026-06-29
Title: Laravel: Solving Permission Issues with File Operations in Cache Storage
Body:
Dealing with file operations such as writing to or reading from a cache file is an integral part of any web application, particularly when using frameworks like Laravel. However, it's not uncommon for developers to encounter permission errors while manipulating data stored within the cache folder. In this comprehensive blog post, we will dive deeper into these issues and provide you with the necessary steps to set up proper permissions on your storage and framework cache folders.
Background
Before getting into the actual solutions for the permission issues, let's first understand the Laravel architecture. By default, Laravel runs as a web server process with a user account, such as www-data or another specified user depending on your setup. The code is executed under this user context, and it's essential to manage permissions accordingly so that your application can correctly manipulate files in its storage directories.Common Issues
One of the most common issues that users experience is thePermission denied error when trying to create a new file or edit an existing one within Laravel's cache folder. This usually occurs due to incorrect ownership or file access permissions in the storage/framework/cache directory. The root cause may stem from the default 'write' permission set, inconsistent user account management, or even incorrect chown commands that may have been executed by a previous setup.
Solutions
To resolve this issue, follow these steps: 1. Ensure your application is running as the intended user (e.g., www-data). You can execute thewhoami command to check your current account and change it using the commands below, if necessary:
- For root user: sudo su
- For non-root user: su -
2. Run the following chown command to set the correct ownership for all files and folders in your Laravel application:
sudo chown -R www-data:www-data /path/to/laravel-app
3. Ensure that the required executable file permissions are set correctly:
/path/to/laravel-app: Set to755(Read, Write and Execute for owner, Read and Write for group and others)/path/to/laravel-app/storage: Set to770(Read, Write for owner, Read and Write for group, no access for other users)
ls -lh /storage/framework/cache'drwxrwsr-x 55 www-data www-data 4.0K Jan 18 20:56 data', this means your cache folder has the correct permissions. However, if it starts with d--w--w- or any other restrictive settings, follow these steps to fix them:
- If you are using nginx: Run the command sudo chmod 775 /home/<user>/<laravel folder>/storage
- If you are using Apache or any other web server that runs with root privileges: Run the command sudo chown -R www-data:www-data storage inside your Laravel app directory to set the correct user ownership, then adjust permissions recursively for all files and directories in the storage folder using chmod 775.