VPNSentinel Client

VPNSentinel Client is a lightweight monitoring container that attaches to an existing virtual private network (VPN) container such as Gluetun and checks,…

  • Monitoring & Logging
  • Network Services
  • Tools & Utilities
VPNSentinel Client is a lightweight monitoring container that attaches to an existing virtual private network (VPN) container such as Gluetun and checks, every five minutes by default, whether traffic really goes through the VPN and whether Domain Name System (DNS) queries leak. It reports results to a VPNSentinel server, giving homelab operators of WireGuard or OpenVPN containers a traffic-light dashboard status and instant Telegram alerts when their tunnel fails.

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.

45/100 Fair

Maintained
88last commit 9 days ago
Popular
00 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
2016 GB minimum RAM, runs on ARM

Availability: platform listings confirmed today

GitHub stars
0
Open issues
7
Last commit
2026-11-12
Latest release
v1.1.18
License
MIT
Activity
rising

Checked 9 days ago - source: GitHub (agigante80/VPNSentinel)

Resources & Compatibility

Minimum requirements: 16 GB RAM. ARM (e.g. Raspberry Pi) is supported.

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

First-install notes

  • Install the VPN client for your distro Use the install command given for your Linux distro (for example sudo apt install proton-vpn-gnome-desktop on Debian/Ubuntu) to get the client. Don't run the desktop app and command-line client at the same time, because they can clash and drop the connection. source
  • Start WireGuard with the exact config To start a WireGuard VPN tunnel, run sudo wg-quick up <config-file> in a terminal, where sudo gives the command the needed system permission. If the file name is wrong or you forget sudo, the tunnel won't start and your traffic stays unencrypted. source
  • Add openresolv for terminal OpenVPN If you use OpenVPN from the terminal, install OpenVPN and openresolv, a small helper for DNS (name-to-IP lookup), as well. This helps keep DNS requests inside the VPN, which prevents DNS leaks and broken lookups. source
  • Attach the client to your VPN container Put the client on the VPN container's network: in Extra Parameters, replace --network=container:gluetun with the exact name of your VPN container, point the server URL at the Unraid host IP plus the server's mapped API port, and use the same API key and API path as the server. source
  • Allow the keepalive to reach the server In the VPN container, set FIREWALL_OUTBOUND_SUBNETS to include the Unraid host's LAN subnet. Otherwise the client's keepalive is blocked, it logs 'Failed to send keepalive', and it never turns green on the dashboard. Recreating the VPN container also requires recreating the client. source

Fetched 9 days ago - each note links to its source

Alternatives (2)

Checked 9 days ago - source: AlternativeTo

Common questions

How do I attach the VPNSentinel client to the VPN container it should monitor?

In the client's Extra Parameters, replace the network flag with --network=container:NAME, where NAME is the exact name of the VPN container. The client must run in that same network namespace.

Why does the client log “Failed to send keepalive” and not show on the dashboard?

The VPN container may be blocking traffic to the host. Set FIREWALL_OUTBOUND_SUBNETS in the VPN container to include the host's LAN subnet.

Which authentication settings does the client need?

It must use the same API key and the same API path as the VPNSentinel server.

How often does the client report by default?

It reports every 5 minutes by default. The interval is controlled by VPN_SENTINEL_INTERVAL, in seconds.

Answers sourced from github.com

Community

Collected yesterday - public community threads