Connected to WiFi but no internet

A guest says "it connected, but nothing opens", and the reflex is to blame the card and reprint. It is not the card: the code only fills in the SSID and password, and once the phone reports connected its job is over. Here are seven real causes, in the order worth checking.

1. Separate the three different "cannot connect" cases

SymptomResponsible layerQR related?
Nothing happens, or "incorrect password"Code quality, size, payload accuracyYes
Shows connected, pages never loadIP allocation, authentication, DNS, routing policyAlmost never
Some apps work, others do notDNS, proxy, OS network settingsNo

Making that distinction prevents a lot of wasted work. All seven causes below fall in the second and third rows.

2. Seven causes and how to identify them

CauseTypical symptomHow to confirm
DHCP pool exhaustedEarly joiners fine, later ones "connected, no internet"Check allocated leases against the pool size; shorten the lease from 24h to 2h
Captive portal pendingBrowser jumps to a login or consent page, or spins foreverOpen a plain http page (not an https home page) and see whether it redirects
DNS unavailableChat apps work, browser shows "server not found"Test with a public resolver, or open a raw IP address directly
Guest SSID blocked from WANConnects and dies; not even the portal loadsIn the admin page, check the guest network is not restricted to LAN or behind a MAC allow-list
Client or bandwidth capEveryone slows down at peak, some devices dropCheck the connected-device count and rate limits; consumer routers often cap at 10–16
Double NAT / second routerGets an IP but cannot route; games or calls misbehaveLook for a second router behind the modem, both running DHCP
Time schedule / parental controlNothing works during specific hoursCheck whether the guest SSID has an allowed-hours window or a paused-device rule

3. Three checks on site, thirty seconds to assign blame

  1. Scan the same card with a second device. Both fail to reach the internet → network side, leave the cards alone; only one fails → that phone.
  2. Have the guest forget the network and rejoin. Stale profiles fail silently with new passwords and can leave the IP allocation stuck.
  3. Open a plain http address. A login page means captive portal; endless spinning means egress or DNS.

If all three point at the network, check the connected-device count and the DHCP pool. Between them they explain most "connected but no internet" tickets at a venue.

Owner-side checklist

  • Guest SSID really allowed out to the internet, no stray MAC allow-list.
  • DHCP pool sized at roughly twice your seat count, lease not too long.
  • Connected devices near the cap; above ~15, move to a business AP.
  • Rate limit not set absurdly low (below 2 Mbps almost nothing loads).
  • No second router creating double NAT; modem in bridge or single-router mode.
  • No allowed-hours schedule silently cutting the guest network after closing.

4. When a reprint is actually justified

Only these: the phone cannot scan at all (too small, inverted, glare, cropped quiet zone), it reports a wrong password (the payload disagrees with the router), or only one class of phone can scan (payload or platform compatibility). Everything else is not a print problem.

To check whether the card itself is healthy, run the payload through the validator — string, byte count and escaping in one pass. Unsure about the printed size? Reverse it from distance with the size calculator.

If the card checks out, do not reprint

Verify the payload, size the code from distance, and stop treating a network fault as a printing fault.

Open the WiFi QR code studio

Related reading

Frequently asked questions

The phone says connected but pages do not load — is the QR code wrong?
Almost never. The code's only job is filling in the SSID and password; once the phone reports connected, the code is done. No loading pages is an IP, authentication, DNS or router-policy problem, and reprinting will not change it.
Only some guests have no internet after joining — why?
Usually a DHCP pool or client limit: the first few take the addresses and later devices join without an IP. Shorten the lease, enlarge the pool, or move to a business AP sized to your seat count.
Fastest way to spot a captive portal?
Open a plain http address in the browser rather than an https home page. If it redirects to a login or consent screen, that is a captive portal — joining the WiFi is not the same as getting online.
New router, guests cannot get online. What first?
Check whether the guest SSID is actually allowed out to the internet and whether a MAC allow-list got enabled, then look for a second router creating double NAT. The SSID and password in the code usually stay valid unless the new box ships a different name.

Templates that fit this setup

Three layouts picked for this scenario — swap the venue name and password, then export.