filebrowser: --auth.method='none' gets ignored

Description I’m trying to mount filebrowser behind a caddy proxy /files/ http://filebrowser. I don’t need any authentication, so I passed command: "--auth.method='none' --baseurl /files" in my docker-compose.yml.

Expected behaviour filebrowser should not ask for any username or password

What is happening instead? filebrowser asks for username + password

How to reproduce?

version: '3.5'
services:
  filebrowser:
    image: filebrowser/filebrowser
    command: "--auth.method='none' --baseurl /files"
    depends_on:
      - proxy
  proxy:
    image: abiosoft/caddy
    ports:
      - '80:80'
    volumes:
      - './Caddyfile:/etc/Caddyfile'

http://0.0.0.0:80 {
    proxy /files http://filebrowser
}

About this issue

Original URL
State: closed
Created 6 years ago
Comments: 23 (9 by maintainers)

Most upvoted comments

@alx 2.0 introduced many changes. Please take a look at

Your filebrowser.json contains some not-used options. Try replacing it by:

{
  "port": 8888,
  "baseURL":"/filebrowser",
  "address": "",
  "database": "/etc/database.db",
  "root": "/srv/data",
  "noauth": true
}

hacdias on Feb 15, 2019

@alx 2.0 introduced many changes. Please take a look at

https://docs.filebrowser.xyz/configuration/authentication-method

https://docs.filebrowser.xyz/cli/filebrowser

Your filebrowser.json contains some not-used options. Try replacing it by:
{
  "port": 8888,
  "baseURL":"/filebrowser",
  "address": "",
  "database": "/etc/database.db",
  "root": "/srv/data",
  "noauth": true
}

Wow! It works for me. BTY, maybe need to touch a file named /etc/database.db or the container would create a directory named /etc/database.db and the container got killed.

d0zingcat on Dec 16, 2020

@alx please remove database.db, clean the cache and try again. Your logs show calls to endpoints from the previous version which leads me to conclude that your browser has the previous version cached. The options root and noauth on your configuration file are only used the first time (when there is no database created). Further changed to those parameters won’t affect anything.

hacdias on Feb 15, 2019

@hacdias thanks a lot for your help, it was an issue with the docker cache.

alx on Feb 15, 2019

I had the same issue, after pulling the latest filebrowser image on docker hub it works like a cham, thanks 👍

dbeniamine on Dec 27, 2018