How do you fix "No input file specified"?

Did you update homestead by any chance? No input file specified usually shows up when you try and connect to a hostname nginx isn't configured to serve.

@deringer I may have, I type "brew update", and "composer update", every few days from my home directory. If I did, what would the steps be that I would need to take to fix this?

I did just notice that I am running php5 in vagrant and outside of vagrant, so on my computer and not in the VM, I am running php 7. Could this be playing a part in all of this?

SSH into your homestead environment and run ls /etc/nginx/sites-available. Do you see the domain you're trying to access listed there?

No input file specified is exactly that. Nginx can not find a index or home file to load. In other words nginx isn't pointed to laravels public folder correctly for the url your trying to access. That's it.

So your homestead.yaml file is wrong (99% of the time) in forwarding the url to the proper folder.

The command etc/nginx/sites-available wont work. I get the error -bash: /etc/nginx/sites-available: Is a directory If I use "sudo nano /etc/hosts" from my home directory I see it. And when I check to make sure export PATH="$PATH:$HOME/.composer/vendor/bin" is in the "sudo nano .bash_profile" it is as well.

@jwavess It's with the ls but this is better

ls -lah /etc/nginx/sites-available

You probably haven't got your mapping for the site setup properly. Check the root /home/web/laravel/public; entry.

@bashy ls -lah /etc/nginx/sites-available would not work, I'm on mac - idk if that matters, I tried sudo nano /etc/nginx/sites-available and it prompted me to enter my password, which I did, and nothing was in there. How do I check my mapping? You mean the mapping in my yaml file?

Seth

i got it!