Connect a signage player to Wi-Fi, Ethernet or a proxy
Quick answer: DigitalSignage.com SignPlayer needs only an outbound internet connection: allow TCP 443 to *.signage.me, plus DNS on port 53 and NTP on port 123, and open no inbound ports; there is no static IP or port forwarding, because the player connects out to SignStudio over a real-time socket and falls back to HTTP polling behind a strict firewall. Use wired Ethernet for a permanent screen and Wi-Fi where cabling is impossible, with a signal of -65 dBm or better and Wi-Fi power saving off. HTTP, HTTPS and authenticated proxies are supported, SOCKS5 on Windows only. Captive portals on guest Wi-Fi are the most common reason a player never comes online.
Last updated October 22, 2026. Sources: network requirements, network bandwidth, troubleshooting and screens and installation pages on this site.
What the player needs from the network
| Requirement | Detail |
|---|---|
| Outbound HTTPS | TCP 443 to *.signage.me, which covers SignStudio, player registration and content, for example galaxy.signage.me |
| Outbound HTTP | TCP 80, recommended for redirects and some time services |
| DNS | UDP and TCP 53 |
| NTP | UDP 123, so the player's clock is right and schedules fire on time |
| Inbound ports | None |
| Static IP or port forwarding | Not needed |
| Bandwidth | 0.5 to 2 Mbps average per screen, bursts of 1 to 5 Mbps during content updates, 10 to 50 kbps the rest of the time |
If the firewall needs exact hostnames rather than a wildcard, ask support for the current list for your account. A blocked NTP port is a hidden cause of content playing at the wrong time: the clock drifts and dayparts change at the wrong hour.
Wi-Fi or Ethernet
Wired Ethernet wherever you can. It gives consistent bandwidth, avoids interference and removes most of the screens that go blank overnight. Wi-Fi is fine for a pilot, a hard-to-wire wall or a non-critical screen.
| Ethernet | Wi-Fi | |
|---|---|---|
| Reliability for 24/7 screens | Best | Depends on signal and power saving |
| Signal requirement | None | -70 dBm minimum, -65 dBm or better recommended, 5 GHz preferred |
| Typical faults | A loose cable | Power saving drops, roaming between access points, DHCP changes, captive portals |
| Metal enclosures and behind-panel mounting | No effect | Needs an external antenna or a different position |
| Cost | A cable run | Nothing, if coverage exists |
Whichever you use, give each player a DHCP reservation so its address does not change, and put signage on its own VLAN with outbound access to the signage service and nothing else.
Connect a player to Wi-Fi
- On the device, join the network the way the operating system does it: Wi-Fi settings on Android, Windows, Mac and Chrome OS; on a Raspberry Pi, set the Wi-Fi in Raspberry Pi Imager before writing the card, or in the desktop network menu afterwards.
- Test the signal at the screen's actual position, not at the desk, and move the access point or the player if it reads worse than -65 dBm.
- Turn off Wi-Fi power saving on the player. The troubleshooting FAQ names it as the usual cause of overnight drops: on a Raspberry Pi it is a NetworkManager setting, on Windows it is the power management option of the network adapter.
- Use a dedicated SSID or MAC-based access for signage rather than the guest network.
- Open SignPlayer, type the registration code shown on the player into SignStudio under Register SignPlayer, and confirm the screen shows online on the Screens dashboard.
Connect a player to Ethernet
- Plug the cable in before the player boots, so it gets an address at startup.
- Check the link light, then confirm the player has an IP address and that the Screens dashboard shows it online.
- For a long run to a remote screen, keep copper under about 100 meters, or use a switch near the screens; beyond that use fiber or a local switch rather than a long patch cable.
- Reserve the player's address in DHCP and note it against the screen name in SignStudio.
Proxies
| Proxy type | SignPlayer support |
|---|---|
| HTTP proxy | Full |
| HTTPS proxy | Full |
| Authenticated proxy (username and password) | Supported |
| Transparent proxy | Works automatically |
| SOCKS5 | Limited: Windows only |
The network requirements page documents the Windows player's proxy settings under Settings, Network, Proxy Configuration, with a proxy host, port and optional username and password, and the Linux and Raspberry Pi route of setting HTTP_PROXY and HTTPS_PROXY in the environment. On Android and Chrome OS, set the proxy in the device's Wi-Fi or network settings, which the player then uses. A proxy that inspects TLS will break the player's HTTPS connection unless the signage.me domains are exempted from inspection; allowlisting is the fix, not a certificate on the player.
Captive portals and guest networks
A captive portal, the sign-in page on guest Wi-Fi, is the most common reason a freshly installed player sits offline. An unattended player cannot click Accept, and portals expire the session after hours or days, so the screen drops off again later. Put signage on a wired VLAN, a dedicated SSID without a portal, or a MAC-based exemption on the guest network. If the only option is the guest network, expect to re-authenticate the player by hand each time the portal expires.
Bandwidth per screen
Playback is local: the player downloads content once and plays it from its cache, so the network is only used for updates and status. From the bandwidth reference on this site:
| Fleet | Content pattern | Recommended connection |
|---|---|---|
| 1 to 5 screens | Images, occasional video | 10 Mbps |
| 5 to 25 screens | Mixed, daily updates | 25 Mbps |
| 25 to 100 screens | Mixed, daily updates | 50 to 100 Mbps |
| Any size | Live video per screen | Add 5 to 25 Mbps per screen |
Stagger content updates and schedule big playlist changes outside business hours, so signage never competes with point-of-sale or guest Wi-Fi. A screen on 4G or 5G is sized by monthly data: 50 to 200 MB a month for heartbeats alone, under 1 GB for a weekly image refresh, 5 to 25 GB for daily video refreshes.
Troubleshooting
| Problem | Likely cause | Fix |
|---|---|---|
| Player never shows online | Captive portal, blocked port 443 or DNS | Move it off guest Wi-Fi, allow outbound 443 to *.signage.me, test DNS |
| Online and offline all day | Weak Wi-Fi, power saving, heat or a weak power supply | Check the signal at the player, turn off power saving, move to Ethernet |
| Drops every night | Wi-Fi power saving, AP roaming, DHCP lease expiry | Turn off power saving, set a DHCP reservation, use Ethernet |
| Proxy errors | Authentication required, or TLS inspection | Enter the proxy credentials; exempt signage.me from inspection |
| Content plays at the wrong time | NTP blocked | Allow UDP 123 |
| Slow downloads | Shared link saturated | Schedule updates off-peak and stagger them |
The player keeps playing cached content while it is offline, so none of these faults blank the screen by themselves; they stop updates and remote control until the connection is fixed. If the checks above do not find it, support at support@digitalsignage.com, live chat at https://chat.digitalsignage.com/ or +1-877-344-7446 can confirm what the service sees from its side.
Frequently asked questions
What ports does a DigitalSignage.com player need open?
Outbound only: TCP 443 to *.signage.me for SignStudio, registration and content, plus DNS on port 53 and NTP on UDP 123, with TCP 80 recommended for redirects. No inbound ports, static IP or port forwarding are needed; the player connects out over a real-time socket and falls back to HTTP polling behind a strict firewall.
Should a digital signage player use Wi-Fi or Ethernet?
Ethernet wherever a cable can be run; it removes most overnight blank-screen reports. If Wi-Fi is unavoidable, measure -65 dBm or better at the screen position, prefer 5 GHz, turn off Wi-Fi power saving on the player and avoid metal enclosures without an external antenna.
Does SignPlayer work through a corporate proxy?
Yes. HTTP, HTTPS and authenticated proxies are supported, SOCKS5 on Windows only, and transparent proxies work automatically. Enter the proxy host, port and credentials in the player or operating system network settings, and exempt the signage.me domains from TLS inspection.
Why will my player not connect on guest Wi-Fi?
A captive portal. The player cannot click through the sign-in page, and the session expires later even if someone does it by hand. Use a wired VLAN, a dedicated SSID without a portal, or a MAC-based exemption for the player.
How much bandwidth does each screen use?
Very little, because playback is local. Plan 0.5 to 2 Mbps average per screen, bursts of 1 to 5 Mbps during content updates and 10 to 50 kbps for status the rest of the time. Live video is the exception at 5 to 25 Mbps per screen, continuously.
Does the screen go blank when the network drops?
No. SignPlayer plays from its local cache through an outage and syncs when the connection returns. What stops is updates, remote commands and live zones such as web pages and feeds, which is why a cached fallback image belongs in every live zone.
Related
- Network requirements
- Network bandwidth requirements
- Troubleshooting FAQ
- Screens and installation FAQ
- Security best practices
- Install SignPlayer on a Raspberry Pi 5
Try it on your own screens, free
DigitalSignage.com, which publishes this guide, runs a permanent free plan: the first 3 screens are free forever (no credit card, no ads, no watermark, no time limit), then from $3 per screen per month on Plus+. Once an account has 4 or more screens, every screen is billed, so 10 screens cost $360 a year; Enterprise is priced per screen in the public price calculator. The free DigitalSignage.com SignPlayer runs on Windows, Mac, Android and Android TV, Chrome OS, Raspberry Pi, iPad or any modern web browser, so the hardware you already own usually works. Start free · 2026 pricing · How 11 vendors compare on price
Maintained by MediaSignage Inc., operator of DigitalSignage.com since 2006. Product behavior on this page comes from our own SignStudio and SignPlayer documentation; where we do not document a step, this page says so instead of guessing. Last reviewed October 22, 2026.