VPNSentinel Server
VPNSentinel Server is a monitoring container that collects keepalives from VPNSentinel clients in VPN containers, displays a traffic-light dashboard for VPN,…
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.
50/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
- No data
Based on 3 of 4 factors.
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
ARM (e.g. Raspberry Pi) is supported.
Checked 9 days ago - source: Docker Hub image tags and published docs
First-install notes
- Start by copying vpn.env.example Copy vpn.env.example to vpn.env before running docker compose. If that file is missing, compose may fail to start the VPN, and if the settings are wrong you may need to restart it after fixing them. source
- Keep these required compose settings In docker-compose.yml, keep privileged: true (special system permissions), UDP ports 500 and 4500, and the /lib/modules mount. IPsec needs those so it can talk to the Linux kernel; without them, the server may not start or devices may not connect. source
- Check logs for VPN login details After it starts, run docker logs ipsec-vpn-server and look for the Server IP, shared key (IPsec PSK), username, and password. You need those exact details to connect your phone, laptop, or other devices. source
- Configure the API key and clients Set an API key on the server and give the same key to every VPNSentinel client; leaving the key empty disables authentication. Install vpn-sentinel-client beside each VPN container and point its server URL at this container's mapped API port. Client status is kept in memory, so it returns after a server restart at the next keepalive, default every 5 minutes. source
Fetched 9 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Can I store the API key, Telegram credentials, and Apprise URLs in files instead of environment variables?
Yes. The API key, Telegram credentials, metrics token, and Apprise URLs can each be read from a file using *_FILE variables or Docker secrets.
What alert destinations can VPNSentinel use besides Telegram?
It can send the same alerts to ntfy, Gotify, Discord, email, and 100+ other services through Apprise.
When does the server report a VPN bypass?
It sends a critical red alert when VPN traffic is not routing through the VPN.
What DNS-related failure does it detect?
It performs DNS leak detection and reports DNS queries that expose your location by bypassing the VPN.
Can one VPNSentinel server monitor several VPN clients?
Yes, it supports monitoring unlimited VPN clients from a single server.
Answers sourced from github.com
Community
No community discussions collected yet.