0
Answered

problem with permissions (docker compose filerun:filerun)

pandathesamurai 10 months ago updated by Vlad R 9 months ago 9

Hello, dear developer!

I'm running latest version of filerun in docker compose behind Traefik2 as a reverse proxy. 

And looks like there's some problems with permissions:

My user's profile picture do not shown up after upload. It is just a blank image in place of where it should be. Inspect/Console in google chrome says on that element: /a/?uid=2&noCache=1644966481281:1 Failed to load resource: the server responded with a status of 404 ()

part of my docker compose file:

https://pastebin.com/NV2azL7Q


my customizables/config.php:

<?php umask(012); 

$config['path']['thumbnail_cache'] = '/var/www/html/thumbnails/'; 

$config['app']['ui']['enable_favicon_ico'] = true;

Kindly please help

Answer

Answer
Answered

Please see solution for e-tag problem here: https://feedback.filerun.com/en/communities/1/topics/1437-nextcloud-client-409-conflict-on-files-over-10mb#comment-5370

There is another thread related to the error with the user avatar. Closing this topic.

Aslo every 10-15min I see sync error in official latest nextcloud app's for linux (manjaro standart repo) and windows10.

And on manjaro I see this errors only about files in @Home/Joplin folder, then on windows I can't sync at all because of them.


part of filerun's docker logs:

filerun  | + id -u www-data
filerun | + '[' '!' -e /var/www/html/index.php ']'
filerun | + exec /usr/bin/supervisord -c /filerun/supervisord.conf
filerun | 2022-02-16 00:37:54,796 CRIT Supervisor is running as root. Privileges were not dropped because no user is specified in the config file. If you intend to run as root, you can set user=root in the config file to avoid this message.
filerun | AH00558: apache2: Could not reliably determine the server's fully qualified domain name

when I changed download accelerator (under cpanel/Files/Misc/options) from Apache XSendfile to NGINX X-Accell and refreshed page - avatars magically appeared! Problem with E-tag persist 

Under review

Please let me know the FileRun version and the Nextcloud app version.

FileRun: 20220202,

Nextcloud desktop app №1: Version 3.4.2 (Manjaro). Using virtual files plugin: suffix

Nextcloud desktop app №2: Version 3.4.2 (Windows). Using virtual files plugin: wincfapi

Sorry, forget to mention: i'm running filerun@docker-compose in Ubuntu-20.04 under windows 10 wsl2. 

I re-created the filerun, worked only as superuser and noticed that the problem with etag began to occur apparently (?) because of Joplin, when in Joplin enabled automatic synchronization once every N minutes. Joplin changes e-tag, after that nextcloud client can't synchronize these Joplin files for some time (and this is correct behavior), after some short time nextcloud client synchronizes files without errors (unlike simple user). 

So looks like with whole problem concern all non superuser users.

Answer
Answered

Please see solution for e-tag problem here: https://feedback.filerun.com/en/communities/1/topics/1437-nextcloud-client-409-conflict-on-files-over-10mb#comment-5370

There is another thread related to the error with the user avatar. Closing this topic.