armanlife/firefox-vpn-client

Worth a look if you already have a Firefox Account and mainly need browser-style traffic tunnelled, but check the documented port and UDP limits first.

The problem

You want encrypted traffic without paying for a subscription or running a server. Normally that means a paid VPN or assembling a proxy core yourself. This project wraps Mozilla's account-linked tunnel in an app: sign in with a Firefox Account, pick a country, and the client handles the connection. You get a usable tunnel drawing on the 50 GB a month the README says each account includes, with multi-account mode switching when one runs out.

What's different

Rather than running its own network, the client carries traffic through Mozilla's Fastly-hosted servers over HTTP/2 and HTTP/3 tunnels. That gives a free user a ready endpoint list and ping test instead of manual configuration, plus smart routing so local sites open directly without spending data.

Multi-account rotation is the other distinctive piece: when one account's quota ends, the next takes over automatically. That makes several accounts act like one larger allowance, but its value depends on holding multiple accounts and their quotas continuing to exist. The README does not explain how quotas are pooled or what happens when an account fails mid-session.

The same core ships in two shapes. Apps cover graphical use on Android, Windows, macOS and Linux; on headless Linux servers a core provides a web panel, terminal menu and SOCKS5/HTTP proxy ports, which is what makes the project relevant beyond everyday browsing.

Who should try it

Good fit: someone with a Firefox Account who mainly needs web traffic tunnelled on a laptop, phone or small Linux server, and prefers a simple interface over protocol flexibility. The server core with a web panel suits a headless box needing an HTTP/SOCKS proxy.

Poor fit: anyone who needs UDP voice and video calls, online games, mail clients, or SSH beyond the documented GitHub exception. The README states the tunnel is TCP only and restricted to ports 80, 443, 8080 and 8443, so those workflows are refused. Android users relying on push notifications may see some apps notify only when opened, since port 5228 is not carried.

Requirements and limitations

The hard limits decide it: no UDP, web ports only, and the Android notification caveat. These are properties of the upstream servers as described by the project, not likely near-term client fixes, so choosing it means accepting a browser-shaped tunnel. The 50 GB figure comes from the project's description of Mozilla's allowance, not independent measurement.

Setup is straightforward: per-platform downloads, plus an install script and server documentation for Linux and macOS. Ongoing care is mostly watching account quotas and the limits above. Speed and stability claims are author claims, not benchmark evidence.

HotRepo's take

HotRepo tracked the repo on 2026-10-24 and 2026-10-25: two recorded dates. It appeared at #13 on the NEW-REPOSITORY board (新项目榜, not overall Trending) with 159 total stars on 2026-10-25. That supports a snapshot of early attention only; persistence cannot yet be judged. Before committing, verify the documented limitations against the ports and UDP traffic you rely on.