Tor Proxy leplusorg/tor:latest https://hub.docker.com/r/leplusorg/tor bridge sh false 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. https://github.com/leplusorg/docker-tor/issues https://github.com/leplusorg/docker-tor https://github.com/leplusorg/docker-tor#readme https://raw.githubusercontent.com/raccommode/Raccommode-Unraid-Community-Apps/main/templates/tor-proxy.xml https://www.torproject.org/static/images/tor-logo/Color.png Network:Other Tools:Utilities This container has no web interface and is not a VPN. Configure each client app to use the SOCKS5 proxy explicitly, for example socks5h://UNRAID-IP:9050 or the Tor container name on a custom Docker network. Keep SOCKS Hostname set to 0.0.0.0 so Docker port publishing can reach the proxy. Exposing 9050 on your LAN lets other local clients use it, so restrict access with your network or firewall rules if needed. Do not add a DATA_DIRECTORY variable unless you intentionally override Tor's internal data path. Keep Set Permissions false on Unraid if you see Operation not permitted on /var/lib/tor. Tor can take a short time to bootstrap after startup. Apache-2.0 9050 /mnt/user/appdata/tor-proxy 0.0.0.0 9050 notice false false