VPN troubleshooting
If your VPN will not connect — or it connects but a website, app or call still fails — work through the connection one step at a time.
Quick answer
A VPN problem generally falls into one of two groups: the VPN itself will not connect, or the VPN connects but the destination still does not work.
Likely causes can include one server IP being blocked, local Wi-Fi or firewall interference, protocol restrictions, old browser or app sessions, GPS or device signals, account or payment region, app-store region, website VPN detection, or third-party service outages and rules.
Change one variable at a time.Diagnostic router
Choose the state that best matches what you can see. Each path starts with reversible checks and changes one variable at a time.
Connection fails, times out or disconnects immediately.
Credentials, one server, the selected protocol or the local network may be involved.The VPN shows connected, but the destination remains unavailable.
The destination may block one VPN IP or use browser, app, account or device signals.The connection succeeds elsewhere but fails on one local network.
A captive portal, firewall or protocol restriction may be interfering.The app reports the previous or account country after the VPN connects.
GPS, permissions, SIM, app-store, account region or cached state can still matter.The connection is unstable, slow or drops during use.
Distance, unstable Wi-Fi, network switching or client/protocol behavior may be involved.First response
Work in order and note where the result changes. That makes the cause easier to isolate.
Check the client status before troubleshooting the destination.
One VPN server IP may be blocked while another works.
Reconnect first, then fully close and reopen the destination.
This reduces the effect of old cookies and session state.
A difference points toward the original local network.
Availability varies by client, device and platform.
Mobile apps may use GPS or device-level location signals.
Keep the wording, time and affected app or site for Support.
Server troubleshooting
A single VPN server IP may be blocked by a destination while another server in the same country works normally.
Connection options
Protocol and connection-option availability varies by client, platform and server. Do not assume every individual server exposes every protocol.
Modern recommended starting option.
Widely compatible and useful for manual configuration.
OpenVPN configuration tool →A supported option that can be useful around network changes where appropriate.
Available on supported desktop VPNclient applications where ordinary VPN traffic may be interfered with.
L2TP/IPsec and PPTP are retained for compatibility, not recommended as the normal troubleshooting default.
Beyond the VPN IP
A VPN changes network routing and the public VPN IP. A destination may also consider account, device, browser or platform information.
A destination may remember a previous region or login state.
Try a private session or clear data for that destination.
An app may use location permission instead of relying only on IP.
Review permissions and test the web version if available.
Signup or profile information can establish an account region.
Review the provider’s account settings and rules.
Some services may compare payment region with account or IP information.
Do not assume VPN location changes billing eligibility.
The installed app or available catalogue may follow the store account region.
Check the Apple or Google account region where relevant.
A provider may use phone-country or verification information.
Review the service’s supported-country and verification rules.
A destination may identify and block a particular VPN server IP.
Try another current server in the same country.
A destination can use additional browser or device information.
Restart, test a clean session and follow the provider’s rules.
Network comparison
Hotel, airport, public, school, workplace, apartment or restrictive networks may use captive portals, firewalls or filtering that interferes with VPN traffic.
Stealth is an available troubleshooting option, not a guarantee that every network will allow the connection.
Problem-specific paths
Use the guide that matches the destination or connection problem instead of changing unrelated settings.
Network, ISP, country, session or VPN-IP filtering.
Calling traffic, network quality, permissions or local rules.
Provider country, account, billing, phone or workspace rules.
VPN detection, licensing, account or payment-region rules.
Hostname, protocol, credentials or device configuration.
Captive portal, firewall, filtering or unstable access.
Unfamiliar networks, app access and location consistency.
One endpoint, hostname or server IP may be affected.
DNS symptoms
A mismatch between the VPN connection and DNS resolution can create confusing location or access behavior. It is one possible cause, not a diagnosis by itself.
Realistic limits
A VPN cannot guarantee changes to:
Support handoff
Clear comparison results help distinguish a server, protocol, network, destination or account-rule problem.
VPN troubleshooting FAQ
Start with the visible symptom, change one variable and keep the exact error if the issue remains.
The destination may block one VPN server IP, retain an old browser session, or consider account, device or location signals beyond the visible IP address. Try another current server in the same country, restart the destination and test a private browser session.
Verify the supplied VPN account details, try another current server, try another supported protocol or client option, and compare another network. The exact error and the point at which the connection fails are useful for Support.
The Wi-Fi may require a captive-portal login or may restrict a protocol, port or VPN traffic. Complete the Wi-Fi login, reconnect, try another server or supported protocol, and compare mobile data again.
Start with a nearby current server for general use. If a destination requires a particular visible country, try another current server in that same country before changing countries.
Yes, when the client or platform provides another supported option. Start with WireGuard, then consider OpenVPN or IKEv2/IPsec as appropriate. Stealth is available on supported desktop VPNclient applications.
An app may use GPS, device permissions, SIM, app-store region, account country, billing information or cached state. A VPN changes network routing and the visible VPN IP, not every signal on the device or account.
A mismatch between the VPN connection and DNS resolution can contribute to confusing access or location behavior. Reconnect, restart the app or browser, compare another network and try another current server.
A streaming service may identify a VPN server IP or enforce account, payment, app-store and licensing rules. Another server in the same country may help, but a VPN cannot guarantee access to a service or catalogue.
Send the device and OS, current country, network type, server hostname or location, protocol or client option if known, affected destination, exact error, comparison results from another server or network, and a screenshot where useful. Never send a VPN password, full payment-card details, private keys or seed phrases.
Human support
Send the connection details and the checks you already tried.