Vagrant+Chef配置Apache2虚拟主机遇激活及权限问题求助

Hey there! Let's work through your two Vagrant/Chef Apache issues step by step—totally get how confusing these tools can be when you're just starting out, so let's break it down simply.

The problem here is that while Chef is dropping the default.conf template into the right location, it's not actually telling Apache to enable the site. The a2ensite command is what triggers that activation, and we need to add that explicit step to your Chef recipe.

Fix: #

Add an apache_site resource to your recipe (make sure this comes after the template resource that deploys default.conf):

apache_site 'default.conf' do
  enable true
end

This Chef resource runs the equivalent of a2ensite default.conf automatically, and it will also trigger an Apache restart if needed to apply the change. If you're using the official apache2 cookbook, this resource is already included, so no extra dependencies are required—just drop that block into your recipe (like the default.rb file of your custom cookbook) and it’ll handle activation on your next provision.

This error almost always comes down to file permissions or Apache’s directory access rules. Here’s why it’s happening:

• Vagrant shared folders are usually owned by the vagrant user/group by default, but Apache runs as the www-data user (on Debian/Ubuntu systems), which doesn’t have read access to that directory by default.
• Alternatively, your Apache default.conf.erb template might not have the correct access rules set for the /vagrant/web1_docroot directory block.

Fixes (pick one that works for you): #

Option 1: Adjust Shared Folder Permissions in Vagrantfile

Update your Vagrantfile to set the owner/group of the shared folder to match Apache’s user:

config.vm.synced_folder "./web1_docroot", "/vagrant/web1_docroot", 
  owner: "www-data", 
  group: "www-data"

This ensures the folder is owned by the user Apache runs as, so it can read the files inside. Run vagrant reload after making this change to apply it.

Option 2: Fix Permissions via Chef

If you prefer handling it through Chef, add an execute resource to your recipe to set the correct ownership:

execute 'set_webroot_permissions' do
  command 'chown -R www-data:www-data /vagrant/web1_docroot'
  action :run
  only_if { File.exist?('/vagrant/web1_docroot') }
end

This runs the chown command to give Apache’s user access to the directory.

Option 3: Verify Apache Directory Configuration

Double-check your default.conf.erb template to make sure the <Directory> block for /vagrant/web1_docroot allows access. It should look something like this:

<Directory "/vagrant/web1_docroot">
    Options Indexes FollowSymLinks
    AllowOverride All
    Require all granted
</Directory>

If the Require all granted line is missing or set to deny, that will cause a 403 even if permissions are correct.

内容的提问来源于stack exchange，提问作者psyvic