Skip to content

Host school network requirements

Snapdown is a web app for wrestling tournaments: brackets, table scoring, event administration, and live results. Every scoring table needs internet access for the whole event. Scoring devices are usually Chromebooks or Windows laptops owned by the tournament or its volunteers, not by the host school.

This page has two parts:

  • Part 1 is what Snapdown needs. It’s the same for every event.
  • Part 2 is a worksheet for the details that change per event. The tournament organizer and the host school’s IT staff fill it in together.

Download the Word document

Organizers: fill in the worksheet, cut anything that doesn’t apply, and send it to the host school’s IT contact at least a week before the event.

The easiest setup is a guest or event network with a password (WPA2 or WPA3 Personal). Enterprise Wi-Fi (802.1X) also works if devices the school doesn’t manage can join it; see Enterprise Wi-Fi below.

  • Wi-Fi reaches every scoring table and the head table, with the gym full of people.
  • Personal Chromebooks and Windows laptops can join without a school account or device enrollment.
  • The network handles the number of devices on the worksheet in Part 2.
  • Access stays on from setup through the last bout. Guest passes that expire after a few hours will drop scoring tables mid-event.
  • Any captive portal, sign-in page, or device registration is explained in advance.

Snapdown devices don’t talk to each other on the local network; every device talks to Snapdown’s servers. Client isolation on a guest network is fine.

If spectators share the same Wi-Fi, a full gym can crowd out the scoring tables. A separate network for scoring devices, when the school can offer one, avoids that.

These addresses run the app. If any are blocked, Snapdown won’t work.

Address What it does
*.snapdown.io The app (app.); data, sign-in, live updates, photos and logos, and matchup generation (api.); bout video (video.)
snapdown.com Help Center and the Ask Snapdown assistant

Keep the asterisk in *.snapdown.io. Many filters treat a plain domain as that exact name only.

Some DNS filters, including GoGuardian DNS, also check where a name points. api.snapdown.io points at a supabase.co address, so if it’s still blocked after *.snapdown.io is allowed, add *.supabase.co too.

These are needed only for the features listed:

Address Needed for
accounts.google.com Sign in with Google
appleid.apple.com, appleid.cdn-apple.com Sign in with Apple
*.stripe.com, *.stripe.network Card payments, if registration or checkout happens on this network
tile.openstreetmap.org Maps on registration and hometown pages

Everything uses HTTPS on TCP port 443, including the secure WebSocket (WSS) that carries live scores and mat queues. Devices also need normal DNS.

Snapdown doesn’t need any inbound firewall rules or port forwarding.

SSL inspection: filters that decrypt HTTPS traffic can break the WebSocket even when the address is allowed. The usual sign is that pages load but scores only change on refresh. Exempt api.snapdown.io from SSL inspection.

For GoGuardian and other DNS-based filters, the Snapdown phone and tablet apps, and email senders, see the full network allowlist.

If the only available network uses enterprise authentication, IT needs to provide the connection settings in Part 2. Chromebooks are the usual sticking point: ChromeOS asks for the RADIUS server’s CA certificate and a server domain suffix, and a laptop that connects fine on Windows can still fail on a Chromebook if those are missing.

If the enterprise network only accepts school-issued devices or certificates, ask for a guest network instead.

  • Bout video uploads from the scoring computer during each bout, so it needs much more upload capacity than scoring alone. Test every planned camera together on the venue network. See Record bouts and offer live video.
  • Score clocks connect to the scoring computer with an Ethernet cable, not through the school network. See Connect a Trackwrestling score clock.

From a scoring device on the venue network, the organizer checks:

  • app.snapdown.io loads and tournament staff can sign in.
  • A test bout scored at one table shows up live on another device without refreshing.
  • The connection holds at every mat and at the head table.
  • Bout video uploads from every planned camera at once, if the event uses video.
  • The school’s IT contact is reachable on setup day.

Filled in by the tournament organizer and the host school.

Tournament / organization
Event date(s)
Setup date and time
Venue / school
Number of mats
Expected devices (tables, head table, displays)
Bout video in use? Yes / No
Tournament contact (name, phone)
Name
Email
Phone (setup day)
Network access confirmed Yes / Pending
Network name (SSID)
Password or sign-in method
Captive portal or device registration steps
Access expires at
Separate network for scoring devices? Yes / No
Allowlist in place (Part 1 addresses) Yes / Pending
SSL inspection exemption for api.snapdown.io Yes / Not needed / Pending
Setting Value
Network name (SSID)
EAP method
Phase 2 authentication
CA certificate
Server certificate domain suffix
Identity / username and password
Other instructions

Also covers: host school · school IT · network requirements · IT checklist · venue wifi · guest wifi · 802.1x · enterprise wifi · chromebook wifi