LeakWatch

LeakWatch teaches you which of your Docker containers should be behind a VPN - and shows you, at a glance, whether they actually are.

  • Network Services
  • Security
  • Tools & Utilities
LeakWatch teaches you which of your Docker containers should be behind a VPN - and shows you, at a glance, whether they actually are. Building an *arr stack and not sure what needs a VPN? LeakWatch lists every container, tells you whether a VPN is REQUIRED (torrent/usenet), RECOMMENDED (indexers, *arr apps) or NOT NEEDED (Plex, dashboards, databases), and explains WHY in plain language. Then it checks each container's real public IP and flags anything that should be protected but is leaking your server's real IP. Zero configuration: just set the WebUI port and click Apply - everything else is preset. The scan runs automatically when you open the page. For new users it is a guide to safe setup; for experienced users it is a single dashboard to confirm everything is configured as expected and to catch a VPN that silently dropped.

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.

48/100 Fair

Maintained
60last commit 155 days ago
Popular
2110 GitHub stars
Easy to install
201 install platform, Docker image
Light to run
No data
Security check
85no serious findings, CI, tests, new single-developer project

Based on 4 of 5 factors.

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

GitHub stars
10
Open issues
4
Last commit
2026-06-19
License
MIT
Activity
stale

Checked 7 days ago - source: GitHub (tophat17/LeakWatch)

Resources & Compatibility

Requirements not published yet.

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

First-install notes

No first-install notes yet.

Alternatives

No alternatives collected yet.

Common questions

How does LeakWatch verify that a container is actually behind a VPN?

It finds each container's real public IP and labels the result protected, leaking, or fine on the server IP. This can catch a VPN that silently dropped.

What leak checks does LeakWatch include beyond checking the IPv4 public IP?

It includes IPv6-leak detection, Tor-exit detection, Tailscale/ZeroTier mesh awareness, and a multi-source cross-check.

Should a reverse proxy such as Nginx Proxy Manager be placed behind a VPN according to LeakWatch?

No. LeakWatch lists Nginx Proxy Manager as needing no VPN, because it needs your normal connection and a VPN would break it.

Does LeakWatch explain why each container gets its VPN recommendation?

It gives each container a recommendation and shows a plain-language why on hover. Clicking it opens a full about this app explainer.

Answers sourced from github.com

Community

Collected 47 days ago - public community threads