WhatsApp PC Login Fails on Wi‑Fi? 9 Fixes (2026)

Quick answer: If WhatsApp won’t log in on your PC only on Wi‑Fi, that Wi‑Fi is blocking or misrouting the WhatsApp Web/Desktop connection (most often DNS filtering, proxy/PAC, QUIC/HTTP3, or WebSocket rules).

Confirm it with a hotspot test, then fix DNS/proxy/QUIC and router filters so WhatsApp can complete pairing and keep the session connected.

Quick Fix Checklist

• Confirm it’s the Wi‑Fi: connect the PC to a phone hotspot and open https://web.whatsapp.com/. If it works on hotspot, your Wi‑Fi/router is the cause.
• Hard refresh + clean session: open an Incognito/Private window and try again (or clear site data for web.whatsapp.com).
• Disable VPN/Proxy/PAC: Windows Settings → Network & Internet → Proxy → turn off Proxy and any Setup script.
• Switch DNS (fast win): set DNS to 1.1.1.1 / 1.0.0.1 (or 8.8.8.8 / 8.8.4.4), then run ipconfig /flushdns.
• Turn off Secure DNS (DoH): Chrome/Edge → Settings → Privacy & security → Security → disable “Use secure DNS”.
• Complete captive portal: open http://neverssl.com to trigger Wi‑Fi sign-in/terms.
• Try another browser: if Chrome fails, test Firefox (different HTTP3/QUIC behavior).
• Disable IPv6 temporarily: if only WhatsApp fails but other sites work, IPv6 misrouting is common.
• Desktop app reset: Repair/Reset WhatsApp Desktop (Windows) or reinstall if it’s stuck in a login loop.

Causes (realistic, not generic)

• DNS filtering/interception: “Safe DNS”, ISP DNS, Pi-hole/AdGuard/NextDNS profiles, or router DNS rewriting can break WhatsApp endpoints.
• WebSocket blocking: some corporate/hotel networks block WebSocket upgrades used by WhatsApp Web/Desktop, causing “Computer not connected” or endless loading.
• QUIC/HTTP3 incompatibility: certain routers/security appliances mishandle QUIC, leading to QR pages that load but pairing fails or stalls.
• Captive portal not completed: Wi‑Fi shows connected, but traffic is blocked until you accept terms/sign in.
• Proxy/PAC enforcement: a proxy auto-config (PAC) script routes traffic through a proxy that blocks WhatsApp or WebSockets.
• Broken IPv6 path: partial connectivity where many sites work, but WhatsApp fails due to bad IPv6 routing or DNS AAAA responses.
• Local cache/state corruption: browser service worker/cache or WhatsApp Desktop local state can keep retrying a bad network path on that Wi‑Fi.
• Time/certificate issues: incorrect system time or TLS inspection can cause secure connection failures that look like a login problem.

Cause	Fix (what actually works)
DNS filtering / wrong DNS answers	Set DNS to 1.1.1.1/1.0.0.1 (or 8.8.8.8/8.8.4.4) + ipconfig /flushdns + allowlist WhatsApp domains in Pi-hole/AdGuard
Proxy/PAC blocks WebSockets	Disable Windows Proxy + remove PAC “Setup script” (or ask admin to allow WhatsApp Web/WebSockets)
QUIC/HTTP3 breaks on this Wi‑Fi	Disable QUIC/HTTP3 (Chrome flags) or use Firefox; restart browser
Captive portal not completed	Open http://neverssl.com, sign in/accept terms, then retry WhatsApp
Router web filter / parental controls	Temporarily disable filtering; then allowlist WhatsApp domains and turn filtering back on
IPv6 misrouting	Disable IPv6 on the Wi‑Fi adapter temporarily; update router firmware / fix IPv6 settings

Step-by-Step Fix

1) Prove it’s a Wi‑Fi-only issue (30 seconds)

• Connect the PC to a phone hotspot.
• Open https://web.whatsapp.com/ (or WhatsApp Desktop) and try pairing.
• If it works on hotspot but fails on Wi‑Fi, continue—this confirms the WhatsApp login problem in PC not working on Wi‑Fi is network-related.

2) Fix DNS misrouting (most common)

Windows 11/10:

• Settings → Network & Internet → Wi‑Fi → your network → Hardware properties → Edit DNS server assignment.
• Set to Manual → enable IPv4 → Preferred DNS: 1.1.1.1 → Alternate DNS: 1.0.0.1.
• Open Command Prompt (Admin) and run:

ipconfig /flushdns

• Reload web.whatsapp.com and try pairing again.

If you use Pi-hole/AdGuard/NextDNS: check the block/query log while loading WhatsApp Web and allowlist anything WhatsApp-related that is blocked.

3) Turn off Secure DNS (DoH) and “security DNS” features

Secure DNS can conflict with networks that intercept DNS or require their resolver, causing WhatsApp Web to partially load or fail pairing.

• Chrome/Edge: Settings → Privacy and security → Security → disable Use secure DNS.
• Firefox: Settings → Network Settings → disable DNS over HTTPS.

Retry WhatsApp Web after changing this (close all browser windows if needed).

4) Clear WhatsApp Web site data (non-obvious cache fix)

If the QR loads but pairing loops or the page stays stuck on “Loading…”, clear the site’s cache/service worker so it rebuilds cleanly on your Wi‑Fi.

• Chrome/Edge: Settings → Privacy and security → Third-party cookies → See all site data and permissions → search whatsapp → remove data for web.whatsapp.com.
• Or open DevTools (F12) → Application → Storage → Clear site data.
• Reopen https://web.whatsapp.com/ and pair again.

5) Force WhatsApp Web to avoid QUIC/HTTP3 (high-impact on “bad routers”)

Some routers and security appliances break QUIC/HTTP3, which can cause login stalls even when normal browsing works.

• Chrome: open chrome://flags
• Search QUIC → set Experimental QUIC protocol to Disabled.
• Relaunch Chrome and retry WhatsApp Web.

If your PC is managed and flags are locked, test Firefox or Edge as a workaround.

6) Remove proxy/PAC enforcement (common on office/school Wi‑Fi)

• Windows Settings → Network & Internet → Proxy.
• Turn off Use a proxy server.
• Disable Setup script (PAC) if present.
• For testing, also turn off Automatically detect settings.

If WhatsApp starts working after disabling proxy/PAC, your network policy is likely blocking WhatsApp/WebSockets through the proxy. You’ll need the network admin to allow it.

7) Fix captive portal / “connected but blocked” Wi‑Fi

• Disconnect and reconnect to the Wi‑Fi.
• Open http://neverssl.com (HTTP, not HTTPS).
• Complete the sign-in/terms page, then reopen WhatsApp Web/Desktop.

8) Temporarily disable IPv6 (selective failure fix)

If WhatsApp fails only on this Wi‑Fi and DNS changes didn’t help, IPv6 can be the culprit.

• Control Panel → Network and Internet → Network Connections.
• Right-click your Wi‑Fi adapter → Properties.
• Uncheck Internet Protocol Version 6 (TCP/IPv6) → OK.
• Retry WhatsApp login.

If this fixes it, update router firmware and review IPv6 settings (or keep IPv6 off until the router is fixed).

9) WhatsApp Desktop: reset network state and permissions

• Fully exit WhatsApp Desktop (system tray → Exit).
• Windows: Settings → Apps → Installed apps → WhatsApp → Advanced options → Terminate → Repair → Reset.
• Reopen WhatsApp Desktop and pair again.

If it still fails, uninstall WhatsApp Desktop, reboot, then reinstall the latest version from Microsoft Store (or the official installer) to replace corrupted components.

10) Router-side filtering: allow WhatsApp traffic (home Wi‑Fi fix)

If hotspot works but home Wi‑Fi doesn’t, test by temporarily disabling these router features (then re-enable with an allowlist):

• Parental controls / Web filtering / Safe browsing
• DNS filtering (router “safe DNS”, NextDNS profiles, Pi-hole/AdGuard)
• Intrusion prevention / DoS protection (overly aggressive settings can break WebSockets)

Allow/whitelist these domains (exact names can vary):

• web.whatsapp.com
• whatsapp.com
• static.whatsapp.net
• *.whatsapp.net
• *.fbcdn.net (sometimes used for static assets)

After allowlisting, flush DNS again on the PC: ipconfig /flushdns.

Still Not Working

• Identify the exact failure point:
  • QR won’t load / blank page: DNS/filtering/captive portal is most likely.
  • QR loads but pairing fails: QUIC/HTTP3, proxy/PAC, or WebSocket blocking is most likely.
  • Pairs then disconnects (“Computer not connected”): Wi‑Fi stability, firewall/web filter, or proxy timeouts are common.
• Check system time and TLS inspection: ensure Windows Date/Time is set to automatic. If you’re on a corporate network with SSL inspection, WhatsApp Web may be blocked by policy.
• Run a quick network reset (Windows): Settings → Network & Internet → Advanced network settings → Network reset. Reboot and test again (this clears stuck adapters and Winsock-related issues).
• Test on the same Wi‑Fi with another device: if another laptop also fails, focus on router/DNS/filtering. If only one PC fails, focus on proxy, Secure DNS, cache/site data, IPv6, or Desktop app reset.
• Use DevTools to confirm blocking (advanced): Chrome → F12 → Network → reload WhatsApp Web. Look for repeated failures like ERR_NAME_NOT_RESOLVED (DNS), ERR_CONNECTION_RESET (filter/proxy), or many requests stuck Pending (proxy/WebSocket/QUIC issues).
• Escalate with useful details: if this is office/school/hotel Wi‑Fi, ask the admin to allow WhatsApp Web and WebSockets. Provide the time of failure and that it works on hotspot but not on Wi‑Fi.
• Last-resort confirmation test: try a trusted VPN briefly. If VPN fixes it, the Wi‑Fi is filtering WhatsApp traffic and the real fix is router/admin allowlisting (don’t rely on VPN if it violates policy).

If you share your Windows version, whether you’re using WhatsApp Web or Desktop, the Wi‑Fi type (home/office/hotel), and the exact error text, you can pinpoint whether it’s DNS, proxy/PAC, QUIC/HTTP3, WebSocket filtering, or IPv6 in a few minutes.

If the App Fails but the Browser Works

If the browser version works but the app fails, the account itself is usually not the problem.

Why this happens

This pattern normally points to corrupted app cache, stale local session data, or a device-specific networking issue.

How to fix it

1. Use the working browser session as a control test while troubleshooting the app.
2. Force close the app and reopen it before trying the same action again.
3. Disable VPN, proxy, DNS filtering, or security apps temporarily.
4. Update or reinstall the app if the same failure only appears inside the app.

Important notes

• This is one of the fastest ways to narrow the issue to the app layer instead of the account layer.
• If the app still fails after reinstalling, the device configuration may be the next thing to inspect.

Frequently Asked Questions