Any idea why the docker container says "Unhealthy" when looking at "docker ps" ? I've tried deleting and re-adding the containers...seems to be working fine but what does that mean?

I'm having issues setting this up. I'd like to set up a reverse proxy, so I need to add this to my existing custom network. It works fine on the default br0 network.

 

But on my own custom network, if I try to open the WebUI, it only opens

about:blank#blocked

 

If I add a forward from port 80 to an external port, then I get
 

404 Not Found
openresty

 

Any idea what might be going on here?

 

 

EDIT: I found a solution.

 

It turns out, the 404 Not Found error was because it was trying to access port 80 by default, which is currently being used by Nginx. I fixed this by changing the WebUI link in the advanced settings of the container to

 

http://[IP]:[PORT:1234]/

Where 1234 is my port.

Edited May 28, 20242 yr by ggrey
Found a solution

Is there any way to get rid of the "noindex" tag with FileBrowser? I'm trying to use this app as a means to get around the file:// protocol issue with SharePoint search. The file:// protocol won't allow you to download, open or edit a file. Unfortunately the noindex tag stops SharePoint search form indexing the files. There's no way to get SP to bypass that tag. 

/thx

Edited June 18, 20242 yr by mattm1121

On 4/1/2019 at 6:12 PM, ceyo14 said:

like alturismo said, First set to Bridge mode then click "+ Add another Path, Port,...." once there do the following:

 

Config Type: Port

Name: blank or whatever you want

Container Port: 80

Host Port: What ever port you want to set ( I have 100 for example)

Connection Type: TCP

Description What ever you want

 

After this, press ADD Button and test.

 

 

thank you very much for your post. It is useful even after 5 years  

Hi, I'm trying to get this app on organizr/SWAG, but I always end up with "502 bad gateway" no matter what I tried. I found many different config for nginx, but the different tweak don't seem to help. About to just give up. I don't know what I'm doing wrong, but here's my basic settings.

 

Cname seems to be working as "filebrowser.Domain.Net" links to my IP adress. I do have other app working fine (sonarr, deluge, netdata to name a few)

 

/ # cat .filebrowser.json
{
  "port": 80,
  "baseURL": "",
  "address": "",
  "log": "stdout",
  "database": "/database.db",
  "root": "/srv"

 

Unraid:

 

Organizr:

 

filebrowser.subdomain.conf:

## Version 2023/05/31
# make sure that your filebrowser container is named filebrowser
# make sure that your dns has a cname set for filebrowser

server {
    listen 443 ssl http2;
    listen [::]:443 ssl http2;

    server_name filebrowser.*;

    include /config/nginx/ssl.conf;

    client_max_body_size 0;

    # enable for ldap auth (requires ldap-location.conf in the location block)
    #include /config/nginx/ldap-server.conf;

    # enable for Authelia (requires authelia-location.conf in the location block)
    #include /config/nginx/authelia-server.conf;

    # enable for Authentik (requires authentik-location.conf in the location block)
    #include /config/nginx/authentik-server.conf;

    location / {
        # enable the next two lines for http auth
        #auth_basic "Restricted";
        #auth_basic_user_file /config/nginx/.htpasswd;

        # enable for ldap auth (requires ldap-server.conf in the server block)
        #include /config/nginx/ldap-location.conf;

        # enable for Authelia (requires authelia-server.conf in the server block)
        #include /config/nginx/authelia-location.conf;

        # enable for Authentik (requires authentik-server.conf in the server block)
        #include /config/nginx/authentik-location.conf;

        include /config/nginx/proxy.conf;
        include /config/nginx/resolver.conf;
        set $upstream_app filebrowser;
        set $upstream_port 80;
        set $upstream_proto http;
        proxy_pass $upstream_proto://$upstream_app:$upstream_port;
    }

    location ~ (/filebrowser)?/api/public {
        include /config/nginx/proxy.conf;
        include /config/nginx/resolver.conf;
        set $upstream_app filebrowser;
        set $upstream_port 80;
        set $upstream_proto http;
        proxy_pass $upstream_proto://$upstream_app:$upstream_port;
    }

    location ~ (/filebrowser)?/share {
        include /config/nginx/proxy.conf;
        include /config/nginx/resolver.conf;
        set $upstream_app filebrowser;
        set $upstream_port 80;
        set $upstream_proto http;
        proxy_pass $upstream_proto://$upstream_app:$upstream_port;
    }

    location ~ (/filebrowser)?/static {
        include /config/nginx/proxy.conf;
        include /config/nginx/resolver.conf;
        set $upstream_app filebrowser;
        set $upstream_port 80;
        set $upstream_proto http;
        proxy_pass $upstream_proto://$upstream_app:$upstream_port;
    }
}

 

I can currently reach it fine via "localIP:7979". But either through Organizr or with "filebrowser.Domain.Net" gives the 502 error. Not sure how to diagnose it even at this point.

 

I did see a couple of remarks about the

1 hour ago, matmat07 said:

But either through Organizr or with "filebrowser.Domain.Net"

i dont use organi... so rather 1st look forward to solve your reverse proxy setup

 

1 hour ago, matmat07 said:

# make sure that your filebrowser container is named filebrowser

your container is named FileBrowser ... case sensitive ... should work when both are on the same proxynet,

as alternative, replace filebrowser with IP and port with 7979 in the swag config ...

 

1 hour ago, matmat07 said:

 set $upstream_app filebrowser;
        set $upstream_port 80;

on all entries ... upstream... 192.... upstre...port 7979

Yea, even though "nslookup" did resolve with caps, it is better to have it without everywhere, thank you.

 

I believe the port should stay 80. Is it the port we're looking at inside docker right? From the same "proxynet" network. I any case, I tried it. The only difference was that "308" changed to "1" in nginx error log:

2024/07/23 13:56:45 [error] 666#666: *308 filebrowser could not be resolved (3: Host not found), client: 192.168.1.1, server: filebrowser.*, request: "GET / HTTP/2.0", host: "filebrowser.domain.net", referrer: "https://organizr.domain.net/"
2024/07/23 14:00:49 [error] 666#666: *1 filebrowser could not be resolved (3: Host not found), client: 192.168.1.1, server: filebrowser.*, request: "GET / HTTP/2.0", host: "filebrowser.domain.net", referrer: "https://organizr.domain.net/"

 

While changing the web adress in this post, I did notice the IP in there points to my real router.

Am I understanding Nginx is trying to resolve "filebrowser" using my router instead of docker's DNS (not sure if there's such a thing, but whatever made nslookup bring up the right internal IP of 172.18.0.12).

 

 

Alright, got it working.

I believe I had some public IP in there from an old internet provider of where the server used to be.

Once I deleted the resolver.conf file, I was at least able to get the default SWAG page. After that, a mix of force refresh, "80" for port, an update of SWAG and a fresh "filebrowser.subdomain.conf" file (which had port 8080 by default), It works.

 

I hope it makes sense for someone, and it'll help if someone come here looking for help like others did in the past.

The resolver file only has "127.0.0.11" in it now. And like I said, Port has to be the "inside docker" one.

 

hi there,

 

I setup FileBrowser today, and after some trouble with NGINX it's running very fine!

One thing is strange however; I created a new user for myself (so I don't use the Admin all the time). Under the Logout-Button, I have a little bar and the info 15.9 GiB of 30 GiB used.  And this is very confusing, because I didn't saw any notion of how I could limit the available space, but these 30GB are vaguely the size of my docker.img, the filling is also quite close. Does this mean that the user folder (which doesn't exist) gets written into the docker image? The Admin user doesn't get this bar and info 

On 2/26/2024 at 5:03 PM, jonskin44 said:

HI thanks for your reply. The only file I can see in appdata/filebrowser is database.db is the config file stored somewhere else?

Likewise.  Am I missing something? Did you figure this out?

hi--I'm a new unRAID user (just set up a server a few weeks ago) and this filebrowser docker container has been one of my favorite community apps so far, fills one of my expectations for my NAS perfectly. The only issue I'm having is that permissions for files uploaded through the browser interface are not being set as I would like. They show up as owner: root permissions: -rw-r--r--, which does not give my linux mint VM running on the server write permissions. Ideally I would want them to show up with write permissions for all, right now I've been manually changing them through the unraid webUI. Is there a way to have newly uploaded files automatically granted write access for all?

 

Thanks in advance for any help!

On 7/23/2024 at 9:52 PM, matmat07 said:

Alright, got it working.

I believe I had some public IP in there from an old internet provider of where the server used to be.

Once I deleted the resolver.conf file, I was at least able to get the default SWAG page. After that, a mix of force refresh, "80" for port, an update of SWAG and a fresh "filebrowser.subdomain.conf" file (which had port 8080 by default), It works.

 

I hope it makes sense for someone, and it'll help if someone come here looking for help like others did in the past.

The resolver file only has "127.0.0.11" in it now. And like I said, Port has to be the "inside docker" one.

 

I have the same issue than you
I try to put the port 8080 so the default port on swag is good
I can reach filebrowser with the ip but the domain fail. error 502 (bad gateway)

It was working before but not anymore (i think because of the last update of swag)

I try a restart of swag but nothing help.

 

 

EDIT : I update the port in the filebrowser.subdomain.conf and put again port 80 and it's work like a charm. Don't understand why it was not working at the first time.

Edited November 16, 20241 yr by Rayman

On 8/14/2024 at 7:47 PM, kory.b said:

way to have newly uploaded files automatically granted write access for all?

may try this

 

Hello,  I'm looking for some input or help:  I'm finding that if I enter a Password, it doesn't stick after a docker update. What I find is that admin/admin is once again made available (making access to the service trivial).

 

This seems like a pretty big show stopper.  Here's what I've done: 

1. Delete everything, fresh install.
2. Install and use Docker defaults, add path to a test folder.  Login, change password (test with logout and it works). Restart container - works.
3. Choose to "force update (of docker)" in Unraid, go back to login - it's been reset. Admin/Admin works, but my changed password is not working.

Is anyone else able to confirm this, or that they don't see this issue? This makes me very uncomfortable trusting this moving forward without understanding this better.

Edited December 19, 20241 yr by Tomahawk51

On 12/19/2024 at 7:08 AM, Tomahawk51 said:

Hello,  I'm looking for some input or help:  I'm finding that if I enter a Password, it doesn't stick after a docker update. What I find is that admin/admin is once again made available (making access to the service trivial).

 

This seems like a pretty big show stopper.  Here's what I've done: 

1. Delete everything, fresh install.
2. Install and use Docker defaults, add path to a test folder.  Login, change password (test with logout and it works). Restart container - works.
3. Choose to "force update (of docker)" in Unraid, go back to login - it's been reset. Admin/Admin works, but my changed password is not working.

Is anyone else able to confirm this, or that they don't see this issue? This makes me very uncomfortable trusting this moving forward without understanding this better.

Yep, seeing the same thing here.  Also noticed I have an appdata folder with only an empty /db folder in it.  Not sure how anything would persist in the current state of this image and template....

 

EDIT - I found that by manually adding the Post argument string in the screenshot from a couple of posts back that now I at least have the database.db in that /db folder. Unless the pw is stored in there, which is not optimal because it makes a reset more difficult, I still think there's an issue.

Edited February 7, 20251 yr by BurntOC

I actually disabled the auth since I use it with a reverse proxy. But, after making any settings changes, I made a backup of the database.db file, stopped the container and restore the database.db, and start up again. Only way it seemed to make the settings "stick."

Edited February 17, 20251 yr by Gex2501

Hi all, I'm trying to get SSO working for FileBrowser with Authelia + NPM but I keep getting the FileBrowser login window after having authenticated with WebAuthn in Authelia. A similar setup works for e.g. Calibre-Web. 

 

I have set `--auth.method=proxy --auth.header=Remote-User` as Additional Requirements and restarted FileBrowser. (source: https://filebrowser.org/configuration/authentication-method#proxy-header)

 

What could be causing this? I think that Authelia and NPM are setup correctly.

has someone succesfully getting this to work? Thanks.

Hello, Im a bit of a noob so bear that in mind, recently I've setup a container with filebrowser, managed to make it work, with no problems using it, but the problem I have is the files and folders created or imported using filebrowser I cant edit or modify them using smbshare, stating I dont have permissions. Any way to fix this?

6 hours ago, Pivias said:

Any way to fix this?

may tr adding this to extra parameters

 

48 minutes ago, alturismo said:

may tr adding this to extra parameters

 

tried it before, get back an error, container doesn´t start

9 hours ago, Pivias said:

tried it before, get back an error, container doesn´t start

then may change permissions ... ?

4 hours ago, alturismo said:

then may change permissions ... ?

yes I did that, didn´t resolve it, but I resolved that issue using this argument
Its creating the files as nobody, but I still cant edit the files owner "nobody" has Read-Write but group and other has "Read-only", any particular reason for what´s causing this?

Is there any way to stop having it default to admin / logfile password every time it updates?

The maintainer of the community app (@knex666) needs to update the CA to match the latest updates upstream:

• Default admin password is now automatically generated on first initialization

• Volume mounts and permissions have been updated: https://github.com/filebrowser/filebrowser/releases/tag/v2.33.0

Edited June 23, 20251 yr by hacdias

3 hours ago, hacdias said:

The maintainer of the community app (@knex666) needs to update the CA to match the latest updates upstream:

• Default admin password is now automatically generated on first initialization

• Volume mounts and permissions have been updated: https://github.com/filebrowser/filebrowser/releases/tag/v2.33.0

@knex666 Any chance you're tracking these latest changes?