One website does not work through VPN: how to diagnose it
When only one website fails, the VPN tunnel is usually not the whole story. The cause can be DNS, browser cache, CDN routing, site policy, DPI, or packet size.
Quick answer
Compare the same URL without VPN, with another VPN server, in another browser, and on another network. If only one destination fails, collect the URL, server, time, and exact browser error before changing many settings.
Symptom, cause, check, fix
Start by proving the scope. A single-site failure is different from no internet, DNS outage, or a broken app route.
Use the same page, same browser, and same network for the first comparison so the result is readable.
| Symptom | Likely cause | How to check | How to fix |
|---|---|---|---|
| Only one domain fails | Site policy, CDN path, or blocklist | Try another VPN server and direct access | Change location and clear browser state |
| Subdomain fails, main site works | DNS or CDN edge mismatch | Compare DNS answers before and after VPN | Flush DNS and test another resolver |
| Reset or timeout | DPI, MTU, or middlebox | Try another network and smaller payload site | Change server and collect timestamp |
What to do if it still fails
Do not send account pages or private URLs to support. Send the public hostname, selected VPN server, network type, exact error, and whether another server worked.
If a site blocks datacenter traffic, the clean fix may be a different exit location rather than a local app change.
Checklist
- ✓Test direct access
- ✓Test another VPN server
- ✓Test another browser
- ✓Record the exact error and time
FAQ
Does one blocked site mean the VPN is broken?
Not necessarily. It often points to destination policy, CDN routing, or filtering on one path.