Network requirements for IT
The addresses players' phones and the host's browser must reach over HTTPS on port 443, why WebSockets matter, and what not to inspect.
Quack runs in the browser, over HTTPS on port 443 only. Players' phones and the host's computer must reach the addresses below, with WebSockets allowed. There is nothing to install and no other port to open. If these are blocked, phones can't join; if the network is slow or crowded, answers arrive late.
Which addresses must be reachable?
Allow these on port 443 for every device in the room. The first six are needed by players' phones and the host alike. The last two are needed by the host's computer only, because it runs the editor and the big screen.
| Address | Used for | Needed by |
|---|---|---|
| getquack.app | The site, the apps and their sign-in pages | Everyone |
| europe-west1-getlyva-3b966.cloudfunctions.net | Joining, answering and every step of a session | Everyone |
| identitytoolkit.googleapis.com, securetoken.googleapis.com | Signing in (players get an anonymous sign-in) | Everyone |
| *.europe-west1.firebasedatabase.app | The live session, over WebSockets | Everyone |
| apis.google.com | Loaded by the sign-in library | Everyone |
| firebasestorage.googleapis.com | Images on slides | Everyone |
| firestore.googleapis.com | Decks and accounts | Host |
| www.youtube-nocookie.com, www.youtube.com | Video slides | Host |
Why do WebSockets matter?
Each phone and the big screen hold one open WebSocket (wss://) to the live session's database at *.europe-west1.firebasedatabase.app. Allow the whole wildcard: the database hands each connection to one of its servers under that domain. When WebSockets are blocked, the connection falls back to HTTPS long-polling, which works but adds delay.
- Allow WebSockets to *.europe-west1.firebasedatabase.app.
- Don't SSL-inspect these addresses. Inspection can break WebSockets and adds a delay to every answer.
- Plan for the room. A slow or crowded Wi-Fi delays every answer, and when a quiz scores speed, a late answer scores less.
- Test before the day. Join a session from a phone on the same network the room will use.
What else can a session load?
A session can also reach a few other addresses, but only when a deck or a host uses the feature behind them. None of them is needed to join a session or to answer. Allow them if your rooms use GIFs or video slides, or if hosts sign in with a social account.
- GIFs from the editor's GIF search load from static.klipy.com, cdn.klipy.com and cdn.klipy.co.
- Video slides stream from YouTube's own servers once the player starts.
- Host sign-in with Google, Microsoft, Apple or Facebook opens that provider's sign-in page.
- Analytics go to eu.i.posthog.com and eu-assets.i.posthog.com, only for visitors who accept it. Blocking them changes nothing.