HideMe Privoxy

A self-hosted Docker container that runs a WireGuard-based HideMe VPN client with Privoxy and MicroSocks, letting home-network devices send HTTP and SOCKS…

  • Network Services
  • Tools & Utilities
A self-hosted Docker container that runs a WireGuard-based HideMe VPN client with Privoxy and MicroSocks, letting home-network devices send HTTP and SOCKS traffic through HideMe for private, filtered connections.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?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). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

32/100 Low

Maintained
14last commit 595 days ago
Popular
2211 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data
Security check
75no serious findings

Based on 4 of 5 factors.

Availability: platform listings confirmed today, links checked 32 days ago

GitHub stars
11
Open issues
1
Last commit
2025-04-05
Latest release
latest
Activity
stale

Checked 9 days ago - source: GitHub (alturismo/wg_hideme_privoxy)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is not supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Installation Run the Docker image with NET_ADMIN and /dev/net/tun, and add --sysctl net.ipv6.conf.all.disable_ipv6=1 when IPv6 is enabled. Map /config for persistence, expose 8080/tcp for Privoxy and 1080/tcp for MicroSocks, and set LOCAL_NET, HIDEME_SERVER, HIDEME_USER, HIDEME_PASS, and TZ. The README includes a full docker run example. source

Fetched 39 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Can I run only the SOCKS proxy or only Privoxy?

Yes, set HIDEME_SOCKS to off to disable SOCKS, or set HIDEME_PRIVOXY to off to disable Privoxy.

Where should I store the container configuration?

Mount the container path /config to a persistent host path, for example /mnt/user/appdata/wg_hideme_privoxy/:/config:rw.

How do I allow only my local network to use the proxy and let local addresses bypass it?

Set LOCAL_NET to the CIDR mask or comma-separated CIDR masks of the local IP addresses that should access the proxy and bypass it.

Which ports should I publish for the proxy?

Publish port 8080 for Privoxy and port 1080 for the SOCKS proxy, and edit them if using bridge mode.

What extra setting is needed when IPv6 is active on my network?

Add the extra Docker parameter --sysctl net.ipv6.conf.all.disable_ipv6=1 to disable IPv6.

Does the container replace DNS and keep the VPN connected?

The included hide.me client replaces DNS servers, includes a killswitch, and checks for reconnection every 3 minutes.

Answers sourced from github.com

Community

Collected 53 days ago - public community threads