File Browser
User-friendly file management with a web UI
The File Browser maintainer has announced that the project is being archived. Key points:
- Repository archived 2026-09-01 — it closes to new issues and pull requests on that date.
- Final release already shipped — there will be no further releases, bug fixes, or security fixes.
- Known unfixed vulnerabilities — the maintainer notes issues in command execution and session handling that will not be addressed.
- Do not expose it directly to the internet — upstream advises running it behind a reverse proxy that terminates TLS and handles authentication.
QuickBox status: QuickBox serves File Browser through the user-scoped nginx reverse proxy (route /username/filebrowser/) on the QuickBox HTTPS vhost, with the File Browser service bound to loopback rather than exposed directly to the internet, and every request gated by a per-user File Browser login (JSON authentication against the per-user database). Because the project is archived, the QuickBox team will provide no further updates or support beyond this documentation — treat this page as reference for existing installations.
Overview
File Browser provides a file managing interface within a specified directory and can upload, delete, preview, rename, and edit files. QuickBox Pro installs File Browser as a per-user service, creates a per-user database, and exposes it through the user-scoped reverse proxy path.
Key features
These highlights focus on how QuickBox configures File Browser for each user.
User-scoped root
Each user’s root is set to /home/username/ with a matching base URL of /username/filebrowser/.
Per-user login
QuickBox creates a File Browser user named username in the per-user database.
Per-user database
Settings and users live in /home/username/.config/Filebrowser/filebrowser.db.
Per-user service
Runs with a templated systemd unit named filebrowser@username.
When to use it
File Browser is ideal when you need a lightweight, browser-based file manager for user home directories.
Good fit
- You want a web UI to manage files inside user home directories.
- You need per-user access with QuickBox-managed credentials.
What QuickBox sets up
- QuickBox configures a user-scoped File Browser instance at /username/filebrowser/.
- Each user gets their own database and log directory under /home/username/.config/Filebrowser.
Installation
Install from the Dashboard
Open App Dashboard → Package Management (/dashboard?mode=packages), find File Browser
in the catalog (browse the File Management category or search), and click Install. The
dashboard streams the install log live and File Browser appears in your Application Control
panel when it finishes. There is nothing to pick in the dialog — File Browser is a plain
install. Reinstall, Update, and Remove are available from the same panel.
What you see is gated by your account: admins manage any user’s apps; regular users manage their own. See App Management for the full flow.
Because the File Browser project is archived, Update will not pull new upstream releases — none are expected. Treat this app as reference for existing installations.
Install from the CLI (automation)
The CLI runs the same scripts as the Dashboard and is suited to automation and scripting:
qb install filebrowser -u username
qb reinstall filebrowser -u username
qb update filebrowser -u username
qb remove filebrowser -u usernameFull flag reference: CLI Reference.
Access and authentication
URL / route
QuickBox configures File Browser with a user-scoped base URL and reverse proxy route:
/username/filebrowser/
The dashboard Launch action opens the same user-scoped route.
Credentials / tokens
QuickBox creates a File Browser user for each QuickBox user and sets the password using the QuickBox user password. If the password is shorter than 12 characters, QuickBox pads it with random alphanumerics before writing it to the File Browser database.
Security notes
File Browser is configured to use JSON authentication and stores its settings and users in /home/username/.config/Filebrowser/filebrowser.db.
Ports and networking
QuickBox assigns the File Browser port dynamically. It selects a random base in the 8200–8300 range and then sets the web port to that base plus 10 (typically 8210–8310).
You can confirm the live port in the dashboard Service Control list, where the File Browser row displays the assigned port in the port field.
Configuration and files
The File Browser configuration, logs, and database are stored per user.
Additional files and paths used by QuickBox:
/usr/local/bin/filebrowser/etc/nginx/software/username.filebrowser.conf/etc/systemd/system/filebrowser@.service
Common tasks
Use the dashboard Service Control list for File Browser to start, stop, refresh, and launch the web UI. The same panel shows the current assigned port.
Best practices
These recommendations align with how QuickBox configures File Browser.
Do
- Use the dashboard port field to confirm the assigned File Browser port.
- Keep the File Browser database at
/home/username/.config/Filebrowser/filebrowser.dbintact for user access. - Use
qb update filebrowserto move to the latest build available for the archived project (no new upstream releases are expected).
Don't
- Do not assume a fixed port, since QuickBox assigns the web port dynamically.
Troubleshooting
These checks map to the configuration and dashboard controls provided by QuickBox.
Verify the nginx reverse proxy exists at /etc/nginx/software/username.filebrowser.conf and that the File Browser service is running in the dashboard Service Control list.
QuickBox may pad short passwords to at least 12 characters before creating the File Browser user.
The assigned port is shown in the File Browser row of the dashboard Service Control list. Use that value when validating connectivity.
Resources
These links are derived from the QuickBox release source for File Browser.
Resources
Join the Community
Media server operators sharing configs, getting support, and shaping the future of QuickBox Pro.