On 4/19/2025 at 5:22 AM, hogmoff said:

In my configuration it's only working with UID=99, GID=100,UID Name=99, GID Name=users

Otherwise the mapping doesn't fit:
(left side docker console, right side unraid console)

 

 

The username nobody is 65534 as standard value in docker -> mapping do not work

Unfortunatly the mapping is not the only issue. Any file created in filerun can renamed but not deleted.
Maybe the mask should be set to 777, current value is 644. I tried to set a variable "UMASK=777" but without any effect.

Anyone a idea about the issue? How did you resolve this?
 

if youre on the newest 2026.1.0 those var's aren't needed anymore

This is all you need on 2026.1.0 version (you will need to chown nobody:users from the unraid console on your appdata folder if it's not already)

Edited April 18Apr 18 by MowMdown

Great news! Vlad released a patch that allows filerun to work on the iOS Nextcloud APP!!!!!!

26.2.0 is released: https://filerun.com/index.php/changelog?v=2026.2.0

Edited April 21Apr 21 by MowMdown

Added step-by-step guide for updating from FileRun 2024.x to the latest 2026.2, refer to the post under the main topic:

I finally had some time to go through the update process myself and had a few minor hiccups though otherwise it's pretty seamless. I've captured everything regarding the process for Unraid users so if anyone was still holding off on updating now is a good time to do so :) the entire process should only take ~5 minutes. Let me know if you have issues!

Edited April 24Apr 24 by ImSkully

HELLO Team

I just bought Filerun. I started everything fresh with new containers. The UNRAID apps gives MYSQL 9.7.0 and the latest filerun container. Everything looked good. Database created, filerun got to it's setup screen and so on. I entered my license and it setup the rest of the system. Once I logged in I got this error:

Message to Vlad:

 I am getting 42000 errors when I try to access filerun after login.   I see this in the php logs in a tmp folder.

 What can I do about this ?

 

[12-May-2026 19:39:15 UTC] ↘️Drive/ui/get/tree (POST)

               🔎SQLSTATE[42000]: Syntax error or access violation: 1305 FUNCTION filerun.MD5 does not exist

                              🐞FR\Core\DB\DatabaseException (42000)

🔎"[unknown]", in 🐘"/var/www/html/apps/Drive/!classes/Files/DBPaths.php#30"

 

Vlad's response:

Please disable FIPS Mode in your MySQL server, or if that is not an option for you, you can use a separate MySQL container just for FileRun where FIPS is not enabled.

My response back after looking into this:

I think it is off

 mysql> SHOW VARIABLES LIKE 'ssl_fips_mode';

+---------------+-------+

| Variable_name | Value |

+---------------+-------+

| ssl_fips_mode | OFF   |

+---------------+-------+

1 row in set (0.005 sec)

 

What might it be.. I am running 9.7.0 mysql container.

Vlads message back:

My recommendation is to replace MySQL with the latest version of MariaDB, until a solution to this is found. 

So I loaded the latest MariaDB container from APPs and set it up with defaults. I then moved my database from mysql to mariadb and use the same login etc.

It works !!!! No issues and the filerun product runs exactly like it's demo

There is something in the latest version of MYSQL 9.7.0 that is causing a query issue. Anyway I wanted to document my journey here so no one else gets stuck too.

Edited May 13May 13 by 5STAR

Having a weird issue with my filerun setup.

/user-files is owned by nobody:users I run chown -R nobody:users /mnt/user/filerun-data so everything looks good.

However, when I try to upload an image via WebDAV or directly to the website, it doesnt go throw. So clearly it doesnt have access to write, only read?

I tried to create a text file via the website. It actually managed to create it, but it only created an empty text file.

I double-checked, and container does have that extra flag --user 99:100

--

docker exec FileRun id nobody

uid=65534(nobody) gid=65534(nogroup) groups=65534(nogroup)

--

docker exec FileRun id

uid=99 gid=100(users) groups=100(users)

--

# ls -l

total 0

drwxr-xr-x 1 nobody users 16 Jun 7 16:53 Adventure\ Capture/

-rw-r--r-- 1 nobody users 0 Jun 7 17:16 test.txt

Edited June 7Jun 7 by Nelli

for me, problems with webdav usually point to a problem with your reverse proxy. Are you using nginx or some other reverse proxy? I would also ask this in the filerun forums as they've been pretty helpful.