Skip to main content
0%

VPN Not Working: Step-by-Step Troubleshooting

11 min readUpdated

If your VPN is not working, first identify the symptom: the app will not launch, the connection cannot be established, or the VPN is connected but the service you need will not open. Record the error message, then check the network, client, account and supplied configuration. One failure does not establish a common cause for every VPN.

Sources were checked on October 28, 2026. This is a procedure for your own checks; we have not tested specific clients, devices or leaks for this article.

If you are considering VPNON, the service offers one day of trial access for $1.50. Before paying, check the final price and the next charge time. Under the terms of service, you can cancel the subscription in your account; cancellation and a refund of paid funds are separate actions. Read the refund conditions separately.

Step 1: Local network and internet without VPN

  1. Record whether all sites fail to open or only one service does.
  2. Compare the same service with and without the VPN only when permitted and acceptable for your task. If you cannot disable the VPN, record that limitation.
  3. If possible, compare another device on the same network or the same device on another permitted network. Account for mobile data limits.

The difference can narrow the check but does not prove a router fault, blocking or ISP responsibility. If access disappears when the VPN is disconnected, first check whether connection protection is designed to do this. Network comparisons are described in Apple's guide, and blocking connections outside the VPN in Android's documentation.

Connection testHow fast is your internet right now?
Test your internet?Press to start — takes 30 seconds and up to 50 MB of data
—mspingmax—avg—min——Mbpsdownloadmax—avg—min——Mbpsuploadmax—avg—min—
Jitter—Ping under load—
Last speed test
MetricResultmaxavgmin
Ping—ms———
Download—Mbps———
Upload—Mbps———

Step 2: VPN client, version, and permissions

Check the client version, operating system compatibility and error message. Obtain updates from the official source. Check the device's date, time and time zone; these checks also appear in Apple's guide.

Compare the selected profile and connection method with the provider's instructions. Windows' built-in VPN and a separate app are different methods; not every configuration works with the built-in client. Before replacing a profile, save the settings you need and a way to restore access. Do not publish subscription links, keys or passwords.

If acceptable, restart the client and check another server offered by the same service. Change one parameter at a time and record the result. Deleting the profile, reinstalling and changing country are not mandatory first steps. Check firewall messages using the next section.

On Android:

  1. Open system settings and search for VPN. The path and available options depend on the device.
  2. Open the relevant connection's settings or its app. Check that the intended service is selected; on the first connection, accept the system request only for an app you trust.
  3. Check whether always-on connectivity and blocking connections outside the VPN are enabled, if those options are available. Do not disable them blindly: they may explain why internet access is unavailable until the tunnel is restored.

The path is described in Android Help, and system consent and blocking in the VpnService documentation.

On iPhone, check VPN settings, profiles and network filters using Apple's guide. Do not delete an unfamiliar or work profile as an experiment; coordinate managed device settings with the administrator.

Step 3: Antivirus, another VPN, and corporate policies

Check which VPN and network filters are active. On Android, a user or work profile can have only one active VpnService; this is a specific operating system limit, not a diagnosis for every computer.

Read protection messages and the client's documentation. If a known app is blocked, ask the provider which rule is required. Do not turn off the entire firewall or antivirus, or open arbitrary ports for a check. Microsoft warns that exceptions carry risks too; do not allow an unknown app. See also VPN and antivirus.

On a work or school network, coordinate third-party VPN use and rule changes with the administrator. Do not remove MDM profiles or required filters.

Step 4: The VPN service side

Check the chosen service's official status and support notices. Separately check your account's access status and whether the supplied configuration is current. Do not pay again just because the client failed to connect.

Save the exact error text. For example, the OpenVPN Connect / Access Server documentation associates AUTH_FAILED with invalid credentials or an expired session token. This is an example from a specific system, not an explanation of every VPN message.

The absence of an outage notice does not prove that the service is working correctly. Complaints and differences between networks do not by themselves establish blocking.

Step 5: Protocol and port

Choose only connection methods supported by the client, operating system and your service's server. If the provider offers an alternative profile or an obfuscation/stealth mode, follow its documentation. Having a mode does not guarantee operation on every network. Platform-dependent protocol availability is illustrated in Proton VPN's documentation.

Do not change the port or UDP/TCP arbitrarily: settings must match the server. For example, the original WireGuard protocol sends packets over UDP; this is not a universal switch to TCP in any client. Assess individual providers' wrappers and modes using their documentation.

Save the original settings. Do not disable encryption or certificate verification to establish a connection. Success with another mode does not by itself prove DPI blocking.

How to check that your VPN works

Separate three questions: is the connection established, does the traffic you need pass through the tunnel, and does the service you need work? A connection icon and a test in one browser do not answer all three. An example of included and excluded routes appears in Cloudflare's documentation.

The checks below cover IP, DNS, WebRTC, protection settings and stability. External test sites receive your browser's requests and the address visible to them. Do not enter keys, subscription links or account details there.

Checking the IP Address

  1. Choose one IP check service, such as 2ip.io. If comparison without the VPN is permitted and acceptable, record the displayed address before connecting. Otherwise, note that this baseline is unavailable.
  2. Connect to the selected server and refresh the check in the same browser. Check the client's documentation to confirm whether this browser is included in the tunnel.
  3. Compare the address with the server's expected exit. If the tool shows IPv4 and IPv6, assess them separately.

The country may remain the same; changing it is not a requirement for a working VPN. A changed address shows the result of that browser request, not protection for all apps. If the address differs from what you expect, check the profile, routing and result with support before deciding on a cause.

A difference between 2ip.io and 2ip.ru alone does not establish a VPN fault. If results differ, record the browser and mode used for each check and clarify the route. None of these results by itself confirms encryption.

Checking for DNS Leaks

A DNS test shows the resolvers that handled its test queries. Compare them with the expected client, operating system and browser setup: a third-party resolver or browser DoH may be part of that configuration. The server owner's name does not by itself reveal the entire DNS query path. DoH's role is described in DNSLeakTest's explanation.

  1. Read the description of the chosen test and run a check on dnsleaktest.com if you accept sending test queries.
  2. Save the displayed resolvers and test conditions.
  3. If the result is unexpected, check the VPN and DNS settings documentation or contact support. Do not change DNS blindly.

This test does not check every app and is not an audit of encryption or data retention policies.

Checking for WebRTC Leaks

WebRTC can use network addresses to connect participants. What a page can access depends on the browser, permissions and routing. Address types and modes are described in RFC 8828.

On BrowserLeaks, assess local and public addresses separately. A private local address alone does not mean the ISP's public address was exposed. A public address outside the expected route requires checking the client and browser configuration.

Do not install a random extension or disable WebRTC because of one unclear field: this can disrupt calls and other functions. First find an explanation of the result in the documentation. This test does not confirm the security of the entire system.

Checking Traffic Encryption

An IP change, stability and the absence of a browser warning do not confirm VPN tunnel encryption. HTTPS protects its own connection between browser and site and is not a test of the separate VPN layer. These connections are distinguished in EFF's encryption guide.

Check:

  1. Which protocol and protection mode the client and server documentation specify.
  2. That the profile supplied for this mode is selected and the connection completes without an authentication verification error.
  3. Which limitations and checks the provider describes for your release.

Do not disable certificate verification or encryption to remove an error. These documentation checks do not replace a technical audit; we have not captured or decrypted traffic for this article.

Checking Connection Stability

Record reconnection times, network changes and client messages. Separately note whether access to all resources disappears or only one service fails. A speed fluctuation alone does not establish the cause.

Losing internet access when the tunnel drops can be expected behavior from a kill switch or system blocking of connections without the VPN. The name, scope and behavior of this protection depend on the client and operating system; an icon returning does not prove protection for every route. A specific blocking mechanism is described in Android's documentation.

Check the protection description for your version. Do not disable it or create an artificial dropout for this article; send observations to support if failures recur.

If Your VPN Still Does Not Work

Give official support the operating system and client versions, failure time, network type, error text and results of each permitted comparison. State whether the app fails to launch, a connection cannot be established, or one service fails after connecting.

Remove IP addresses, email, keys, subscription links and tokens from public screenshots and messages. A full log may contain sensitive data: first clarify the required excerpt and official way to send it.

One failed connection does not establish long-term blocking or a need to buy another VPN. Coordinate further changes with the administrator if the network is managed.

FAQ

Why won't the VPN turn on?

If the app itself will not launch, first check compatibility, its version and the operating system message. If the app opens but cannot establish a connection, move on to the network, profile and account: that is a different symptom.

What should I do if the VPN won't connect?

Record the error and check the service's official status and supplied configuration. Compare another permitted network or server if acceptable; do not disable protection or change everything at once.

Why is the VPN connected but not working?

Connection status does not confirm every app's route or the availability of a particular site. Check whether the relevant app is included in the tunnel, the expected exit IP and DNS settings; do not treat one unclear result as proof of a leak.

Author: — Cybersecurity specialist, VPNON