Skip to main content


!Friendica Support did you know that in your wiki there are dead links. i was wondering why my new friendica server from yesterday to today has more than twice as much storage space consumed. i was looking for information about the perpetrator called storage in the database. but https://wiki.friendi.ca/docs/database when i go to storage - there are a error 404. and no more information about what storage is and how i can reduce the size of this table....
in reply to Eric Mächler

No (at least I) did not know it. Thanks for sharing the info.

The files you are looking for are on your friendica note (instead of wiki.friendi.ca) or here in the repository https://git.friendi.ca/friendica/friendica/src/branch/develop/doc/database.
in reply to Eric Mächler

In the admin section of your node you can switch from database-based storage for pictures and files to file-base storage. It will give your database some room to breathe but it will grow your filesystem instead.
in reply to Hypolite Petovan

I followed your advice and I got
ERR_HTTP_RESPONSE_CODE_FAILURE .

Any hints?
in reply to 8Petros [Signal: Petros.63]

Can you please expand on what you were doing when you got this error? Also paging @Fabio as he implemented the storage switch feature.
in reply to Hypolite Petovan

The context: I am self-hosting Friendica under #Yunohost, so I created a directory at: /home/yunohost.multimedia/petroskowo

Then I opened admin options (Firefox):

Once I click "Save and use", the response is a blank screen at
https://petroskowo.pl/admin/storage/Filesystem

When I tried the same from my Android / DuckDuckGo browser, I get
"Page ... cannot be loaded, because ERR_HTTP_RESPONSE_CODE_FAILURE"

As usually with such cryptic errors my money is on access rights. ls -l shows

drwxrwxr-x+ 2 root               root 4096 Nov  4 18:28 petroskowo

but I do not know if and to what should I change it.
in reply to 8Petros [Signal: Petros.63]

What is your web server user? What is the user you run the Friendica worker cron job with? Both should be the same and neither should be root.
in reply to 8Petros [Signal: Petros.63]

@8Petros. (Fediverse > Mastodon®) @Hypolite Petovan The storage folder should be accessible and writeable by your webserver user. On debian, that is "www-data".
If you are running the worker with the cronjob, make sure that is running as the same user. Also if you are using systemd service, check the service file and make sure it's using the same user.

A blank screen in browser usually is caused by fatal php errors. You can check your webserver logs and see if they have been logged somewere,
or you can add in index.php, just after the line use Dice\Dice; this code:
ini_set('log_errors', 1);
ini_set('error_reporting', E_WARNING | E_ERROR | E_PARSE | E_NOTICE);
ini_set('error_log', '/tmp/php.log');

and try again. errors should be then be written to /tmp/php.log

the error "ne:ERR_HTTP_RESPONSE_CODE_FAILURE" is an android thing.
in reply to Fabio

@Fabio -- kudos!

Thanks to you, I learned today how to:

1. From my cron table retrieve the username: friendica

2. From /var/www/friendica find out out ownership and mode: friendica:www-data 0750

3. In /var/www/friendica create log/friendica.log

4. Apply details from #2 to the directory I created for media files

And now the storage switch went without any glitches.

root@tepewu:/home/yunohost.multimedia/petroskowo# ls
0c  2a  37  41  4d  61  71  8c  bf  d5  f6
0e  2e  3a  42  57  62  73  93  c8  e3  ff
29  33  3e  4b  60  6d  79  94  c9  e9  index.html


Thank you for your support.
#2 @Fabio

Lo, thar be cookies on this site to keep track of your login. By clicking 'okay', you are CONSENTING to this.