Can you try running "vagrant provision" from the laravel folder and see if that helps. If not, we'll probably need the log to see what goes wrong.
I've had the issue a few times myself, usually something is not set up right and I'll need to run "vagrant provision" or destroy and recreate the instance to fix it.
Yeah i tried vagrant provision each time i changed something in config. I skimmed thru logging and didn't find anything unusual. I am thinking this has to be a problem with virtualbox but don't know what to look at. Can i use something like VMware instead of virtualbox?
Sign in to participate in this thread!
Laravel
Laravel News
Laracasts
Laravel Podcast