OpenVPN monitoring
TLS-based VPN, config-based — actively verified from ExitProbe's distributed edge probes.
About OpenVPN
OpenVPN is one of the most widely deployed VPN protocols in the world. It runs over TLS (TCP or UDP), supports a huge range of ciphers and authentication methods, and works practically everywhere.
Its flexibility is also its weakness in production: certificate expiry, cipher mismatches and MTU problems often cause partial failures where the port is open but no session can be established.
How ExitProbe tests it
- 1ExitProbe parses your .ovpn profile and initiates a full TLS session from an edge probe.
- 2Authenticates using the credentials or certificates embedded in your config.
- 3Sends verification traffic through the established tunnel to confirm the exit IP.
- 4Reports handshake time separately from total check duration so you can spot degrading TLS performance.
Your credentials are stored encrypted (AES-256-GCM) and only decrypted in memory at check time on the probe running the test. They never appear in logs, API responses, or incident payloads.
Common questions
Yes. The transport mode is read directly from your config file, so proto udp and proto tcp profiles both work without any extra settings.
Your checks start failing with a TLS error and an incident opens immediately — usually days before users report it, if you set a sensible check interval.
Yes. Profiles with embedded <ca>, <cert> and <key> blocks work out of the box; just paste the whole file.
Monitor your OpenVPN server today
Free plan included — real handshakes, exit IP verification, instant alerts.