vpn-sentinel-client agigante80/vpn-sentinel-client:latest https://hub.docker.com/r/agigante80/vpn-sentinel-client none sh false https://github.com/agigante80/VPNSentinel/issues https://github.com/agigante80/VPNSentinel VPNSentinel client: runs inside your VPN container's network (for example gluetun) and reports every 5 minutes by default (VPN_SENTINEL_INTERVAL, in seconds) whether traffic really goes through the VPN and whether DNS leaks, to a VPNSentinel server. Setup: (1) In Extra Parameters, change gluetun in --network=container:gluetun to the exact name of your VPN container. (2) Set the server URL to http://HOST:PORT, where HOST is the Unraid host and PORT is the server's mapped API port. (3) In the VPN container, set FIREWALL_OUTBOUND_SUBNETS to include the LAN subnet of that host, otherwise the keepalive is blocked and the client never turns green; the client then logs "Failed to send keepalive" and does not appear on the dashboard. (4) Use the same API key and API path as the server. Notes: recreating the VPN container breaks this container until it is recreated too, and Unraid may display the port mappings wrongly when --network= is set in Extra Parameters. https://raw.githubusercontent.com/agigante80/VPNSentinel/main/docs/images/icon-256.png Network:Management Tools: https://raw.githubusercontent.com/agigante80/VPNSentinel/main/unraid/vpn-sentinel-client.xml --network=container:gluetun A running VPN container (for example gluetun) and a VPNSentinel server. /api/v1 UTC