Office and hotel QuickQ: disconnect client and Kill Switch → finish the portal or corporate dialer → Connect. Still failing: compatible protocol and a phone-hotspot A/B. If Connect is already up, the portal never loads.
Portals want a real HTTP hit. PAC plus a tunnel sends some tabs to 127.0.0.1.
Order
- QuickQ off, lock off.
- SMS / room / corporate client.
- Normal pages, then QuickQ.
- Fail → compatible/TCP + hotspot.
Smart routing vs intranet: mode. When to re-arm the lock: encryption. Install: first run. Download, FAQ, guides.
Field questions tied to this guide
- Portal never appears. Quit QuickQ and the lock. System browser, any http page. Then Connect.
- Mandatory PAC? Keep PAC in the work browser profile. QuickQ in a clean profile. Never both on one profile.
- IT bans VPNs? Follow policy. This site will not help you dodge MDM.
- Hotspot works, office SSID does not? UDP or firewall. Compatible/TCP, or stay on the hotspot.
Change one control, then retest
While working through “QuickQ on office and hotel networks: portals, PAC, UDP filters”, write the download-page version, mode, protocol, and node name on the first line of a note. After each toggle, run one check only: 1.1.1.1/help or the exact page that failed. Changing Kill Switch, split rules, and nodes together makes the next failure un-debuggable. Get QuickQ packages only from the download page; permissions and device limits live in the FAQ and guides.
On office or hotel networks, finish captive portals and clear leftover PAC entries before you decide this article’s failure mode applies. A cellular A/B exposes router DNS and parental filters quickly. Avoid hammering login on a second device during the test so session kickouts are not mistaken for radio drops.
Pin the combination that works—SSID, node, protocol—and reuse it on that network instead of starting from Auto every time. Keeping slug qqv-office-captive as your note title makes the write-up searchable later.
When to stop and change layers
After five identical failures, stop. Recheck the documented build, confirm a single tunnel client, ensure Kill Switch was not blocking a portal, and verify the browser is not Direct in a split list. Stopping is how you escape the wrong layer.
When you ask for help, include time, SSID, mode, protocol, node names, and steps already tried. After recovery, verify egress in a clean browser so cache does not fake success, then write the split list or favorites back into your notes before the next reinstall.
Extra pass for “QuickQ on office and hotel networks: portals, PAC, UDP filters”: retest three minutes on a second network and confirm the download page build. If only one app fails, inspect split membership; if everything fails, inspect permissions and DNS first. One change at a time remains the fastest habit when debugging QuickQ.
Extra pass for “QuickQ on office and hotel networks: portals, PAC, UDP filters”: retest three minutes on a second network and confirm the download page build. If only one app fails, inspect split membership; if everything fails, inspect permissions and DNS first. One change at a time remains the fastest habit when debugging QuickQ.
Extra pass for “QuickQ on office and hotel networks: portals, PAC, UDP filters”: retest three minutes on a second network and confirm the download page build. If only one app fails, inspect split membership; if everything fails, inspect permissions and DNS first. One change at a time remains the fastest habit when debugging QuickQ.
Extra pass for “QuickQ on office and hotel networks: portals, PAC, UDP filters”: retest three minutes on a second network and confirm the download page build. If only one app fails, inspect split membership; if everything fails, inspect permissions and DNS first. One change at a time remains the fastest habit when debugging QuickQ.
Extra pass for “QuickQ on office and hotel networks: portals, PAC, UDP filters”: retest three minutes on a second network and confirm the download page build. If only one app fails, inspect split membership; if everything fails, inspect permissions and DNS first. One change at a time remains the fastest habit when debugging QuickQ.
Extra pass for “QuickQ on office and hotel networks: portals, PAC, UDP filters”: retest three minutes on a second network and confirm the download page build. If only one app fails, inspect split membership; if everything fails, inspect permissions and DNS first. One change at a time remains the fastest habit when debugging QuickQ.