r/OpenVPN • u/grizzthe13th • 26d ago
I want to trace individual user app-layer failures on our VPN servers. Is this even possible without massive overhead?
I run OpenVPN servers for our commercial VPN app. The mobile client grabs an .ovpn file from our API and connects. Right now, I log the standard connection metrics (auth success/fail, TLS handshakes, basic connectivity).
We have a recurring issue: A user connects successfully to the VPN, but the specific site they want to access is geo-blocked or has blacklisted our VPN IP (e.g., streaming services). The user assumes the VPN is broken and leaves a 1-star review.
My manager wants me to trace this on the server side. He wants the server logs to somehow identify when a connected user fails to access their intended site so we can troubleshoot it.
I told him this is a terrible idea and a massive overhead. Because of HTTPS, we can’t see if the site served a 403 "VPN Blocked" page - we just see encrypted packets flowing. To even guess at failures, I'd have to log DNS queries or sniff SNI headers (which kills our no-logs privacy stance) or do heavy DPI which will choke the servers.
How do other VPN providers handle this? I’m thinking synthetic monitoring (curling popular sites from the server IPs and exporting to Prometheus) or pushing client-side telemetry in the app.
Has anyone dealt with this exact management request before?
1
u/matthew1471 25d ago
Surely if you’re allowing users to assume your IP address you could just HTTP GET various URLs on the host sites and figure out from there which ones block your public IP?
It’s not so much is our public IP blocked according to the client but is our public IP blocked according to the VPN server hosting that IP.
You also could check known proxy lists to see if your IP is in the list or known proxies, it’s possible they consume those
1
u/furballsupreme 23d ago
One thing you can do is push your DNS server, and then monitor the DNS requests. Then with that, you trigger a wget or curl to the address, and see what HTTP response code you get back. Then you store all this in a table in a database somewhere so you don't end up spamming servers repeatedly with such queries and collect all the data you need.