filebrowser + apache-reverse-proxy + docker-compose

[mqu]

here is an example of using Filebrowser with a little bit strengthened docker-compose.yml, Apache reverse-proxy.

apache2 site configuration with redirect, reverse-proxy and Websocket.

<VirtualHost *:80>
        ServerName filebrowser.domain.local
        ServerAdmin admin@domain.local

        ErrorLog ${APACHE_LOG_DIR}/glacier-error.log
        CustomLog ${APACHE_LOG_DIR}/glacier.log combined

        # Enforce HTTPS:
        RewriteEngine On
        RewriteCond %{HTTPS} !=on
        RewriteRule ^/?(.*) https://%{SERVER_NAME}/$1 [R,L]
</VirtualHost>

<VirtualHost *:443>
	ServerName filebrowser.domain.local
	ServerAdmin admin@domain.local
	# ...

	RewriteEngine On
	ProxyPass / http://localhost:8080/
	ProxyPassReverse / http://localhost:8080/
	ProxyPreserveHost On

	RewriteCond %{HTTP:Upgrade} =websocket
	RewriteRule /(.*) ws://localhost:8080/$1 [P,L]

</VirtualHost>

filebrowser.json

{
  "port": 8080,
  "baseURL": "",
  "address": "",
  "log": "stdout",
  "database": "/srv/fb/filebrowser.db",
  "root": "/srv/fb/data",
  "username": "admin"
}

docker-compose.yml

version: '3.7'

# doc: https://filebrowser.org/installation
x-defaults-std:
    &default-settings-std
    restart: unless-stopped
    logging:
      driver: "json-file"
      options:
        max-size: "20k"
        max-file: "5"
    tmpfs:
      - /tmp
      - /run
    networks:
     - private

x-defaults-ress-limit:
    &defaults-ress-limit
    deploy:
      restart_policy:
        condition: on-failure
        max_attempts: 5
      resources:
        limits:
          cpus: '0.5'
          memory: 150M
        reservations:
          memory: 25M
    ulimits:
      nproc: 128
      nofile:
        soft: 1024
        hard: 2048
    mem_swappiness: 0
    memswap_limit: '200M'
    cap_drop:
     - ALL

x-defaults-healthcheck:
   &defaults-healthcheck
   healthcheck:
      test: "curl -f http://localhost:8080/health || exit 1"
      interval: 2m
      timeout: 5s
      retries: 3
      start_period: 15s

services:
  app:
    <<: *default-settings-std
    <<: *defaults-ress-limit
    <<: *defaults-healthcheck
    image: filebrowser/filebrowser
    read_only: true
    user: 1000:1000
    ports:
      - "8080:8080"
    volumes: 
      - ./filebrowser.json:/srv/fb/filebrowser.json
      - ./data/fb:/srv/fb/
    entrypoint: /filebrowser --config /srv/fb/filebrowser.json

networks:
  private:

install

mkdir -p ./data/fb ; sudo chown 1000:1000 ./data/fb

[gedw99]

thanks.

can also use caddy too to so the same in case you didn't know.

[nanouk76]

Hi,
I would very much like for you to guide me in using Caddy. The instructions for that are pretty scant on Internet. I am unable to make it work at the moment. I have this in my Caddyfile for Jellyfin and it works beautifully :

streaming.website {
         reverse_proxy 127.0.0.1:8096
}

But when I add this for filebrowser :

filebrowser.website {
         reverse_proxy 127.0.0.1:444
}

and reload caddy, the page loads with error 502.
This is what I have in filebrowser.json :

{
  "port": 444,
  "baseURL": "",
  "address": "192.168.0.69",
  "log": "stdout",
  "database": "/home/joe/filebrowser/filebrowser.db",
  "root": "/media/video"
}

If I comment out the filebrowser entry in Caddyfile, reload caddy, and restart filebrowser with the following filebrowser.json :

{
  "port": 444,
  "baseURL": "",
  "address": "192.168.0.69",
  "log": "stdout",
  "database": "/home/joe/filebrowser/filebrowser.db",
  "root": "/media/video",
  "cert": "/etc/letsencrypt/live/****/cert.pem",
  "key": "/etc/letsencrypt/live/****/privkey.pem"
}

I have access to the filebrowser webpage.

What am I doing wrong? Any help would be very much appreciated since thanks to caddy the TLS certificate would be renewed automatically. TIA.

[nanouk76]

No one? Really? It certainly seems like the easiest thing in the world but it's a no go for me. I have been trawling the web in search for an answer but all in vain. Changing the port did not change anything. I am running latest filebrowser v. 2.27.0 installed as per the installation instructions
curl -fsSL https://raw.githubusercontent.com/filebrowser/get/master/get.sh | bash
I am not running filebrowser in a docker or other container.
This in Caddyfile

my.domain.name {
         reverse_proxy 127.0.0.1:444
}

serves me a 502 error.
So at the moment, I still have to do a port redirection from the wan side of my router to 444 on the internal filebrowser server. Not happy with that since theoretically redirecting ports 80 and 443 to the caddy server should do it. And the SSL part should be taken care of transparently. I am really banging my head here because the caddy reverse proxy solution works just fine for my other self-hosted sites. Anyone? Pretty please?

[nanouk76]

Hmm, anybody home?
Looks like the place is moreless deserted... It seems this discussion thread is not actively monitored by the users of filebrowser or the developer(s). I can't imagine I am the only person with this problem. I am an absolute noob when it comes to proxies et al but I can copy bits of code OK to suit my needs. Even asking ChatGPT has provided me with no viable anwsers. So, I am a a complete loss. In the hope someone somewhere will get this message in a bottle...