Error Failed to create _files

johnny

I updated the index.php file on my ubuntu 20.04 with the php-mysql-apache installed on it, but when I ran it
I got the error message:

Error
Failed to create _files

What is the matter? Could you help me fix it please?
Thanks

Karl

Looks like permissions. View your ?check=1 page, what do you see? I am guessing it's a difference between the "owner" of the dir and the "owner" of the file. Basically the PHP function mkdir() fails when trying to create the _files dir, and this dir is necessary to store config and cache.

If you have a link, please include and I can check further (send to karl AT photo.gallery if private).

johnny

Karl

https://imgbox.com/b8gN6kdl

For the record, ubuntu runs as a VM in Vmware workstation

Thanks

Karl

I can't see red/green checkmarks from your paste, but it looks to me like root is NOT writeable because it only outputs permissions and [owner ***] when something is not writeable. As you can see in our demo, [owner] is not output because root is writeable:
https://demo.files.gallery/index.php?check=1

Root needs to be writeable from the index.php. Why it's not writeable, I can't say from here.

johnny

Karl

I edited my previous post and I linked an image.

Anyway, it's a strange behaviour since I haven't any kind of issues with other php files in other directories on the same server
Thanks

Karl

That response in ?check=1 comes when PHP is_writable() fails for the tested dir/file. Is it default config btw? You can try this: Create a file mkdir.php in your root, add the below, and run in browser:

<?php
if (!@mkdir('./_files')) {
    $error = error_get_last();
    echo $error['message'];
}

It should provide a more descriptive error. From here:
https://stackoverflow.com/questions/927564/how-to-find-a-reason-when-mkdir-fails-from-php

johnny

Karl

I ran a test.php file with the code you suggested. Got this:

mkdir(): Permission denied

Karl

johnny mkdir(): Permission denied

Your PHP simply can't write to disk, which is necessary if Files app is to store config, resized images and folder cache. I can't diagnose this from here without access, assuming this is a private server. Normally, it would be permissions, owner mismatch or your website document root pointing to areas on disk that PHP may be able to read, but not write. You will need to ask in forums for the specific server combo you have setup.

Using Files app without cache
It is possible to edit the config in index.php and disable all cache features, but this is slow and inefficient. With cache features disabled, Files app will no longer require capabilities to write to disk.

fabiosistemi

Karl

fabiosistemi .

Is there any question?

fabiosistemi

Karl I made a mistake in answering.