Hey,
I was working on this project, setting up some custom gulp / elixir tasks, got browsersync up and running as an elixir task and then I stopped there. After a few hours I came back to continue and when I ran browsersync, I saw 403 Forbidden. So I opened myapp.dev:8000 and I see the same thing there.
Opened 2 other projects that are up on homestead and they work normally but the project I am currently working on is forbidden.
Does anyone know what could be the problem? Where can I find the logs?
You may take a look at your nginx and php5-fpm error log:
nginx
sudo cat var/log/nginx/yoursite.tld-error.log
// and
sudo cat var/log/nginx/error.log
The error log of your homestead site is declared in your sites nginx config which is located here:
/etc/nginx/sites-available
In your domains config file you have the line error_log /var/log/nginx/domain.tld-error.log error;
For PHP the log file is located at:
sudo cat var/log/php5-fpm.log
Ok so I saw that line inside of the folder sites-available but I can't seem to find the var/log/nginx directory.
Ok, I was curious to see if a new project will work, so I created a new project, copied my files into it and when I ran gulp with my browser-sync elixir extension, it did something to the project, so it's forbidden again!
I still can't figure out why my apps become forbidden when I run my gulp extension browsersync and how to get my app back to normal after being fobidden. It is weird because, before I transform the browsersync task into an elixir extension, it worked perfectly fine, so I did a little bit of a refactoring to clean up some code and it started "Forbidding" my applications when I run gulp with mix.browserSync() inside of my gulpfile.js.
If you have a copy task, you might have files with strict permissions, so that it only can be read by you, not by the user the web server is running as. At least that's what happened to me (Linux).
Comment out browserSync in your gulpfile to see if the error persists.
Please or to participate in this conversation.