Connection help
VPN Not Connecting? A Safe Troubleshooting Checklist
Diagnose a VPN that will not connect without disabling security: check the underlying network, account, app, server and DNS symptoms step by step.
Separate the symptom from its cause
A VPN that stays on connecting, connects without loading websites, or drops whenever Wi-Fi changes can involve different faults. Reinstalling everything at the first sign of trouble makes those faults harder to distinguish. Start by recording what you actually see: the app version, operating system, network type, selected location, time and exact message. If you are testing JungleVPN, check the current test-preview information first. A website demo, downloaded installer or activation screen does not itself establish that a production tunnel has been provisioned.
Work through the checks below in order and change one thing at a time. Keep notes about what changed and whether it helped. Do not post activation codes, private keys, passwords or complete configuration files in a public forum. A useful support request normally begins with the symptom and a small amount of redacted context, not a dump of everything stored on the device.
Check the connection underneath the VPN
Confirm that your device has joined the network you intended to use. If you are at a hotel, airport or café, determine whether a legitimate sign-in page still needs to be completed. An uncompleted network portal can stop the VPN from reaching its server even though the Wi-Fi symbol is visible. Ask the venue for the correct sign-in method rather than installing software suggested by an unfamiliar page.
If you can safely use a separate trusted network, compare the same app there. A problem on one network but not another is a useful clue; it is not proof of a deliberate block. Keep sensitive tasks paused if you cannot establish the required protection. Our public Wi-Fi travel checklist explains the preparation and portal checks in more detail. Never bypass a browser security warning as a shortcut to getting online.
Verify the account, profile and supported app
Check that the product, account or issued configuration you are using is intended for that application and operating system. Confirm expiry, device limits and any activation step through the provider’s own documentation. A code displayed by a demonstration checkout may not be a credential that a native application can redeem. Avoid repeatedly issuing new codes or deleting a working entitlement while trying to diagnose an unrelated network failure.
For Windows, Microsoft’s VPN connection instructions distinguish having a profile from connecting with it. They also direct users to their provider or administrator for the correct connection details. Do not guess a protocol or insert a random server address into the built-in Windows VPN form. Some services require their own application, and a profile for one protocol cannot simply be relabelled as another.
Use the operating system’s actual connection view
Look at the app and operating system together. A status notification can tell you which VPN profile is active, while the provider’s application may explain a failure in more detail. On Android, settings labels and available features can vary with the manufacturer, Android version and app. Follow the instructions for the device you have rather than a screenshot from a different model.
The Android VPN help page describes the system’s VPN connection and settings controls. Do not assume that an always-on option or a traffic-blocking setting is implemented identically by every VPN app. If a work profile or employer-managed configuration is present, ask its administrator before changing it. The purpose of this check is to identify conflicting or unexpected profiles, not to erase managed security settings.
Test location and browsing without weakening security
If the provider supports choosing another available server, try one alternative and note the result. Keep the test small: one location, one trusted website and one clear outcome. An unavailable location, interrupted service or routing problem can look similar from the client. If every location fails on multiple trusted networks, further random switching is unlikely to provide useful evidence; collect the common error and contact support.
When the app reports connected but websites do not resolve, note whether all destinations fail or only one service. DNS settings, a captive portal, an app-specific error and a service outage require different responses. Do not change global DNS, routing, IPv6 or firewall settings blindly. Those changes can affect other applications or conceal the original fault. Our explanation of VPN protection boundaries also explains why one successful IP check is not a complete privacy test.
Escalate with a small, reproducible report
Write down a short sequence someone else could follow: the network you used, the app version, the selected location, the action you took and the message that appeared. Add whether another trusted network changed the result. Use an exact time with a timezone so the provider can correlate the event. If support asks for diagnostic data, use its official private route and review the file for secrets before sending it.
Before testing new JungleVPN software, read the current app and test-release information and retain any known-good installer or configuration according to the provider’s instructions. Reconnecting, restarting and updating should follow the supported workflow; destructive resets are a last resort, not a first step. Stop when you have a reliable working connection or a clearly reproducible failure. The goal is an understood, secure result, not a successful-looking screenshot produced by turning safeguards off.