zenniaDeck Remote
Connection check

Will the remote work on this network?

Four checks, a few seconds. Run it on the laptop and on the phone — they are often on different networks, and only one of them has to be blocked for the remote to fail.

Checking…

  1. Reaching the server

    Does this network resolve the name and allow HTTPS to it?

  2. 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.

  3. The deck script

    The one file your deck loads. Blocked here means no badge on the deck at all.

  4. 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

Fastest Tether to your phone

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.

Cleanest Ask for one hostname

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.

No internet at all Run it on the laptop

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.