Skip to content

File Browser Quantum Runbook

Health Check

{job="filebrowser"} |= "error"

Or check the monitor widget on Glance, which pings http://192.168.1.126:8080.

Common Issues

Container won't start

Check Docker logs:

ssh [email protected] docker logs filebrowser

Common causes:

  • Config syntax error in /opt/filebrowser/data/config.yaml
  • Port conflict on 8080
  • Bind-mount path doesn't exist (LXC misconfigured)

OIDC login fails

  1. Verify PocketID is reachable from the container
  2. Check callback URL matches: https://files.eva-00.network/api/auth/oidc/callback
  3. Verify Vault secrets match the PocketID client credentials

Search not working

File Browser Quantum uses SQLite for indexing. If search returns no results after adding new files:

  1. Wait for the indexer to catch up (runs automatically)
  2. Check logs for indexing errors
  3. If the database is corrupted, delete /opt/filebrowser/data/database.db and restart

Files not visible

Check bind-mount configuration:

ssh [email protected] ls -la /data/

All four directories (unohana, urahara, filedump, dlbox) should be populated. If empty, verify LXC bind-mounts via pct config 126 on chizuru.

Known Issues

Cross-source move/copy — no progress, unresponsive UI

Moving or copying files between sources (e.g. Dlbox → Unohana) works but has poor UX:

  • The Move/Copy button becomes unresponsive during the operation
  • No progress indicator — the UI shows a sad face while the cross-filesystem copy+delete runs
  • Logs may show harmless lstat: no such file or directory errors from retry race conditions
  • Operations do complete successfully (verify in the destination)

This is an upstream FBQ limitation — cross-mount operations require copy+delete under the hood and the UI doesn't handle it gracefully. No config fix available as of v1.3.7-beta.

Redeploy

Trigger the workflow via Forgejo Actions dispatch, or push a change to any file in services/filebrowser/.