I have a project in laravel 5 in my notebook (windows), I created a repository for it in bitbucket and decided to use on my desktop (ubuntu 14). But for some reason they are showing several errors. And I'm new in version 5, I searched but could not understand the reason for the errors.
My .gitignore:
vendor/
node_modules/
# Laravel 4 specific
bootstrap/compiled.php
app/storage/
# Laravel 5 & Lumen specific
bootstrap/cache/
storage/
.env.*.php
.env.php
.env
# Rocketeer PHP task runner and deployment package. https://github.com/rocketeers/rocketeer
.rocketeer/
After cloning a repository within the htdocs of xampp, I used the following commands:
1) composer install
2) chmod 777 -R storage
3) chmod 777 -R bootstrap
but when opening http://localhost/myProject/public/
Whoops, looks like something went wrong.
1/1 ErrorException in Filesystem.php line 75:
file_put_contents(/opt/lampp/htdocs/myProject/storage/framework/services.json):
failed to open stream: No such file or directory
Run the commands the correct way:
chmod -R 777 storage
chmod -R 777 bootstrap
i.e. the -R flag needs to come after chmod.
Related
I'm having some weird problem with Laravel 8.
I installed the framework and started working with it, but when I try to edit / delete some controller, my Ubuntu asks for a password.
Another problem. My controller displays records on a page with paginate(15) pagination, but instead of the usual numbers, I get the Previous & Next direction, and when I try to change something in the html template, I get an error file_put_contents(/var/www/storage/framework/views/c6d615eb91fe3a0edd449165e94d034703bbb84d.php): failed to open stream: Permission denied and this problem can only be cured by clearing the cache, but this should not be the case.
Error #1: Your user does not have write permissions for those files/directories. Did you use sudo while installing or copying anything? Do you have these files outside of your home directory? (/home/username/)
Error #2: Your webserver (nginx, apache, etc.) probably does not have access to the application's /storage/ directory.
SSH into the server.
Navigate to the projects root folder.
Run the following commands to make the directories writable:
sudo chmod -R gu+w storage/
sudo chmod -R guo+w storage/
sudo chmod -R gu+w bootstrap/cache/
sudo chmod -R guo+w bootstrap/cache/
I am a verry new Leaner of Laravel framework. Laravel works properly on my desktop. I push my laravel project to github and then when i git clone the project, it is not working. Some pages show me run composer update. after i run it, laravel shows errors of 500
Server Error. please help me. I use ubuntu
First you should update your .env file, because it is ignored by git from .gitignore. so you can copy paste .env.example to .env with this command:
cp .env.example .env
And make sure you have given permissions to storage and bootstrap folder.
sudo chgrp -R www-data storage bootstrap/cache
sudo chmod -R ug+rwx storage bootstrap/cache
I hope it will help you. if not then please let me know.
Thanks #AH.Pooladvand for the correction.
By default there are some files in your .gitignore file which will not push into your github repository most important ones are vendor and .env files
so first you should take a copy of your .env.example and make your .env file then set
then run php artisan key:generate to create your application key
and then set proper configuration of .env file like database and etc..
if you are hosting your files in /var/www/something make sure public and storage directory has the proper permissions however hosting files as root user is strongly not recommended
Run these two commands in the directory where Laravel is installed:
sudo chmod 755 -R DIRECTORY_NAME
chmod -R o+w DIRECTORY_NAME/storage
Then clear the cache and dump the auto load:
composer dump-autoload
I've just git clone a repository of mine containing a Laravel 5.1 project. I've gone through the normal steps to get it up and running (setup the webserver, db, etc). I've now gone to the web address I configured and i'm getting the following error message:
ErrorException in compiled.php line 6648:
file_put_contents(/3c7922efc24ab13620cd0f35b1fdaa61): failed to open stream: Permission denied
Any idea's what folder it's trying to access?
I solved the problem with this solution, clarifying that if you have Windows, you apply lines 1 and 3 and it works the same.
php artisan cache:clear
chmod -R 777 storage/
composer dump-autoload
To solve this problem I needed to create a few folder's that were missing from my install. You require the following folders to be readable and writable by your www user:
/storage
/storage/cache
/storage/framework
/storage/framework/sessions
/storage/framework/views
/storage/framework/cache
/storage/logs
Also, set the folder permissions to 775. From the root directory run the command: sudo chmod -R 755 storage
If nothing help you and if you work on windows with docker it can be the issue that wrong symlink you have, you can try:
ln -s /var/www/storage/app/public /var/www/public/storage
And after that:
chown -R $USER:www-data storage
chmod -R 777 storage
on docker bash.
If you're using ubuntu, most likely you have to give permissions to that folder storage
cd into the project and
use the command -> sudo chmod 755 storage/*
I had similar problem in my localhost and the problem was that I was trying to upload a file larger than upload_max_filesize in my php.ini file .
just updating this to greater value and restart my server solved the problem ,, if you having similar problem this might be the case
If you are on a Linux distribution with SELinux enabled, here is what you need to do:
sudo chcon -R -t httpd_sys_rw_content_t /var/www/html/my-app/storage
sudo chown -R nginx /var/www/html/my-app/storage
sudo chmod -R u+w /var/www/html/my-app/storage
This should set the proper context for the storage directory, allowing the web server to write to it.
I had this problem lately with my tests, and resolved it through: composer dump-autoload
This is how I solve a similar issue since I don't have access to the terminal to run sudo chown -R www-data:www-data /thedirectory
in
config/filesystem.php
'public' => [
'driver' => 'local',
'root' => storage_path('app/public'),
'url' => env('APP_URL').'/storage',
'visibility' => 'public',
],
Then in my uploader controller
use Illuminate\Support\Facades\Storage;
$file_path= Storage::path('public/importable');
if (!is_dir($file_path)) {mkdir( $file_path,0775, true);}
This is a permission issue. I used few hours to resolve this problem. I found only 3 lines to give permissions. So first go to root folder f your Laravel application and run these 3 lines.
php artisan cache:clear
chmod -R 777 storage/
composer dump-autoload
For me it was because the single file was owned by root...written at some point when I setup the files, and the app couldn't read it. Solution could be to change ownership, get rid of it, etc.
For me solution was to change folder owner of laravel project. Ensure that is your own user and not root:www-data.
sudo chown -R username:group directory
Run the following command in the directory that is being triggered to check the permissions:
ls -lah
Then if there was any issue you can correct it with:
sudo chown -R username:group directory
To stop you from the start, there is NO permission issue. /storage is recursively chmodded 777 and whole project folder is chowned by apache:apache
I even renamed the log file to ...-old and apache created a new one... if it didn't have actual write permissions it would not had been allowed to create it.
Running under CentOS release 6.6 (Final)
Deployed the project from git, the homestead works for my colleague.
Full error:
[Mon May 18 10:17:58 2015] [error] [client 86.124.208.14] PHP Fatal
error: Uncaught exception 'UnexpectedValueException' with message
'The stream or file
"/var/www/vhosts/mapper.pavementlayers.com/storage/logs/laravel-2015-05-18.log"
could not be opened: failed to open stream: Permission denied' in
/var/www/vhosts/mapper.pavementlayers.com/vendor/monolog/monolog/src/Monolog/Handler/StreamHandler.php:84\nStack
trace:\n#0
/var/www/vhosts/mapper.pavementlayers.com/vendor/monolog/monolog/src/Monolog/Handler/RotatingFileHandler.php(88):
Monolog\Handler\StreamHandler->write(Array)\n#1
/var/www/vhosts/mapper.pavementlayers.com/vendor/monolog/monolog/src/Monolog/Handler/AbstractProcessingHandler.php(37):
Monolog\Handler\RotatingFileHandler->write(Array)\n#2
/var/www/vhosts/mapper.pavementlayers.com/vendor/monolog/monolog/src/Monolog/Logger.php(265):
Monolog\Handler\AbstractProcessingHandler->handle(Array)\n#3
/var/www/vhosts/mapper.pavementlayers.com/vendor/monolog/monolog/src/Monolog/Logger.php(543):
Monolog\Logger->addRecord(400, 'exception 'Symf...', Array)\n#4
/var/www/vhosts/mapper.pavementl in
/var/www/vhosts/mapper.pavementlayers.com/vendor/monolog/monolog/src/Monolog/Handler/StreamHandler.php
on line 84
It could be that SElinux is preventing Apache from creating this file.
To test this you could disable SElinux temporally with the following command:
setenforce 0
This will place SElinux in permissive mode. This means that you still receive an error message in your SElinux log file but SElinux will not block the command.
To activate SElinux again you can type:
setenforce 1
Or reboot your CentOS server.
Unfortunately, I had also problems with Laravel 5 on CentOS and the cause was SElinux.
I ended up with disabling SElinux. I know it is not the right thing to do but I haven't had time to get the two working together yet!
Update
So I finally had sometime to investigate this further and I got SELinux working together with Laravel 5. I have just updated this post for people that might run into this issue cause. Disabling SELinux is not the best strategy as mentioned above.
Three things need to be done:
The folders Storage and Bootstrap/Cache need to have the right SELinux context. This can be achieved via the following commands:
semanage fcontext -a -t httpd_sys_rw_content_t "/var/www/<Laravel Site>/storage(/.*)?"
semanage fcontext -a -t httpd_sys_rw_content_t "/var/www/<Laravel Site>/bootstrap/cache(/.*)?"
The SELinux context needs to be applied on the directories:
restorecon -Rv "/var/www/<Laravel Site>/storage"
restorecon -Rv "/var/www/<Laravel Site>/bootstrap/cache"
The Apache user needs to have the rights to create files in both directories. This can be achieved via a ACL in CentOS 7:
setfacl -R -m u:apache:rwX storage/
setfacl -R -m u:apache:rwX bootstrap/cache/
The last thing you need to do is to enable SELinux again.
Try those commands for laravel 5
$ php artisan cache:clear
$ sudo chmod -R 777 app/storage
$ composer.phar dump-autoload
This happens because laravel do not have the permissions to write to the log file, at least for my case.
This worked for me, Laravel 5.4 and above
$ sudo chmod -R 755 storage/
$ sudo chown -R www-data storage/
$ sudo chgrp -R www-data storage/
$ php artisan cache:clear
$ php artisan config:cache
$ composer dumpautoload
Not all steps necessary.
You have to make sure the storage folder exists. If you're deploying from git, make sure the storage folder itself is tracked and created automatically.
ON Laravel 5.7
$ cd /var/www/html/
$ php artisan cache:clear
Application cache cleared!
for centos 7
# ausearch -c 'httpd' --raw | audit2allow -M my-httpd
# semodule -i my-httpd.pp
Since laravel.log is in the storage folder, so I will suggest you run this command on your terminal on Mac.
chmod -Rf 0777 storage
I have the latest Laravel 4 beta 5 build from Laravel's github repo.
I have built a simple web API and it is working fine. I wanted to duplicate the project to another folder and continue working on it from the copy. However, when I try that, I get the following error message:
InvalidArgumentException
Driver [native] not supported.
/Users/tolga/Sites/l4api-copy/bootstrap/compiled.php
Line 10908: throw new \InvalidArgumentException("Driver [{$driver}] not supported.");
Here is what I did in order to copy the project:
[/Users/tolga/Sites] $ cp -R l4api l4api-copy
[/Users/tolga/Sites] $ chmod -R 755 l4api-copy
It didn't work, so I've tried:
[/Users/tolga/Sites] $ chmod -R 777 l4api-copy/app/storage
Still no good, tried to run composer dump-autoload:
[/Users/tolga/Sites] $ cd l4api-copy
[/Users/tolga/Sites/l4api-copy] $ composer.phar dump-autoload
Generating autoload files
[/Users/tolga/Sites/l4api-copy] $
Same error. I have also tried to remove the app/storage folder and re-create it.
[/Users/tolga/Sites/l4api-copy] $ rm -Rf app/storage
[/Users/tolga/Sites/l4api-copy] $ mkdir app/storage
[/Users/tolga/Sites/l4api-copy] $ chmod -R 777 app/storage/
Here is a brand-new error:
ErrorException
Warning: file_put_contents(/Users/tolga/Sites/l4api-copy/bootstrap/../app/storage/meta/services.json):
failed to open stream: No such file or directory in
/Users/tolga/Sites/l4api-copy/bootstrap/compiled.php line 5507
Line 5507: return file_put_contents($path, $contents);
I have also run composer.phar dump-autoload command again, after emptying the app/storage folder.
And finally, I have also tried composer.phar install:
[/Users/tolga/Sites/l4api-copy] $ composer.phar install
Loading composer repositories with package information
Installing dependencies from lock file
Nothing to install or update
Generating autoload files
[/Users/tolga/Sites/l4api-copy] $
None of the above helped. What am I doing wrong? What is the proper way to duplicate a working project?
After a recent commit to the laravel/laravel repository a new session driver, native, has been introduced. From the looks of your errors you should update your application skeleton (the cloned develop branch of laravel/laravel), delete your bootstrap/compiled.php file and re-run composer update to pull in the latest framework changes.
In terms of copying the project you should copy over everything except the vendor directory then run composer install in the new location. You could copy the vendor directory but it's better to run a clean install and let composer dump a new autoload.
I've also seen Taylor mention a cleanup of your app/storage/sessions directory. Delete all the files in there.