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
| Symptom | Responsible layer | QR related? |
|---|---|---|
| Nothing happens, or "incorrect password" | Code quality, size, payload accuracy | Yes |
| Shows connected, pages never load | IP allocation, authentication, DNS, routing policy | Almost never |
| Some apps work, others do not | DNS, proxy, OS network settings | No |
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
| Cause | Typical symptom | How to confirm |
|---|---|---|
| DHCP pool exhausted | Early joiners fine, later ones "connected, no internet" | Check allocated leases against the pool size; shorten the lease from 24h to 2h |
| Captive portal pending | Browser jumps to a login or consent page, or spins forever | Open a plain http page (not an https home page) and see whether it redirects |
| DNS unavailable | Chat apps work, browser shows "server not found" | Test with a public resolver, or open a raw IP address directly |
| Guest SSID blocked from WAN | Connects and dies; not even the portal loads | In the admin page, check the guest network is not restricted to LAN or behind a MAC allow-list |
| Client or bandwidth cap | Everyone slows down at peak, some devices drop | Check the connected-device count and rate limits; consumer routers often cap at 10–16 |
| Double NAT / second router | Gets an IP but cannot route; games or calls misbehave | Look for a second router behind the modem, both running DHCP |
| Time schedule / parental control | Nothing works during specific hours | Check whether the guest SSID has an allowed-hours window or a paused-device rule |
3. Three checks on site, thirty seconds to assign blame
- 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.
- Have the guest forget the network and rejoin. Stale profiles fail silently with new passwords and can leave the IP allocation stuck.
- 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 studioRelated reading
Frequently asked questions
The phone says connected but pages do not load — is the QR code wrong?
Only some guests have no internet after joining — why?
Fastest way to spot a captive portal?
New router, guests cannot get online. What first?
Templates that fit this setup
Three layouts picked for this scenario — swap the venue name and password, then export.