Screen Installation
More options
Discuss with Marie Network Requirements
Technical documentation for school network administrators: static IP for TVs, allowed outbound connections, communication between player and TV, and what to do without DHCP.
This page is for school network administrators. Each screen has a player (a small computer, which we call a device in Studio) and a TV. The player downloads content from the internet and controls the TV over the local network: turning it on, off, and switching inputs.
Summary
- Both the player and the TV are on wired connections (Wi-Fi only by arrangement with us) and in the same subnet.
- Each TV has a static IP address, preferably as a DHCP reservation.
- The player only needs outbound connections: HTTPS (443), SSH to our server for remote management (22), and HTTP for system updates (80), plus DNS and NTP.
- No inbound connections from the internet, no port forwarding or public IP.
- Network without proxy and without a login page (captive portal).
IP Addresses and DHCP
The player obtains its address from DHCP and does not require a static IP.
The TV requires a static IP address, preferably as a DHCP reservation based on its MAC address. The player remembers the TV’s address. If the TV gets a different address after a power outage, the player will not be able to control it (turn on according to schedule, switch input) until it rediscovers it on the network. We know the TV’s MAC address at the latest on installation day, so it’s good for the network administrator to be available on that day to set the reservation immediately.
Connections from the player to the internet
All connections are initiated by the player outbound. If the school filters outbound traffic, allow these:
| Protocol and Port | Destination | Purpose |
|---|---|---|
| HTTPS, TCP 443 (including WebSocket) | oujoezwbmlandgzzxjei.supabase.co | Screen content, scenarios, widget data, images and videos, live updates, and player app updates. |
| HTTPS, TCP 443 | cli.suplovani.cz | First launch, internet check, and daily updates of the management tool. |
| HTTPS, TCP 443 | sshr.suplovani.cz | Downloading keys for remote management during installation. |
| SSH, TCP 22 | sshr.suplovani.cz | Remote management and support. The player opens an encrypted connection to our server for remote administration. |
| HTTP, TCP 80 | Ubuntu mirrors: archive.ubuntu.com, security.ubuntu.com (or national mirror, e.g. cz.archive.ubuntu.com) | Operating system security updates. |
| HTTPS, TCP 443 | api.open-meteo.com | Weather widget (only if the school uses it on screens). |
| HTTPS, TCP 443 | addresses specified in the Web widget | The Web widget displays an external page, which must be accessible from the player. |
| DNS, UDP/TCP 53 | DNS server from DHCP | Address resolution. |
| NTP, UDP 123 | ntp.ubuntu.com or NTP server from DHCP | Accurate time, required for encrypted connections and scheduled power on. Newer Ubuntu versions may verify time via NTS (TCP 4460). |
If port 22 on sshr.suplovani.cz is blocked, the screens will still work, but we cannot manage them remotely, and every repair will require an on-site visit. How remote management works is described in the article How Remote Management of Screens Works.
Communication between the player and the TV
The player controls the TV over the local network. Therefore, both must be in the same subnet (same VLAN), and the network between them must not block broadcast or multicast. Pay special attention to client isolation on Wi-Fi.
| Protocol and Port | Direction | Purpose |
|---|---|---|
| TCP 6466 and 6467 (TLS) | player → TV | TV control (Android TV Remote) and one-time pairing. |
| TCP 5555 | player → TV | Android debugging over network (ADB): TV status, input switching, screenshot. |
| UDP 5353 (mDNS, 224.0.0.251) | both directions | Discovering the TV on the network. |
| UDP 7 and 9, broadcast | player → network | Wake the TV (Wake-on-LAN). |
| ICMP (ping) | player → TV | Check if the TV responds. |
The TV does not need internet access for Suplování.cz. However, its own functions (system updates, manufacturer apps) may require it.
Contact Us
If your network cannot meet any of these requirements, please contact us before installation at podpora@suplovani.cz. Together we will find a solution, such as a separate network just for screens or connection via mobile network.
Updated