Tor-Proxy
Tor Proxy runs the Tor network daemon as a SOCKS5 proxy in a container, so other apps can route explicitly configured outbound traffic through Tor.
Platform availability
Available on 1 of 6 install platforms
- Unraid
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
Also on Docker Hub and GitHub
Health score
69/100 Good
- Maintained
- 100last commit 8 days ago
- Popular
- 3134 GitHub stars
- Easy to install
- 351 install platform, install notes, Docker image
- Light to run
- 95512 MB minimum RAM, runs on ARM
How is this calculated?
A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). Factors without data are left out and the rest are rescaled.
Availability: platform listings confirmed today
- GitHub stars
- 34
- Open issues
- 1
- Last commit
- 2026-09-27
- Latest release
- v3.24.2
- License
- Apache-2.0
- Activity
- steady
Checked 7 days ago - source: GitHub (leplusorg/docker-tor)
Resources & Compatibility
Minimum requirements: 512 MB RAM. ARM (e.g. Raspberry Pi) is supported.
Checked 7 days ago - source: Docker Hub image tags and published docs
First-install notes
- Keep your onion service key safe If you create an onion service, save the ServiceID and PrivateKey that Tor returns. Losing the private key means your existing .onion address can no longer be used. source
- Use .exit to choose an exit node To reach a site through a named Tor exit node, use the documented forms like exampletornode.exit or www.example.com.exampletornode.exit. Without that notation, you cannot direct traffic through that particular exit. source
- Leave pluggable-transport ports local If you add a pluggable transport, an optional helper that makes Tor traffic harder to fingerprint, the examples bind the local control channel to 127.0.0.1. That is loopback, so keep it on the same machine; publishing it can expose Tor internals. source
Fetched 7 days ago - each note links to its source
Variants
Alternatives (12)
- Hotspot Shield - Secure fast VPN to protect identity and hide location.
- Hyphanet - Hyphanet (former Freenet) is free software which lets you anonymously share files, browse and publish "freesites" (web sites acce…
- I2P - I2P (Invisible Internet Protocol) is a universal anonymous network layer.
- Nym - Offers decentralized mixnet routing for network-level privacy, blocks surveillance and metadata leaks via blinded, re-randomizable credenti…
- Onion.ws
- Orbot - Orbot is a freely licensed open-source application developed for the Android platform.
- Proxy Mask
- Shadowsocks - Shadowsocks is a self-hosted SOCKS5 proxy that uses the open-source Shadowsocks encryption protocol.
- Tor - Tor is free software and an open network that helps you defend against traffic analysis, a form of network surveillance that threatens pers…
- Tor Browser - The Tor software protects you by bouncing your communications around a distributed network of relays run by volunteers all around the world…
- Yggdrasil - A proof-of-concept scalable IPv6 meshnet, featuring end-to-end encryption, a unique spanning tree routing algorithm and aiming to implement…
- ZeroNet - ZeroNet uses cryptography (Bitcoin library) and BitTorrent DHT (centralized trackers) to build a distributed censorship-resistant network.
Checked 4 days ago - source: AlternativeTo
Common questions
How do I make another Docker container route traffic through the Tor proxy?
Use a compose file with a tor service and link your app container to it, then set ALL_PROXY to the tor service's port 9050. Check that the app honors ALL_PROXY, otherwise it may bypass Tor.
How can I verify that the containerized Tor proxy is actually working?
After startup, query Tor's IP-check endpoint with curl using the SOCKS5 proxy and hostname proxy settings. This confirms that outbound traffic is being sent through Tor.
Which environment variables control the generated Tor configuration?
The container generates its torrc at startup from a template, and DATA_DIRECTORY, LOG_LEVEL, LOG_FILE, SOCKS_HOSTNAME, SOCKS_PORT, and TORRC_APPEND can be set with environment variables. The default data directory is /var/lib/tor.
If I create an onion service, what should I back up?
Save the ServiceID and PrivateKey that Tor returns. Losing the private key means the existing .onion address can no longer be used.
Answers sourced from github.com, spec.torproject.org
Community
- Proxy Network How the Tor Network : r/selfhosted - Reddit (reddit)
- Tor Project Forum - Defend yourself against tracking and surveillance ... (forum)
- VPN discussion - ask all your VPN related Tor questions here (reddit)
- Newest Questions - Tor Stack Exchange (forum)
Collected 6 days ago - public community threads