4 hours ago, hogmoff said:

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

 

This is all that works for me as well. as noted here:

 

https://forums.unraid.net/topic/187661-support-imskully-filerun/#findComment-1542763

 

If I use those values in my template and create a file inside filerun the file appears like this:

 

Edited April 19, 20251 yr by MowMdown

2 hours ago, MowMdown said:

 

This is all that works for me as well. as noted here:

 

https://forums.unraid.net/topic/187661-support-imskully-filerun/#findComment-1542763

 

If I use those values in my template and create a file inside filerun the file appears like this:

 

Thanks! You give me the the way to the solution.

I installed with the standard user name and the .filerun.trash folder had the wrong user. After changing to 99:100 it works now!

Just testing the above and can confirm that you are correct. The user:group gets set correctly and allows rename/deleting as well as being correctly set to nobody:users with the following UID/GUID config:

 

 

Quite interesting considering nobody:users is what is stated on FileRun docs.

Edited April 25, 20251 yr by ImSkully

Is there a comprehensive guide to this? I can't seem to get it working.

29 minutes ago, Jules said:

Is there a comprehensive guide to this? I can't seem to get it working.

The Installation & Setup section covers all the necessary steps, if you need help then you'll have to provide more specific information about the problems you are facing.

Server error: file_put_contents(/var/www/html/system/data/temp/cache.settings.tmp.php): Failed to open stream: Permission denied in file /var/www/html/core/classes/FileRun/Utils/Cache.php on line 22

I always get this message when I login - is there a way to fix it? :D
I can click it away but still haha

1 hour ago, asynic said:

Server error: file_put_contents(/var/www/html/system/data/temp/cache.settings.tmp.php): Failed to open stream: Permission denied in file /var/www/html/core/classes/FileRun/Utils/Cache.php on line 22

I always get this message when I login - is there a way to fix it? :D
I can click it away but still haha

I started seeing this recently as well and tried reverting the UID/GUID settings which seems to have fixed it - give the below config a go and see if it resolves it:

Interesting, I've not ran across any issues with using 99 and 100 for the names

I still cannot get FR to set "nobody" as the user for my unraid files. it still shows up as "UNKNOWN"

I actually believe UID Name should be "abc" and the GUID name should be "users"

Edited June 17, 20251 yr by MowMdown

There is a major update expected for FileRun at some point in the next few weeks January 2026 - hoping that will bring some improvements to Docker permissions.

Edited December 4, 2025Dec 4 by ImSkully

I would really like to love it but I am really unsure atm. It's the only one that actually works fast and I really like the UI compared to something like seafile and it's not as bloated as nextcloud but the php.ini config and mobile apps kinda ruin it all for me. Using the website on mobile is rather mid and using a webdav doesn't let me upload large files and still can't get behind how to fix that. Idk if that's just me but relying on one guy who doesn't update it all that often kinda makes it hard to swallow. The lackluster community support, guides and general help is a negative for me. The setup is rather simple but idk man, it's a tough sell even tho it is the only piece of software I have paid for in a while and personally really like.

Is this still a bit of a challenge? I had used it years ago and liked it. Thinking of picking it up on half off sale now.

Is there an option of a trial licence for individual? €100 is a steep jump without being able to test at home. And I only found out about the existence of this application today, couple days after apparent black friday offer

Edited December 3, 2025Dec 3 by FrequencyLost

On 11/30/2025 at 2:26 PM, SirKelsALot said:

Is this still a bit of a challenge? I had used it years ago and liked it. Thinking of picking it up on half off sale now.

I've been running FileRun for years and pretty happy with it - that being said I don't use all the bells and whistles that come with it and mainly just use it as an archive for backups and documents/PDFs. If you don't have any greater requirements with it beyond it being a simple 'Google Drive' like solution, then you should be fine. That being said, @toxicPeary made a few good points regarding the fact that there's only a single person maintaining FileRun and receives very slow updates (last one was August 2024 though a new major update is coming in 2026).

19 hours ago, FrequencyLost said:

Is there an option of a trial licence for individual? €100 is a steep jump without being able to test at home. And I only found out about the existence of this application today, couple days after apparent black friday offer

There is an online demo you can check out, or alternatively you can contact FileRun and ask for a trial license as outlined on the demo page.

Edited December 4, 2025Dec 4 by ImSkully

I've been running this container for a while in Unraid! I wish I'd had your community template a couple years ago @ImSkully, thanks for making it! Yours is setup exactly like mine, but there are a few additional notes for those that are setting this up for the first time to avoid any issues:

1. Add LimitRequestBody 0 to /etc/apache2/apache2.conf (you can do this from the console of the filerun container by navigating to that file and using "vi" to edit it. By default you will be unable to upload a file larger than 1GB via webdav from services that don't support Filerun methods of chunking (Photosync), this will fix that.

2. Use these in the advanced settings of Nginx (the gear icon) to avoid any issues with upload & download size & speed:
   client_max_body_size 50000M;

   proxy_max_temp_file_size 0;

   proxy_request_buffering off;

   proxy_buffering off;

   proxy_read_timeout 600s;

   proxy_send_timeout 600s;

   proxy_connect_timeout 300s;

   send_timeout 600s;

   client_body_timeout 600s;

3. FileRun generates thumbnails for images automatically (assuming you have the plugins enabled (via the superuser control panel)), but it only does it once you are viewing the image. If you have a small library this is fine, but I would run into issues where I would try to view all the images in a folder of large RAW files and it would crash my server trying to generate all of them. You can avoid this issue by pre-generating thumbnails by following the instructions in my post on the FileRun forum: https://feedback.filerun.com/communities/1/topics/2498-thumbnail-questions

Edited January 22Jan 22 by DebrodeD

FYI there is a new update 2026.1.0 it’s currently in beta. I attempted the upgrade and for me personally it did not go over smoothly so if you’re gonna update. Make a backup of your container appdata and database.

Also to complete the update you need the :8.4 tag for the container.

So far it seems to be working now but I started over with a clean slate

I've been keeping an eye on the 2026.1 update and following the forum thread, looks very exciting though there's still a few issues that need to be ironed out before its ready. Once the stable release is announced, I'll update the template and share notable breaking changes/migration steps for Unraid users to move over to the latest version with (hopefully) minimal disruption.

On 2/7/2026 at 8:56 AM, ImSkully said:

I've been keeping an eye on the 2026.1 update and following the forum thread, looks very exciting though there's still a few issues that need to be ironed out before its ready. Once the stable release is announced, I'll update the template and share notable breaking changes/migration steps for Unraid users to move over to the latest version with (hopefully) minimal disruption.

FYI 2026.1.0 is live as a stable update

Successfully installed the 2026.1.0 update. Here is what I had to do (which was basically just follow the update instructions here):

1. Backed up everything I could think of (other than user files) - appdata folder & db (using adminer) & container

2. Made sure my MariaDB container was up to date

3. Logged into Filerun as superuser & checked for update, then download/installed it

4. Then went to my FileRun container in Unraid and updated the repository to "filerun/filerun:8.4"

5. After doing that it successfully updated but it wouldn't start because I needed to change my APACHE_USER & GROUP container variables from 99/100 to nobody/users:

   APACHE_RUN_USER_ID=99
   APACHE_RUN_GROUP_ID=100
   APACHE_RUN_USER=filerun
   APACHE_RUN_GROUP=users

6. Then I added these into the "gear" icon of my proxy entry for FileRun in Nginx (after everything else already in there):

   fastcgi_split_path_info ^(.+\.php)(.*)$;
   fastcgi_param PATH_INFO $fastcgi_path_info;

7. Then the container started and I was introduced to the final update screens in FileRun where I came upon one more error:

   ⚠️ The permissions of the file "/var/www/html/system/data/autoconfig.php" do not allow PHP to write data to it. ℹ️ FileRun is installed inside "/var/www/html"

8. I fixed that by running this in the console of the FileRun container:

   chown -R 99:100 /var/www/html/system/data
   chmod -R 775 /var/www/html/system/data

9. I then refreshed the update page in FileRun and it showed as a checkmark , so I continued and I was able to login successfully and it's now working perfectly.

Edited March 16Mar 16 by DebrodeD

On 3/10/2026 at 10:18 AM, DebrodeD said:

Successfully installed the 2026.1.0 update. Here is what I had to do (which was basically just follow the update instructions here):

1. Backed up everything I could think of (other than user files) - appdata folder & db (using adminer) & container

2. Made sure my MariaDB container was up to date

3. Logged into Filerun as superuser & checked for update, then download/installed it

4. Then went to my FileRun container in Unraid and updated the repository to "filerun/filerun:8.4"

5. After doing that it successfully updated but it wouldn't start because I needed to change my APACHE_USER & GROUP container variables from 99/100 to nobody/users:

   APACHE_RUN_USER_ID=99
   APACHE_RUN_GROUP_ID=100
   APACHE_RUN_USER=nobody
   APACHE_RUN_GROUP=users

6. Then I added these into the "gear" icon of my proxy entry for FileRun in Nginx (after everything else already in there):

   fastcgi_split_path_info ^(.+\.php)(.*)$;
   fastcgi_param PATH_INFO $fastcgi_path_info;

7. Then the container started and I was introduced to the final update screens in FileRun where I came upon one more error:

8. I fixed that by running this in the console of the FileRun container:

   chown -R 99:100 /var/www/html/system/data
   chmod -R 775 /var/www/html/system/data

9. I then refreshed the update page in FileRun and it showed as a checkmark , so I continued and I was able to login successfully and it's now working perfectly.

I've tried all this and I can't get it working.

I just get:

The application URL has been now updated.

Reload the page or click here to proceed.

And I can't get past this page.

I was able to fix this with NGINX config tweaking.

Edited March 12Mar 12 by musicking
Fixed

I updated my above post, but I've been working through some bugs in 2026.1 with Vlad the creator and he's solved most of them. I recommend installing the patched update that you can find here: patched update and upload it using the "Offline update" button, under the "Update" FileRun control panel section.

Also, I found out that setting APACHE_RUN_USER to "filerun" or "abc" (or anything you want OTHER than nobody or www-data as recommended in other guides) will fix Unraid seeing the owner as "UNKNOWN" and correctly show as "nobody".

I also added:

// Set File Permissions
umask(000);

to my config.php file found in "html/customizeables" to make it so that full permissions are added to any files created or uploaded to FileRun. That fixed problems I was having with my files not being editable/accessible via smb.

Edited March 16Mar 16 by DebrodeD

1 hour ago, DebrodeD said:

I updated my above post, but I've been working through some bugs in 2026.1 with Vlad the creator and he's solved most of them. I recommend installing the patched update that you can find here: patched update and upload it using the "Offline update" button, under the "Update" FileRun control panel section.

Also, I found out that setting APACHE_RUN_USER to "filerun" or "abc" (or anything you want OTHER than nobody or www-data as recommended in other guides) will fix Unraid seeing the owner as "UNKNOWN" and correctly show as "nobody".

I also added:

// Set File Permissions
umask(000);

to my config.php file found in "html/customizeables" to make it so that full permissions are added to any files created or uploaded to FileRun. That fixed problems I was having with my files not being editable/accessible via smb.

Thank you.

I have applied the update and your suggestions

@ImSkully

Not sure if youve been following along in the filerun forums but there is going to be a newer conatiner which fixes the apache permission stuff, it's no longer needed

You can remove the apache permission vars (all 4) and then just add --user 99:100 to the extra parameters

Edited March 18Mar 18 by MowMdown

Thanks for sharing! I'm pretty swamped this month with various work but will update the CA template and setup instructions soon.

22 minutes ago, ImSkully said:

Thanks for sharing! I'm pretty swamped this month with various work but will update the CA template and setup instructions soon.

No rush, I am working out the kinks with Vlad over in the filerun fourms to make sure that fresh install works just as seamless as doing an in place upgrade on this new exp branch tag. I ran into a few small snags regarding permissions.

So far though it's been pretty smooth.

Edited March 19Mar 19 by MowMdown

Thanks for this docker image. Got everything up and running, except one thing.

How do we add 'external folders' to Filerun? It isn't as simple as using Nextcloud with the 'external storage app'. Is this configurable within the docker image?