Why hotel Wi‑Fi breaks trips

If you’re arriving tired and your mobile data is shaky, hotel Wi‑Fi sounds like the obvious backup. In China, the “Wi‑Fi” step often includes one extra requirement:

  • a captive portal (browser login page)
  • an SMS verification code
  • sometimes a preference for a mainland +86 number

This guide is about getting online reliably, not perfectly.

The fast goal: one working internet path in 10 minutes

Aim for any one of these outcomes:

  1. mobile data works (eSIM/SIM/roaming), or
  2. hotel Wi‑Fi works without SMS, or
  3. front desk provides an alternate login (voucher / room-based / staff assist)

If you can get one path working, you can complete the rest of your setup (payments, ride apps, tickets) calmly.

Common failure modes (and what to do)

Failure 1: the Wi‑Fi connects but “no internet”

Usually: the captive portal didn’t open.

Try in this order:

  • disable VPN mode (if enabled) until you’re online
  • open a plain HTTP URL in your browser (some devices won’t trigger a portal on HTTPS)
  • toggle Wi‑Fi off/on and reconnect
  • “forget network” and reconnect (forces a new portal session)

If it still won’t show: ask the front desk to confirm whether that network requires a portal and what the expected login method is.

Failure 2: the portal loads, but asks for an SMS code you can’t receive

Treat this as a product constraint, not a puzzle to “bypass”.

Safe options:

  • ask for a room-based login (some hotels can bind Wi‑Fi access to room + surname or room + passport)
  • ask for a temporary access code or “voucher” login (some properties generate one)
  • switch to mobile data and do the minimal setup needed to get SMS working (see below)

Failure 3: the portal requires a +86 number

Some hotels can only issue access to a mainland number through their system.

Your practical options:

  • use mobile data (eSIM/roaming) as your primary for the first night
  • if you truly need a local number, choose a travel product that includes a +86 number (plan this before arrival)
  • ask the front desk for an alternative network that doesn’t require a local number (sometimes staff Wi‑Fi exists for special cases)

Failure 4: the portal works, but keeps timing out

Often caused by switching networks or letting the phone sleep during login.

Fixes:

  • stay on the portal page until it confirms success
  • keep the screen awake for 30–60 seconds after “connect”
  • try another device (if you’re traveling as a pair, test both phones)

If the bottleneck is SMS, fix SMS first

If you can’t receive verification codes, many other travel tasks will fail (payments, Didi, 12306, some hotel portals).

Use this related playbook:

Once SMS is reliable, you can retry the portal on your terms.

First-night “minimum viable setup” checklist

Do these in order:

  1. confirm you can open a map and find your hotel pin
  2. confirm you can translate a screenshot (menu, address, login instructions)
  3. confirm you can message/call your travel partner (or hotel) if separated

Then upgrade your setup:

When to escalate to the front desk (and what to ask)

You’re not asking them to “fix your phone” — you’re asking for the hotel’s intended login path.

Ask:

  • “Is there a Wi‑Fi option that does not require SMS?”
  • “Can you issue a temporary login code?”
  • “Can the Wi‑Fi login be bound to my room number?”

If you get online via any method, take one screenshot of the successful login steps so you can repeat it tomorrow.

Connectivity rules and portal systems change. Use this as a practical checklist and confirm details with your hotel and your carrier.

Last verified: 2026-06-12