Can't make Laravel 4 to work on localhost

Question

I'm trying Laravel for the first time after reading an announcement of the Laravel4 beta releasing.

I followed these steps I installed composer and laravel with all the dependencies it needed. I put the laravel inside my ~/public_html directory - as I'm used to do it with Codeigniter, but I think something's wrong here.

If I point to the browser to http://localhost/~carlo/laravel-develop/, it just displays the content of the directory.

Then, while on the filesystem I had a laravel-develop/public folder, it didn't appear on the browser.

I've found that changing the .htaccess like this:

<IfModule mod_rewrite.c> 
RewriteEngine on 
RewriteCond %{REQUEST_FILENAME} !-f 
RewriteCond %{REQUEST_FILENAME} !-d 
RewriteRule ^(.*)$ index.php/$1 [L] 
</IfModule>

resulted in an error when I try to access the public folder. The error:

ErrorException: Warning: file_put_contents(/home/carlo/public_html/laravel-develop/app/config/../storage/meta/services.json): failed to open stream: Permission denied in /home/carlo/public_html/laravel-develop/vendor/laravel/framework/src/Illuminate/Filesystem/Filesystem.php line 77

another one:

/home/carlo/public_html/laravel-develop/vendor/laravel/framework/src/Illuminate/Filesystem/Filesystem.php line 77

then a long list of errors. The last one is:

require_once('/home/carlo/public_html/laravel-develop/start.php') in /home/carlo/public_html/laravel-develop/public/index.php line 53

Same problem here. Unfortunately, none of the answers here helped. I'm positive that my permissions are set correctly, as well as the .htaccess is fine. Still, can't make it work. — Томица Кораћ, Jan 16 '13 at 22:36
@dualed that's not a really good suggestion... IMHO better learn L4, for sure — Gadoma, Aug 16 '13 at 16:27
@Gadoma that was in january, when Laravel 4 was in pre-beta phase. — dualed, Aug 17 '13 at 23:50

adridev · Answer 1 · 2013-03-21T13:39:25.500

70

Try to change the folder permissions for the storage folder using the terminal:

chmod -R 777 storage

More info on this matter can be found here.

edited Mar 21 '13 at 13:39

answered Jan 15 '13 at 21:08

adridev

1,150
10
15

Mark this answer as correct if it helped. This worked for me multiple times. – Nick Nov 07 '13 at 03:16
2

That worked for me too... But why can't I set set the group of storage to www-data and its permissions to 775? – gaflach Jan 31 '14 at 02:23
1

Actually, `chmod 757` is enough. Using `777` might be a little over the top. – enchance Feb 07 '14 at 11:20
@enchance Sure? I just tried with `chmod 757` and it did not work. It did with `chmod 777`. – Dynelight Feb 28 '14 at 18:43
1

chmod -R 775 would be a more secure solution. In this case the group of storage folder should be the same as the web server's. – eaykin May 22 '14 at 11:03
1

`775` only worked for me after I did `sudo chown -R _www:_www mywebfolder` .. see my answer below. – Justin Aug 21 '14 at 19:21
chown on storage worked for me, ubuntu 14.04 and laravel – Elemenofi Dec 13 '14 at 17:22

girlcode · Answer 2 · 2013-04-23T03:32:05.757

16

Your errors resulted because laravel couldn't write to the app/storage folder. The rest was just a stack trace. In order to make the storage folder writable, cd into your app folder and then run:

chmod -R 777 storage

edited Apr 23 '13 at 03:32

answered Jan 15 '13 at 21:33

girlcode

3,155
5
27
41

I don't think it's a matter of permissions since when I point the browser to `http://localhost/~carlo/laravel-develop/` the `public` directory doesn't even appear in the directory tree. I changed the permissions anyway, as you suggested, but it didn't work. – Carlo Jan 16 '13 at 09:09
Then you probably put that .htaccess in the root folder, which is why it's not displaying the public folder... .htaccess goes in the public directory. – girlcode Jan 16 '13 at 15:02
1

755 won't make the directory writable for the web server as you have RWX RX RX but you need RWX on each so `chmod -R 777 storage` – Gazzer Apr 02 '13 at 09:13

score 11 · Answer 3 · edited Apr 20 '14 at 21:39

Production way, moderate complexity for people not familiar with Unix, but more secure:

Go in super user mode (sudo -s or su).
Create group web (groupadd web)
Add you main user to group web (suppose your user is cool_user, so run usermod -a -G web cool_user)
Add php-fpm or web server user (if php is used as a SAPI module) to web group (for example, on CentOS php-fpm utilize apache user name, so in most cases this will work: usermod -a -G web apache)
Change your project root directory group owner to web recursively (chgrp -R web /path/to/project/root/)
Grant recursively write permission for group (chmod -R g+w /path/to/project/root/
Optionally To allow all newly created by apache (or some other) user files and folders be accessible from your user, make them receive group ownership same as their parent folder by setting groupid bit recursively on your project root directory (chmod -R g+s /path/to/project/root/).

Voila!.

Fast and dirty way, for those who doesn't care about security and want make it works at any cost, not secure:

Go in super user mode (sudo -s or su).
Grant recursively full permission (read, write, execute) for all users (chmod -R o=rwx /path/to/project/root/

score 5 · Answer 4 · answered Apr 24 '13 at 17:57

In my case I resolved this error by modifying in file /app/config/app.php the default setting:

'url' => 'http://localhost',

to my local custom virtualhost host url:

'url' => 'http://mydomain.local',

This seemed to be THE essential change that resolved the issue (I also chmod'ed the storage folder, as suggested here)

hope this helps some of you..

score 3 · Answer 5 · answered Aug 16 '13 at 15:47

3

further to above, if you're using a virtualbox/vagrant VM type environment, then on my Mac I needed to issue the chmod on the host (mac) system but on my Windows box, it was fine issuing the chmod direcly on the VM.

answered Aug 16 '13 at 15:47

jacanterbury

1,435
1
26
36

score 2 · Answer 6 · answered Jan 15 '13 at 19:48

2

You need to add: Options +FollowSymLinks

<IfModule mod_rewrite.c> 
RewriteEngine on 
Options +FollowSymLinks
RewriteCond %{REQUEST_FILENAME} !-f 
RewriteCond %{REQUEST_FILENAME} !-d 
RewriteRule ^(.*)$ index.php/$1 [L] 
</IfModule>

answered Jan 15 '13 at 19:48

now it just gives me a 500 error: Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. – Carlo Jan 15 '13 at 20:39

score 2 · Answer 7 · edited Apr 20 '14 at 21:39

2

You need to read the installation documentation:

http://laravel.com/docs/installation#configuration

Pay attention to the bit here:

Laravel requires one set of permissions to be configured - folders within app/storage require write access by the web server.

There is also other stuff thats useful in that document, so make sure you read it all.

edited Apr 20 '14 at 21:39

verheesj

1,438
2
16
24

answered Oct 20 '13 at 16:17

Relaxing In Cyprus

1,976
19
25

score 2 · Answer 8 · answered May 05 '14 at 00:59

I had the same problem, here is how I solve it: In your httpd-vhosts.conf files you need to add the configurations to your folders, this is what I have in mine

<VirtualHost *:80>
    ServerAdmin your@mail.com
    DocumentRoot "/home/carlospublic_html"
    ServerName carlos.local
    <Directory "/home/carlos/public_html">
        Options Indexes FollowSymLinks MultiViews
        AllowOverride All
        Order allow,deny
        allow from all
    </Directory>
</VirtualHost>>

score 1 · Answer 9 · answered May 06 '14 at 13:03

1

The webroot of your server should point to the /public folder of your Laravel installation. This is where the index.html file recides from where Laravel is initialized.

answered May 06 '14 at 13:03

sidneydobber

2,790
1
23
32

score 0 · Answer 10 · edited May 23 '17 at 11:59

0

First, this answer here will help you with permissions. Second, you may need to add RewriteBase ~/carlo/public_html/laravel-develop to your .htaccess since you're running it out of a home directory.

edited May 23 '17 at 11:59

Community

1
1

answered Jan 16 '13 at 02:53

ChrisMoll

365
1
12

score 0 · Answer 11 · answered Mar 25 '13 at 22:04

Hey I got this error too and changing the write permissions didn't seem to work either. It turned out I needed to change the User and Group settings in apache's httpd.conf file. Here's a good tutorial for it: Enable Write Permissions for the Native Built-In Apache in Mac OS X Lion

score 0 · Answer 12 · answered Jun 14 '13 at 23:21

0

Checking on the Requirement for the LR4, your local server must have these: PHP >= 5.3.7 MCrypt PHP Extension

Otherwise, will fail. I am facing this trouble also and now looking for an updated PHP and its extension for my XAMPP.

answered Jun 14 '13 at 23:21

jsdecena

572
2
7
22

score 0 · Answer 13 · answered May 14 '15 at 17:45

I like this method better than changing permissions to 777. Set Apache to run as you.

In terminal type id to get uid=123(Myname).

Open /etc/apache2/httpd.conf and edit it to use your username.

<IfModule unixd_module>
   User Myname
   Group staff
</IfModule>

Back to terminal: sudo apachectl restart

score -1 · Answer 14 · answered Jun 10 '13 at 21:48

-1

I ran into this problem a few minutes back and using sudo chmod -R 777 storage seemed to help make the storage/meta/services.json writable. Just to add to what everyone has been saying. This worked for me.

answered Jun 10 '13 at 21:48

Dammy

7
3

4

Glad to hear it worked, Dammy. However, if the other answers helped you, there's no need to post a duplicate - just upvote! – David Cain Jun 10 '13 at 22:07

Can't make Laravel 4 to work on localhost

14 Answers14

Linked

Related