laravel centOS 7 chmod 755/775 permission denied“could not be opened: failed to open stream: Permission...
up vote
-1
down vote
favorite
I have linux:
Linux version 3.10.0-693.21.1.el7.x86_64
(builder@kbuilder.dev.centos.org) (gcc version 4.8.5 20150623 (Red Hat
4.8.5-16) (GCC) ) #1 SMP Wed Mar 7 19:03:37 UTC 2018
If I set the permission to 777 on storage, laravel works, but if I set it to 755 or 775 it says:
"The stream or file
"/home/admin/domains/linkshift.eu/public_html/storage/logs/laravel-2018-11-08.log"
could not be opened: failed to open stream: Permission denied"
I have tried searching for an answer, but nothing else worked, I have tried doing
Permissions Issue with Laravel on CentOS
but it still doesn't work
Edit: I also have direct admin installed
linux laravel centos7
asked Nov 8 at 9:39
Aivaras77
13
New contributor
Aivaras77 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
-1
down vote
favorite
I have linux:
Linux version 3.10.0-693.21.1.el7.x86_64
(builder@kbuilder.dev.centos.org) (gcc version 4.8.5 20150623 (Red Hat
4.8.5-16) (GCC) ) #1 SMP Wed Mar 7 19:03:37 UTC 2018
If I set the permission to 777 on storage, laravel works, but if I set it to 755 or 775 it says:
"The stream or file
"/home/admin/domains/linkshift.eu/public_html/storage/logs/laravel-2018-11-08.log"
could not be opened: failed to open stream: Permission denied"
I have tried searching for an answer, but nothing else worked, I have tried doing
Permissions Issue with Laravel on CentOS
but it still doesn't work
Edit: I also have direct admin installed
linux laravel centos7
asked Nov 8 at 9:39
Aivaras77
13
New contributor
Aivaras77 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Stackoverflow is about helping programers. This is more suited for super user community - superuser.com
– tukan
Nov 8 at 9:41
I am a programmer, I am just trying to host laravel on a dedicated server
– Aivaras77
Nov 8 at 9:43
But ok I will make a thread there, thank you for the link
– Aivaras77
Nov 8 at 9:44
I'm not saying, by any means, that you are not programmer. I just think the question does not have any programming question.
– tukan
Nov 8 at 10:11
add a comment |
up vote
-1
down vote
favorite
up vote
-1
down vote
favorite
I have linux:
Linux version 3.10.0-693.21.1.el7.x86_64
(builder@kbuilder.dev.centos.org) (gcc version 4.8.5 20150623 (Red Hat
4.8.5-16) (GCC) ) #1 SMP Wed Mar 7 19:03:37 UTC 2018
If I set the permission to 777 on storage, laravel works, but if I set it to 755 or 775 it says:
"The stream or file
"/home/admin/domains/linkshift.eu/public_html/storage/logs/laravel-2018-11-08.log"
could not be opened: failed to open stream: Permission denied"
I have tried searching for an answer, but nothing else worked, I have tried doing
Permissions Issue with Laravel on CentOS
but it still doesn't work
Edit: I also have direct admin installed
linux laravel centos7
asked Nov 8 at 9:39
Aivaras77
13
New contributor
Aivaras77 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I have linux:
Linux version 3.10.0-693.21.1.el7.x86_64
(builder@kbuilder.dev.centos.org) (gcc version 4.8.5 20150623 (Red Hat
4.8.5-16) (GCC) ) #1 SMP Wed Mar 7 19:03:37 UTC 2018
If I set the permission to 777 on storage, laravel works, but if I set it to 755 or 775 it says:
"The stream or file
"/home/admin/domains/linkshift.eu/public_html/storage/logs/laravel-2018-11-08.log"
could not be opened: failed to open stream: Permission denied"
I have tried searching for an answer, but nothing else worked, I have tried doing
Permissions Issue with Laravel on CentOS
but it still doesn't work
Edit: I also have direct admin installed
linux laravel centos7
linux laravel centos7
asked Nov 8 at 9:39
Aivaras77
13
New contributor
Aivaras77 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Nov 8 at 9:39
Aivaras77
13
New contributor
Aivaras77 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited Nov 8 at 10:53
asked Nov 8 at 9:39
Aivaras77
13
New contributor
Aivaras77 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Nov 8 at 9:39
Aivaras77
13
asked Nov 8 at 9:39
Aivaras77
13
13
New contributor
Aivaras77 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Aivaras77 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Aivaras77 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Stackoverflow is about helping programers. This is more suited for super user community - superuser.com
– tukan
Nov 8 at 9:41
I am a programmer, I am just trying to host laravel on a dedicated server
– Aivaras77
Nov 8 at 9:43
But ok I will make a thread there, thank you for the link
– Aivaras77
Nov 8 at 9:44
I'm not saying, by any means, that you are not programmer. I just think the question does not have any programming question.
– tukan
Nov 8 at 10:11
add a comment |
Stackoverflow is about helping programers. This is more suited for super user community - superuser.com
– tukan
Nov 8 at 9:41
I am a programmer, I am just trying to host laravel on a dedicated server
– Aivaras77
Nov 8 at 9:43
But ok I will make a thread there, thank you for the link
– Aivaras77
Nov 8 at 9:44
I'm not saying, by any means, that you are not programmer. I just think the question does not have any programming question.
– tukan
Nov 8 at 10:11
Stackoverflow is about helping programers. This is more suited for super user community - superuser.com
– tukan
Nov 8 at 9:41
Stackoverflow is about helping programers. This is more suited for super user community - superuser.com
– tukan
Nov 8 at 9:41
I am a programmer, I am just trying to host laravel on a dedicated server
– Aivaras77
Nov 8 at 9:43
I am a programmer, I am just trying to host laravel on a dedicated server
– Aivaras77
Nov 8 at 9:43
But ok I will make a thread there, thank you for the link
– Aivaras77
Nov 8 at 9:44
But ok I will make a thread there, thank you for the link
– Aivaras77
Nov 8 at 9:44
I'm not saying, by any means, that you are not programmer. I just think the question does not have any programming question.
– tukan
Nov 8 at 10:11
I'm not saying, by any means, that you are not programmer. I just think the question does not have any programming question.
– tukan
Nov 8 at 10:11
add a comment |
2 Answers
2
active
oldest
votes
up vote
0
down vote
Look like the log file is generated using root user and you are running the laravel from a different user. Make sure the log file is written by same user. Or give permission to your user.
sudo chown -R laravel-user:laravel-user /path/to/your/laravel/root/directory
Run these commands after every deploy
chmod -R 775 storage/framework
chmod -R 775 storage/logs
chmod -R 775 bootstrap/cache
Still If not working, It can maybe also because of SELinux.
Check selinux status on terminal:
sestatus
If status is enabled, write command for disable SElinux( Not reccommended)
setenforce Permissive
or you can do linke below.
yum install policycoreutils-python -y # might not be necessary, try the below first
semanage fcontext -a -t httpd_sys_rw_content_t "/path/to/your/laravel/root/directory/storage(/.*)?" # add a new httpd read write content to sellinux for the specific folder, -m for modify
semanage fcontext -a -t httpd_sys_rw_content_t "/path/to/your/laravel/root/directory/bootstrap/cache(/.*)?" # same as the above for b/cache
restorecon -Rv /var/www/html/ # this command is very important to, it's like a restart to apply the new rules
Selinux is intended to restrict access even to root users, so only the necessary stuff might be accessed, at least on a generalist overview, it's extra security, disabling it is not a good practise, there are many links to learn Selinux, but for this case it is not even required.
answered Nov 8 at 10:00
Jestin Sebastian
19610
How can I do that? How do I check which user it is ran by?
– Aivaras77
Nov 8 at 10:16
See the updated answer
– Jestin Sebastian
Nov 8 at 10:34
setenforce: SELinux is disabled and it still does not work, should I try to turn it on and then run the commands?
– Aivaras77
Nov 8 at 10:46
Run thissudo chown -R laravel-user:laravel-user /path/to/your/laravel/root/directory
– Jestin Sebastian
Nov 8 at 10:48
Also I am running it on super user, I have not created any users
– Aivaras77
Nov 8 at 10:48
|
show 6 more comments
up vote
-1
down vote
Could you show the result of
ls -l /home/admin/domains/linkshift.eu/public_html/storage/logs
and have you tried
php artisan config:cache
php artisan config:clear
composer dump-autoload -o
answered Nov 8 at 9:54
Mou Hsiao
344
total 16 -rwxrwxrwx. 1 apache apache 14827 Nov 8 03:02 laravel-2018-11-08.log
– Aivaras77
Nov 8 at 10:16
I tried everything after doing chmod -R 775 storage, but still The stream or file "/home/admin/domains/linkshift.eu/public_html/storage/logs/laravel-2018-11-08.log" could not be opened: failed to open stream: Permission denied
– Aivaras77
Nov 8 at 10:19
to confirm the name of user of your http server (which is assumed to be apache:apache here), try delete laravel-2018-11-09.log, and set the permission to 777 on storage again, then trigger a execution which writes logs to let apache create a new laravel-2018-11-09.log, and then do ls -l again to see its ownership?
– Mou Hsiao
Nov 8 at 16:38
"total 0" is the output after I did what you said
– Aivaras77
Nov 8 at 18:43
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Look like the log file is generated using root user and you are running the laravel from a different user. Make sure the log file is written by same user. Or give permission to your user.
sudo chown -R laravel-user:laravel-user /path/to/your/laravel/root/directory
Run these commands after every deploy
chmod -R 775 storage/framework
chmod -R 775 storage/logs
chmod -R 775 bootstrap/cache
Still If not working, It can maybe also because of SELinux.
Check selinux status on terminal:
sestatus
If status is enabled, write command for disable SElinux( Not reccommended)
setenforce Permissive
or you can do linke below.
yum install policycoreutils-python -y # might not be necessary, try the below first
semanage fcontext -a -t httpd_sys_rw_content_t "/path/to/your/laravel/root/directory/storage(/.*)?" # add a new httpd read write content to sellinux for the specific folder, -m for modify
semanage fcontext -a -t httpd_sys_rw_content_t "/path/to/your/laravel/root/directory/bootstrap/cache(/.*)?" # same as the above for b/cache
restorecon -Rv /var/www/html/ # this command is very important to, it's like a restart to apply the new rules
Selinux is intended to restrict access even to root users, so only the necessary stuff might be accessed, at least on a generalist overview, it's extra security, disabling it is not a good practise, there are many links to learn Selinux, but for this case it is not even required.
answered Nov 8 at 10:00
Jestin Sebastian
19610
How can I do that? How do I check which user it is ran by?
– Aivaras77
Nov 8 at 10:16
See the updated answer
– Jestin Sebastian
Nov 8 at 10:34
setenforce: SELinux is disabled and it still does not work, should I try to turn it on and then run the commands?
– Aivaras77
Nov 8 at 10:46
Run thissudo chown -R laravel-user:laravel-user /path/to/your/laravel/root/directory
– Jestin Sebastian
Nov 8 at 10:48
Also I am running it on super user, I have not created any users
– Aivaras77
Nov 8 at 10:48
|
show 6 more comments
up vote
0
down vote
Look like the log file is generated using root user and you are running the laravel from a different user. Make sure the log file is written by same user. Or give permission to your user.
sudo chown -R laravel-user:laravel-user /path/to/your/laravel/root/directory
Run these commands after every deploy
chmod -R 775 storage/framework
chmod -R 775 storage/logs
chmod -R 775 bootstrap/cache
Still If not working, It can maybe also because of SELinux.
Check selinux status on terminal:
sestatus
If status is enabled, write command for disable SElinux( Not reccommended)
setenforce Permissive
or you can do linke below.
yum install policycoreutils-python -y # might not be necessary, try the below first
semanage fcontext -a -t httpd_sys_rw_content_t "/path/to/your/laravel/root/directory/storage(/.*)?" # add a new httpd read write content to sellinux for the specific folder, -m for modify
semanage fcontext -a -t httpd_sys_rw_content_t "/path/to/your/laravel/root/directory/bootstrap/cache(/.*)?" # same as the above for b/cache
restorecon -Rv /var/www/html/ # this command is very important to, it's like a restart to apply the new rules
Selinux is intended to restrict access even to root users, so only the necessary stuff might be accessed, at least on a generalist overview, it's extra security, disabling it is not a good practise, there are many links to learn Selinux, but for this case it is not even required.
answered Nov 8 at 10:00
Jestin Sebastian
19610
How can I do that? How do I check which user it is ran by?
– Aivaras77
Nov 8 at 10:16
See the updated answer
– Jestin Sebastian
Nov 8 at 10:34
setenforce: SELinux is disabled and it still does not work, should I try to turn it on and then run the commands?
– Aivaras77
Nov 8 at 10:46
Run thissudo chown -R laravel-user:laravel-user /path/to/your/laravel/root/directory
– Jestin Sebastian
Nov 8 at 10:48
Also I am running it on super user, I have not created any users
– Aivaras77
Nov 8 at 10:48
|
show 6 more comments
up vote
0
down vote
up vote
0
down vote
Look like the log file is generated using root user and you are running the laravel from a different user. Make sure the log file is written by same user. Or give permission to your user.
sudo chown -R laravel-user:laravel-user /path/to/your/laravel/root/directory
Run these commands after every deploy
chmod -R 775 storage/framework
chmod -R 775 storage/logs
chmod -R 775 bootstrap/cache
Still If not working, It can maybe also because of SELinux.
Check selinux status on terminal:
sestatus
If status is enabled, write command for disable SElinux( Not reccommended)
setenforce Permissive
or you can do linke below.
yum install policycoreutils-python -y # might not be necessary, try the below first
semanage fcontext -a -t httpd_sys_rw_content_t "/path/to/your/laravel/root/directory/storage(/.*)?" # add a new httpd read write content to sellinux for the specific folder, -m for modify
semanage fcontext -a -t httpd_sys_rw_content_t "/path/to/your/laravel/root/directory/bootstrap/cache(/.*)?" # same as the above for b/cache
restorecon -Rv /var/www/html/ # this command is very important to, it's like a restart to apply the new rules
Selinux is intended to restrict access even to root users, so only the necessary stuff might be accessed, at least on a generalist overview, it's extra security, disabling it is not a good practise, there are many links to learn Selinux, but for this case it is not even required.
answered Nov 8 at 10:00
Jestin Sebastian
19610
Look like the log file is generated using root user and you are running the laravel from a different user. Make sure the log file is written by same user. Or give permission to your user.
sudo chown -R laravel-user:laravel-user /path/to/your/laravel/root/directory
Run these commands after every deploy
chmod -R 775 storage/framework
chmod -R 775 storage/logs
chmod -R 775 bootstrap/cache
Still If not working, It can maybe also because of SELinux.
Check selinux status on terminal:
sestatus
If status is enabled, write command for disable SElinux( Not reccommended)
setenforce Permissive
or you can do linke below.
yum install policycoreutils-python -y # might not be necessary, try the below first
semanage fcontext -a -t httpd_sys_rw_content_t "/path/to/your/laravel/root/directory/storage(/.*)?" # add a new httpd read write content to sellinux for the specific folder, -m for modify
semanage fcontext -a -t httpd_sys_rw_content_t "/path/to/your/laravel/root/directory/bootstrap/cache(/.*)?" # same as the above for b/cache
restorecon -Rv /var/www/html/ # this command is very important to, it's like a restart to apply the new rules
Selinux is intended to restrict access even to root users, so only the necessary stuff might be accessed, at least on a generalist overview, it's extra security, disabling it is not a good practise, there are many links to learn Selinux, but for this case it is not even required.
answered Nov 8 at 10:00
Jestin Sebastian
19610
edited Nov 8 at 10:40
answered Nov 8 at 10:00
Jestin Sebastian
19610
answered Nov 8 at 10:00
Jestin Sebastian
19610
answered Nov 8 at 10:00
Jestin Sebastian
19610
19610
How can I do that? How do I check which user it is ran by?
– Aivaras77
Nov 8 at 10:16
See the updated answer
– Jestin Sebastian
Nov 8 at 10:34
setenforce: SELinux is disabled and it still does not work, should I try to turn it on and then run the commands?
– Aivaras77
Nov 8 at 10:46
Run thissudo chown -R laravel-user:laravel-user /path/to/your/laravel/root/directory
– Jestin Sebastian
Nov 8 at 10:48
Also I am running it on super user, I have not created any users
– Aivaras77
Nov 8 at 10:48
|
show 6 more comments
How can I do that? How do I check which user it is ran by?
– Aivaras77
Nov 8 at 10:16
See the updated answer
– Jestin Sebastian
Nov 8 at 10:34
setenforce: SELinux is disabled and it still does not work, should I try to turn it on and then run the commands?
– Aivaras77
Nov 8 at 10:46
Run thissudo chown -R laravel-user:laravel-user /path/to/your/laravel/root/directory
– Jestin Sebastian
Nov 8 at 10:48
Also I am running it on super user, I have not created any users
– Aivaras77
Nov 8 at 10:48
How can I do that? How do I check which user it is ran by?
– Aivaras77
Nov 8 at 10:16
How can I do that? How do I check which user it is ran by?
– Aivaras77
Nov 8 at 10:16
See the updated answer
– Jestin Sebastian
Nov 8 at 10:34
See the updated answer
– Jestin Sebastian
Nov 8 at 10:34
setenforce: SELinux is disabled and it still does not work, should I try to turn it on and then run the commands?
– Aivaras77
Nov 8 at 10:46
setenforce: SELinux is disabled and it still does not work, should I try to turn it on and then run the commands?
– Aivaras77
Nov 8 at 10:46
Run this
sudo chown -R laravel-user:laravel-user /path/to/your/laravel/root/directory– Jestin Sebastian
Nov 8 at 10:48
Run this
sudo chown -R laravel-user:laravel-user /path/to/your/laravel/root/directory– Jestin Sebastian
Nov 8 at 10:48
Also I am running it on super user, I have not created any users
– Aivaras77
Nov 8 at 10:48
Also I am running it on super user, I have not created any users
– Aivaras77
Nov 8 at 10:48
|
show 6 more comments
up vote
-1
down vote
Could you show the result of
ls -l /home/admin/domains/linkshift.eu/public_html/storage/logs
and have you tried
php artisan config:cache
php artisan config:clear
composer dump-autoload -o
answered Nov 8 at 9:54
Mou Hsiao
344
total 16 -rwxrwxrwx. 1 apache apache 14827 Nov 8 03:02 laravel-2018-11-08.log
– Aivaras77
Nov 8 at 10:16
I tried everything after doing chmod -R 775 storage, but still The stream or file "/home/admin/domains/linkshift.eu/public_html/storage/logs/laravel-2018-11-08.log" could not be opened: failed to open stream: Permission denied
– Aivaras77
Nov 8 at 10:19
to confirm the name of user of your http server (which is assumed to be apache:apache here), try delete laravel-2018-11-09.log, and set the permission to 777 on storage again, then trigger a execution which writes logs to let apache create a new laravel-2018-11-09.log, and then do ls -l again to see its ownership?
– Mou Hsiao
Nov 8 at 16:38
"total 0" is the output after I did what you said
– Aivaras77
Nov 8 at 18:43
add a comment |
up vote
-1
down vote
Could you show the result of
ls -l /home/admin/domains/linkshift.eu/public_html/storage/logs
and have you tried
php artisan config:cache
php artisan config:clear
composer dump-autoload -o
answered Nov 8 at 9:54
Mou Hsiao
344
total 16 -rwxrwxrwx. 1 apache apache 14827 Nov 8 03:02 laravel-2018-11-08.log
– Aivaras77
Nov 8 at 10:16
I tried everything after doing chmod -R 775 storage, but still The stream or file "/home/admin/domains/linkshift.eu/public_html/storage/logs/laravel-2018-11-08.log" could not be opened: failed to open stream: Permission denied
– Aivaras77
Nov 8 at 10:19
to confirm the name of user of your http server (which is assumed to be apache:apache here), try delete laravel-2018-11-09.log, and set the permission to 777 on storage again, then trigger a execution which writes logs to let apache create a new laravel-2018-11-09.log, and then do ls -l again to see its ownership?
– Mou Hsiao
Nov 8 at 16:38
"total 0" is the output after I did what you said
– Aivaras77
Nov 8 at 18:43
add a comment |
up vote
-1
down vote
up vote
-1
down vote
Could you show the result of
ls -l /home/admin/domains/linkshift.eu/public_html/storage/logs
and have you tried
php artisan config:cache
php artisan config:clear
composer dump-autoload -o
answered Nov 8 at 9:54
Mou Hsiao
344
Could you show the result of
ls -l /home/admin/domains/linkshift.eu/public_html/storage/logs
and have you tried
php artisan config:cache
php artisan config:clear
composer dump-autoload -o
answered Nov 8 at 9:54
Mou Hsiao
344
edited Nov 8 at 10:05
answered Nov 8 at 9:54
Mou Hsiao
344
answered Nov 8 at 9:54
Mou Hsiao
344
answered Nov 8 at 9:54
Mou Hsiao
344
344
total 16 -rwxrwxrwx. 1 apache apache 14827 Nov 8 03:02 laravel-2018-11-08.log
– Aivaras77
Nov 8 at 10:16
I tried everything after doing chmod -R 775 storage, but still The stream or file "/home/admin/domains/linkshift.eu/public_html/storage/logs/laravel-2018-11-08.log" could not be opened: failed to open stream: Permission denied
– Aivaras77
Nov 8 at 10:19
to confirm the name of user of your http server (which is assumed to be apache:apache here), try delete laravel-2018-11-09.log, and set the permission to 777 on storage again, then trigger a execution which writes logs to let apache create a new laravel-2018-11-09.log, and then do ls -l again to see its ownership?
– Mou Hsiao
Nov 8 at 16:38
"total 0" is the output after I did what you said
– Aivaras77
Nov 8 at 18:43
add a comment |
total 16 -rwxrwxrwx. 1 apache apache 14827 Nov 8 03:02 laravel-2018-11-08.log
– Aivaras77
Nov 8 at 10:16
I tried everything after doing chmod -R 775 storage, but still The stream or file "/home/admin/domains/linkshift.eu/public_html/storage/logs/laravel-2018-11-08.log" could not be opened: failed to open stream: Permission denied
– Aivaras77
Nov 8 at 10:19
to confirm the name of user of your http server (which is assumed to be apache:apache here), try delete laravel-2018-11-09.log, and set the permission to 777 on storage again, then trigger a execution which writes logs to let apache create a new laravel-2018-11-09.log, and then do ls -l again to see its ownership?
– Mou Hsiao
Nov 8 at 16:38
"total 0" is the output after I did what you said
– Aivaras77
Nov 8 at 18:43
total 16 -rwxrwxrwx. 1 apache apache 14827 Nov 8 03:02 laravel-2018-11-08.log
– Aivaras77
Nov 8 at 10:16
total 16 -rwxrwxrwx. 1 apache apache 14827 Nov 8 03:02 laravel-2018-11-08.log
– Aivaras77
Nov 8 at 10:16
I tried everything after doing chmod -R 775 storage, but still The stream or file "/home/admin/domains/linkshift.eu/public_html/storage/logs/laravel-2018-11-08.log" could not be opened: failed to open stream: Permission denied
– Aivaras77
Nov 8 at 10:19
I tried everything after doing chmod -R 775 storage, but still The stream or file "/home/admin/domains/linkshift.eu/public_html/storage/logs/laravel-2018-11-08.log" could not be opened: failed to open stream: Permission denied
– Aivaras77
Nov 8 at 10:19
to confirm the name of user of your http server (which is assumed to be apache:apache here), try delete laravel-2018-11-09.log, and set the permission to 777 on storage again, then trigger a execution which writes logs to let apache create a new laravel-2018-11-09.log, and then do ls -l again to see its ownership?
– Mou Hsiao
Nov 8 at 16:38
to confirm the name of user of your http server (which is assumed to be apache:apache here), try delete laravel-2018-11-09.log, and set the permission to 777 on storage again, then trigger a execution which writes logs to let apache create a new laravel-2018-11-09.log, and then do ls -l again to see its ownership?
– Mou Hsiao
Nov 8 at 16:38
"total 0" is the output after I did what you said
– Aivaras77
Nov 8 at 18:43
"total 0" is the output after I did what you said
– Aivaras77
Nov 8 at 18:43
add a comment |
Aivaras77 is a new contributor. Be nice, and check out our Code of Conduct.
Aivaras77 is a new contributor. Be nice, and check out our Code of Conduct.
Aivaras77 is a new contributor. Be nice, and check out our Code of Conduct.
Aivaras77 is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53205011%2flaravel-centos-7-chmod-755-775-permission-deniedcould-not-be-opened-failed-to%23new-answer', 'question_page');
}
);
Post as a guest
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Stackoverflow is about helping programers. This is more suited for super user community - superuser.com
– tukan
Nov 8 at 9:41
I am a programmer, I am just trying to host laravel on a dedicated server
– Aivaras77
Nov 8 at 9:43
But ok I will make a thread there, thank you for the link
– Aivaras77
Nov 8 at 9:44
I'm not saying, by any means, that you are not programmer. I just think the question does not have any programming question.
– tukan
Nov 8 at 10:11