It was an issue with vagrant. I have had the issue setting up laravel also. To fix it I just changed the user/group for apache to vagrant. Generally this wouldn't be safe at all in a production environment but access to the VM is limited to me, so I am not too concerned.
To change the user/group will depend on your OS. In ubuntu the config file is located in /etc/apache2 and it is apache2.conf. Sometimes "apache2" will be swapped out for "http.d". You can edit the file using vim/nano and then save and restart apache.