silverfox-2096/private-browser

Private Browser is a privacy-focused setup that runs Firefox inside an isolated container, routing all internet traffic through a VPN tunnel. The key idea: if the VPN connection drops, the browser loses all internet access immediately. It cannot fall back to your regular network, so your real IP address never leaks. The browser profile also lives entirely in RAM, meaning bookmarks, history, cookies, and downloads are wiped clean every time you shut it down. The project is built from three existing, independently maintained components: Gluetun for the VPN tunnel and firewall kill switch, a Firefox-in-Docker image that provides a browser accessible through a web interface, and nginx as a protective front layer. On top of that, Firefox's own fingerprinting resistance is enabled. The repository itself contains no custom application code, just a Docker Compose configuration file, a short Dockerfile that installs fonts, and two small shell scripts. This means there is no hidden logic to audit or trust. The README is clear about what this tool is and is not. It provides privacy, meaning your ISP, local network, and websites cannot see your real IP. It does not provide anonymity, since your VPN provider can still see your traffic. If you need true anonymity, the README suggests using Tor instead. The project also cannot protect you from a compromised host machine, such as a keylogger. Setup requires Docker and a paid WireGuard VPN subscription. You configure a file with your VPN credentials, create a password for the web login page, then run a launch script. You access the browser through a secure local web address. Daily use is straightforward: start with the launch script, stop with a single command that wipes everything. The README includes troubleshooting for the one known quirk, where restarting the VPN container leaves Firefox attached to a dead network namespace, requiring a manual container restart. A continuous integration pipeline runs security scans on every push and weekly, checking shell scripts, Dockerfiles, and the compose file for known vulnerabilities. The full README is longer than what was shown.