FileBrowser Is Officially Dead — Now What?

FileBrowser Is Dead. RIP. #

So, FileBrowser has officially been EOL’d (End of Life’d). The slick, lightweight file manager you could spin up faster than your coffee machine? Gone. No updates. No security patches. Just you and the ghosts of GNOME 2.

The thread on r/selfhosted (link here) made the rounds recently, and while it wasn’t surprising, it still sucks. Someone mentioned it was kind of limping already pre-2023 once development slowed to a crawl, but now it’s been formally put to rest. If you’re still using it on a public-facing server, take this as your wake-up call to migrate. Like yesterday.

But to where? Let’s talk options.

Option 1: Serve Static Files With Caddy #

Quick. Lightweight. Barebones. If you just need files served, Caddy might be overkill, but damn if it isn’t easy.

Install it by grabbing the binary:

sudo apt install -y debian-keyring debian-archive-keyring apt-transport-https
curl -1sLf 'https://dl.cloudsmith.io/public/caddy/stable/gpg.key' | sudo gpg --dearmor -o /usr/share/keyrings/caddy-stable-archive-keyring.gpg
curl -1sLf 'https://dl.cloudsmith.io/public/caddy/stable/debian.deb.txt' | sudo tee /etc/apt/sources.list.d/caddy-stable.list
sudo apt update
sudo apt install caddy

Then throw a quick Caddyfile together:

:80
root * /path/to/share
file_server browse

Spin it up:

sudo systemctl start caddy

Boom. Files accessible. If you want nice HTTPS certs out of the box, point a domain at it and tweak your config. Hard to argue with a ~20MB memory footprint and basically zero setup.

Downside? No user management. No upload UI. It’s like handing out open keys to your garage. Suited for ultra-private LANs or public/download-only sharing, but if you need ACLs, keep reading.

Option 2: Cloud Commander for File Manager Lovers #

If you liked FileBrowser’s vibe, Cloud Commander is the closest doppelganger. It’s Node.js-based, which might be a dealbreaker for some folks, but it runs on literally everything.

Install:

npx cloudcmd --port 8338

The UI is double-pane, Midnight Commander-style. You get uploads, downloads, basic auth built-in, and some bonuses like an embedded terminal. It’s like your high-school computer teacher’s dream app.

Memory usage? Around 40-60MB in my tests.

The catch? It’s not as pretty as FileBrowser. The UI is functional, not flashy, and configuration lives entirely in ENV vars or CLI args. Not a dealbreaker, but it’s definitely more “tinker-y.”

Option 3: Move Full Cloud — Nextcloud or Seafile #

Sometimes, you don’t replace a knife with another knife. You get a sword—or in this case, a full-blown cloud suite.

Nextcloud #

Nextcloud shines if you’re already deep in the self-hosting rabbit hole. Apps galore, from file-sharing to collaborative document editing.

But here’s the thing: it’s heavy. A modest install needs 1-2GB of RAM on the low end, quickly climbing with plugins. Plus a proper database backend (MariaDB/PostgreSQL). On the upside, deploying via Docker is easy:

docker run -d -p 8080:80 \
    -v /data/nextcloud:/var/www/html \
    nextcloud:apache

You’ll need to hook it up to a reverse proxy (like Nginx or Traefik) for HTTPS. If you can tolerate the weight, it’s hard to beat.

Seafile #

More streamlined than Nextcloud. It’s like Nextcloud if you stripped out the extras and doubled down on straightforward file syncing and sharing. RAM usage is closer to 512MB-1GB, and it’s much faster with large libraries.

Migration Strategy: What Now? #

Before you panic and nuke your FileBrowser install, collect your stuff:

1. Back up your FileBrowser instance.
   Just tarball the volume:

   tar -cvzf filebrowser-backup.tar.gz /path/to/your/filebrowser/data
   

2. Audit permissions.
   Some options (like Caddy) won’t enforce ACLs by default.

3. Test locally before exposing to the world.
   The selfhosting world is 50% learning curve, 50% keeping your server off Shodan.

FAQ #

1. Is FileBrowser still safe to use? #

Not really. It still “works,” but unmaintained software is a minefield. It’s only a matter of time until someone discovers a critical CVE. As one Redditor bluntly said, “Use at your own risk and don’t come crying when your server gets owned.”

2. Can I fork FileBrowser? #

Sure, but do you want to? If you have the dev skills to fork and maintain, you probably don’t need FileBrowser to begin with. Most folks are better off migrating to an actively-maintained project.

3. What about Samba? #

Samba is the old-school favorite, but here’s the thing: it’s clunky. Fine for LAN use if you’re okay fiddling with smb.conf, but compared to modern web UIs, it’s like commuting with a typewriter.