Vagrant 403 Forbidden

Question

I\'ve been running Vagrant successfully for about a week. Last night I ran vagrant reload and now I can no longer access my sites.

• VirtualBox version 4.2.16

Answer 1

My hunch is that this is not a vagrant issue at all but solely an Apache configuration glitch. There are a few things I can think to check.

First, obviously, is to confirm that the user that apache is running under has read and execute permissions for the DocumentRoot folder.

Since you mentioned Apache 2.4, there have been changes in the configs from 2.2. Make sure your Allow from all statements now read Require all granted. (If you were still on 2.2, you'd want to make sure they said Allow from all instead of Deny from all.) In either case, you can set this in each individually, or set a default in your block of the main httpd.conf file.

Getting more obscure, you could check for selinux, although I'm pretty sure this isn't present in Ubuntu by default. (It is in CentOS, for example.)