If your VPN connects over mobile data but not Wi-Fi, the difference is a useful clue: the client and account may be working, while the Wi-Fi network, router, or its sign-in requirements are getting in the way. Start with the network’s sign-in page, then test a fresh connection and check router restrictions, protocol compatibility, and DNS. Change one thing at a time so you can tell which step matters, and restore settings you changed if they do not help.

Identify where the connection fails

Before changing settings, note what the client actually reports. “Connecting” that never finishes suggests a different problem from a completed connection where websites still will not load. An error naming authentication, a timeout, or a DNS failure can also narrow the search. If the client provides logs or diagnostics, record the relevant message before restarting it; avoid posting subscription links, passwords, or other private configuration details publicly.

Compare Wi-Fi with mobile data using the same device, client, profile, and route if possible. If mobile data works but Wi-Fi does not, the comparison points toward the Wi-Fi environment, but it does not prove that the router alone is responsible. A public hotspot may require a sign-in, a workplace network may restrict tunnels, and a home router may apply filtering or parental controls. If neither network works, check the client, subscription, account status, and device permissions before focusing on the router.

5

checks in this guide

2

network types to compare

Use these checks as a sequence, not as a list of settings to change all at once. Disconnect the VPN before testing ordinary Wi-Fi access, and reconnect after each change. When the symptom changes, note the step and the exact network you are using. That small record makes it easier to undo a change and gives support staff useful details if the issue persists.

1. Open the Wi-Fi sign-in page

Hotels, airports, cafés, campuses, and some managed networks use a captive portal. The device may join Wi-Fi successfully but still need you to accept terms, enter a room code, or sign in through a browser before unrestricted internet access is available. A VPN started before that step may wait indefinitely or fail because the network has not yet authorized ordinary traffic.

  1. Disconnect the VPN and confirm that the device is connected to the intended Wi-Fi network.
  2. Open a browser and visit a familiar website, or open the network’s official sign-in page if the venue provides one.
  3. Complete the sign-in or acceptance step, then check that a normal page loads without the portal appearing again.
  4. Return to the VPN client and connect again. If the client was left trying to connect, stop that attempt first and start a fresh one.

Some devices do not display the sign-in screen automatically. Opening a browser can prompt it, but do not enter sensitive credentials into a page that looks unfamiliar or has an unexpected address. Ask the network operator for the official access instructions if the page does not appear. On a managed device, a portal may require an administrator’s approval rather than a personal setting change.

2. Reset the client and check the network

A stale connection attempt can remain after switching networks, waking a device from sleep, or moving between access points. A simple reconnect is a low-risk way to clear that state. Turn the VPN off, close and reopen the client, and reconnect to Wi-Fi if needed. Then select the intended profile and try again. If the device has a system VPN permission prompt, approve it only when it was triggered by the client you chose to use.

Check that the Wi-Fi itself is stable by loading more than one ordinary webpage with the VPN disconnected. If pages also fail without the VPN, troubleshoot the local connection first: reconnect to the network, check whether other devices can browse, and restart the router only if you control it and a restart is appropriate. On a home network, a brief router restart may clear a temporary fault, but it will interrupt other users’ connections. On public or workplace Wi-Fi, do not restart or alter equipment you do not manage.

If only one device has trouble, compare its behavior with another device on the same Wi-Fi, without changing multiple variables. A successful connection on another device suggests checking the original device’s client version, permission state, system date and time, and conflicting network utilities. If every device fails on one Wi-Fi network but works elsewhere, the network or router configuration becomes a stronger lead. These comparisons are diagnostic clues, not proof of a particular cause.

  • ✅ Test ordinary browsing with the VPN disconnected.
  • ✅ Restart the VPN client and make a new connection attempt.
  • ✅ Compare one device on Wi-Fi and mobile data without changing its profile.
  • ❌ Do not run two VPN or proxy clients at the same time; their routes can conflict.
  • ❌ Do not reset a router you do not own or administer.

On Windows, macOS, Android, iOS, and Linux, the menu names differ, but the diagnostic order is similar: confirm Wi-Fi access, close competing network tools, reconnect the client, and check the client’s permission or diagnostic message. If the operating system shows a VPN indicator while applications still cannot reach websites, the tunnel may be active while routing or name resolution remains faulty. Treat those symptoms separately rather than repeatedly toggling the same switch.

3. Check router and network restrictions

Some routers and managed networks restrict traffic needed by particular VPN protocols. A firewall, access-control rule, parental-control feature, security filter, or organization policy may block or interfere with a connection. The behavior depends on the network and protocol; there is no single router switch that must be enabled for every VPN. If you manage the router, review its current rules and documentation rather than changing unrelated security settings at random.

On a home network, temporarily compare the VPN on another Wi-Fi network that you are allowed to use. If the client connects there, check whether the home router has recently received a configuration change or whether a filtering feature is enabled. Change only a setting you understand, record its original value, and test again. Avoid disabling the router firewall wholesale: that can expose devices without showing whether the VPN was the actual cause.

On office, school, hotel, and public Wi-Fi, network owners may intentionally limit VPN traffic. Do not try to evade access controls or install unapproved network tools on a managed device. Ask the network administrator whether VPN connections are permitted and whether a supported method is available. If a network requires a specific sign-in procedure or blocks a protocol by policy, switching DNS will not override that rule.

Router settings involving VPN passthrough, UDP, IPv6, or packet size can be relevant, but their names and effects vary across models. “VPN passthrough” is not a universal requirement, and enabling it does not guarantee that a client can connect. If a router’s documentation indicates that a relevant feature is disabled, make a careful, reversible test. For persistent failures, share the router model, client platform, protocol selection, and non-sensitive error text with the network administrator or service support.

If you are evaluating a service as well as troubleshooting a connection, its platform coverage and setup guidance matter alongside the connection itself. The Q9VPN homepage is a useful place to review the service overview, while the actual Wi-Fi restrictions still need to be diagnosed on the network you are using.

Key takeaway: If the VPN works on another network but not on one managed Wi-Fi network, ask its administrator about permitted VPN use before changing security controls.

4. Try a compatible protocol

A client can offer more than one protocol, but availability depends on the service, configuration, and client implementation. A protocol that works on mobile data may be filtered or unreliable on a particular Wi-Fi network. If your client offers another supported option, select it, save the change, and make a fresh connection attempt. Change only the protocol for this test; keep the route and other settings the same so the result is meaningful.

Do not assume that names in a general guide map directly to every app. Shadowsocks, VMess, Trojan, Hysteria2, and WireGuard are not interchangeable labels for one setting, and a client must implement the protocol and configuration format it receives. If you use a subscription, refresh it through the service’s official instructions before concluding that a protocol is missing. Do not paste a subscription link into an unrelated client or share it with someone offering to “check” it.

After changing a protocol, allow the client to finish one connection attempt and read its status or diagnostic message. If it connects, check that the sites and apps you intend to use work as expected. If the new protocol gives the same error, return to the original setting before testing another cause. If the client reports that the protocol or profile is unsupported, the next step is to verify compatibility with the service and client documentation—not to keep cycling through unrelated options.

Network policies may prohibit certain protocols. On a work or school connection, follow the organization’s rules and ask for an approved alternative rather than trying to disguise traffic. On a network you control, the router’s logs or documentation may help identify a restriction, but avoid exposing credentials or full connection URLs when asking for help.

5. Check DNS and decide what to try next

DNS translates a website name into an address. It is most relevant when the VPN appears connected but websites fail to open by name, while a client diagnostic or another permitted test suggests the tunnel itself is established. DNS is less likely to explain a connection that never gets past its initial handshake. First disconnect and reconnect once; then check whether the client has a DNS setting or diagnostic that identifies a resolver problem.

Review DNS changes carefully. A client may provide its own DNS behavior while connected, and manually setting a device or router resolver can affect other users or bypass an organization’s intended policy. If you changed DNS for testing, write down the original setting and restore it if the test makes no difference. Do not disable DNS protections or install an unfamiliar “DNS fixer” just because a connection fails.

IPv6 or packet-size issues can also produce partial connectivity in some environments, but they are not the first settings to change. Look for a specific clue, such as a connection that establishes but certain destinations consistently fail, or diagnostics that point to packet fragmentation. If you control the network, consult the router and client documentation and make one reversible test at a time. Otherwise, provide the evidence to the network administrator or support team instead of altering system-wide settings.

When the connection still will not start, collect concise, non-sensitive details: the device operating system, client name and version, whether ordinary Wi-Fi browsing works, whether mobile data works with the same profile, the selected protocol, and the exact error text. Include whether the problem affects one Wi-Fi network or several. Do not send passwords, authentication tokens, private keys, or a complete subscription URL. If the service offers official setup instructions, verify that the profile is current and compatible with the client before reinstalling anything.

  • ✅ Portal not completed: sign in to Wi-Fi, then reconnect the VPN.
  • ✅ Wi-Fi browsing fails without the VPN: fix the local network connection first.
  • ✅ One Wi-Fi network blocks a connection: ask its owner whether VPN use is permitted.
  • ✅ Tunnel connects but names fail: inspect client DNS diagnostics before changing resolver settings.
  • ❌ Same failure everywhere: do not assume the router is at fault; check the client, profile, and account too.

Keep the troubleshooting controlled: change one setting, test, record the result, and undo changes that do not help. This avoids turning a Wi-Fi connection problem into a separate DNS, firewall, or routing problem. If the issue remains, a specific error message and a careful Wi-Fi-versus-mobile-data comparison are more useful than a long list of settings that were all changed at once.

Bottom line: Complete Wi-Fi sign-in first, confirm that ordinary browsing works, and then test the client, network restrictions, protocol compatibility, and DNS in that order.