403 on Apache for the laravel project, after upgrading to Ubuntu 13.10

Question

I upgraded to Ubuntu 13.10. At first, when starting apache after the update, there were no / broken files, so I just reinstalled apache. I copied the vhost file.

When I try to access my Laravel project from a browser, it will get a 403 error. I changed the permissions of the root folder several times, but this is still forbidden. I do not think this is a problem with laravel since I already fixed it on 13.04 and I use the same files.

Here is my 000-default.conf file located in / sites -enabled and / sites-available. My apache2.conf file has not changed since installation.

<VirtualHost *:80> DocumentRoot /home/brennan/development/MasonACM/public <Directory /> Options FollowSymLinks AllowOverride None </Directory> <Directory /home/brennan/development/MasonACM/public/> Options Indexes FollowSymLinks MultiViews AllowOverride All Order allow,deny allow from all </Directory> ErrorLog /var/log/apache2/error.log LogLevel warn CustomLog /var/log/apache2/access.log combined </VirtualHost> 

It is also important to note that my .htaccess file is missing and it has not been modified since the site has been working since 13.04.

UPDATE:

I now have apache host settings, but now the browser displays the actual index.php code, which means that apache for some reason does not use php. I just checked that php was installed, so why don't apache recognize it?

Answer 1

Apache2 can also be upgraded to version 2.4 , and there are a few notes.

First, do you have Apache 2.4.x + now? Check by doing:

 $ apache2 -v 

If so, your ghost needs some tweaking:

First: +/- on Options:

Some Options options need the +/- syntax. More details here . This can be especially important when mixing +/- for some directives (read the previous link to see more).

Edit:

 Options Indexes FollowSymLinks MultiViews 

at

 Options +Indexes +FollowSymLinks +MultiViews 

Second: Allow / Deny

Now Apache controls access through mod_authz_host

Edit:

 Order allow,deny Allow from all 

at

 Require all granted 

Read more about upgrading from Apache 2.2 to 2.4 .

Answer 2

I had the same problem, for some reason restarting Apache with Sudo made a difference. Are mods mapped and mcrypt healthy?