Directorys are not writable.

BlameDylan

Hello everyone,
I have recently decided to install Flarum to do some testing and learn to use it. However, I am unable to get it to work and when I visit my installation I get a blank page (hasn't been installed). After an hour or so of trying, I eventually discovered this at the bottom of my Nginx config:

PHP message: PHP Warning:  include(/var/www/sub.mywebsite.com/flarum/storage/framework/views/f8aebd3f27d63d7f2545b724c2ea9039): failed to open stream: No such file or directory in /var/www/sub.mywebsite.com/flarum/vendor/illuminate/view/Engines/PhpEngine.php on line 42

When infact the

/flarum/storage/framework/views/

is empty. I downloaded the latest packaged beta on your downloads page. Any idea where I can obtain these view files?

Thank you,
Dylan

Toby

There's a known issue in beta 1 where the installer will crash if the flarum/storage/framework/views directory is not writable. This will be fixed in beta 2, but in the meantime, see how you go changing permissions so PHP can write to this directory?

stallone

Toby I also got your packaged from your downloads page, but i got a 403 forbidden reply. That' s because of the lack of index.php?

BlameDylan

@Toby thank you for your speedy reply. The whole installation has permissions 777 and is owned by the "nginx" user. (I know 0777 is not recommended, but I'm just testing 😉

Any other ideas?

Kulga

BlameDylan Were the permissions already 777 prior to the install?
If you just changed them, install again.

BlameDylan

@Kulga this is how I went about installing:
1. I downloaded and extracted the zip file.
2. I setup the nginx redirect rules, which can be found at https://gist.github.com/BlameDylan/88a34cc5452284c8d7b4.
3. I attempted to visit the page, no success.
4. I then chmodded the files to 0777.

I will re-attempt installation tomorrow. However, do you have anymore ideas?

BlameDylan

Installed again, no success.

luceos

Who is the owner of the files?
ls -la

BlameDylan

Root, however that is what Nginx and PHP-FPM are running as. (I've tried using both nginx and root)

luceos

BlameDylan

That explains it. Nginx runs by default under www-data; chown the files to that user. No user can modify or write files or in directories belonging to root.

BlameDylan

[root@server www]# chown -R www-data:www-data *
chown: invalid user: ‘www-data:www-data’

luceos

BlameDylan ah, it could also be www-run; check your /etc/nginx/nginx.conf at the top i think

luceos

And never, ever set access rights to 777, unless you want your site to get hacked. (This is a very common reason sites get hacked on shared environments). The last 7 indicates everyone can write; this also allows a bad script on someone elses site to do naughty things 😉

BlameDylan

@luceos yes however I'm just testing locally.

BlameDylan

...
user nginx;
worker_processes auto;
error_log /var/log/nginx/error.log;
pid /run/nginx.pid;
...

Another thing: there is nothing in the views directory, wouldn't that be the problem?

Franz

BlameDylan there is nothing in the views directory, wouldn't that be the problem?

Yeah, that is weird. There should be files.

luceos

BlameDylan it doesn't matter. it needs to create caches and stuff, you can't even write a log file now. Let alone create an error page using a error blade file.

luceos

Ok, chown to nginx 😉

GOD

I know you said you are running everything as ROOT and I know you said this is only a local install. Please keep in mind that depending on which linux distro you are using, there may be some underlying security preventing you from doing what you are doing.

It is better you run your test in the correct manner you would for a live install.

BlameDylan

@luceos Everything's permissions are now 775, and are chowned to nginx. No success.

@GOD understood, reverted to nginx user and 775. Still no difference.

Kulga

BlameDylan Once you do a recursive chmod all bets are off. I'd suggest wiping the install and re extracting.