Checking…
-
Reaching the server
Does this network resolve the name and allow HTTPS to it?
-
It really is the server
A captive portal or filter can answer in its place. This asks for something only the real one can say.
-
The deck script
The one file your deck loads. Blocked here means no badge on the deck at all.
-
The live connection
A real WebSocket, the thing proxies break most often. Blocked here means the badge says “Remote offline”.
If something failed
Three ways round it
Put the laptop on your phone’s hotspot. Only two devices need the network, so the venue’s filter is out of the path entirely. Nothing to install, works mid-session.
The whole ask, for IT: allow live.zennia.sg outbound on TCP 443, HTTPS and WebSocket. No other ports, nothing inbound, no plug-in on the device.
The same software runs locally, and the phone reaches it over the room’s own network. Nothing leaves the room, so there is nothing to filter.
A blocked script costs you the phone, never the talk: the deck’s own keys, timer and present mode never touch the network.