Network Requirements For Ports And Domains

If you deploy signageOS-powered devices within restricted networks, you have to check availability/connectivity to domains and ports below.

Domains

Devices accessing the signageOS Cloud

warning

EU region: devices are moving to the new device gateway. Devices in the EU region connect to gateway.root.signageos.io and upload screenshots to upload.root.signageos.io. Newly set-up devices start using these domains on November 4, 2026, and existing devices are being moved to them. After November 30, 2026, devices can no longer connect through platform.signageos.io, so a device that cannot reach gateway.root.signageos.io goes offline. Keep config.signageos.io and upload.signageos.io allowed as well, and keep platform.signageos.io allowed for devices with older Core App versions, which still load their configuration from it. Devices in the US1 region and devices connecting through gateway.signageos.io are not affected. See the announcement for details.

signageOS rolls out additional regions for EU and US. Customers will be able to choose one of the regions for their device fleet management. Global endpoints must always be allowed along with region-specific ones.

Domain	Protocol	Port	Notes
EU region gateway.root.signageos.io	ws(s), http(s)	443/80	Primary access point for devices in the EU region
EU region gateway.signageos.io	ws(s), http(s)	443/80	Alternative EU-region device endpoint, served through a CDN: devices connect to the nearest edge location
EU region platform.signageos.io	http(s)	443/80	Device configuration for older Core App versions. It was the primary access point for devices before gateway.root.signageos.io. Current Core App versions load their configuration from config.signageos.io only, but older versions still use this domain, so keep it allowed
EU region upload.root.signageos.io upload.signageos.io	http(s)	443/80	Service for uploading screenshots. Some devices still upload to upload.signageos.io, so keep it allowed
US1 region gateway.us1.signageos.io	ws(s), http(s)	443/80	Primary access point for devices in the US1 region
US1 region upload.us1.signageos.io	http(s)	443/80	Service for uploading screenshots in the US1 region
All regions config.signageos.io	http(s)	443/80	Device configuration
Additional regional endpoints gateway.us2.signageos.io gateway.us3.signageos.io gateway.eu1.signageos.io gateway.eu2.signageos.io gateway.eu3.signageos.io	ws(s), http(s)	443/80	Device access points in additional regions
Additional regional endpoints upload.us2.signageos.io upload.us3.signageos.io upload.eu1.signageos.io upload.eu2.signageos.io upload.eu3.signageos.io	http(s)	443/80	Service for uploading screenshots in additional regions
Global endpoints applet-synchronizer.signageos.io	ws(s), http(s)	443/80	Optional - For synchronized content playback, on-prem deployment recommended
Global endpoints 1.signageos.io, static.signageos.io, 2.signageos.io US-regions endpoints static.us1.signageos.io	http(s)	443	CDN endpoint
Global endpoints rm1.signageos.io	ws(s), http(s)	443/80	Samsung RM Management endpoint
Global endpoints icanhazip.com, ipv4.icanhazip.com, captive.apple.com	http(s)	443	For checking internet connectivity, fallback URLs
Global endpoints remote-desktop.signageos.io US-regions endpoints remote-desktop.us1.signageos.io	https	443	Remote desktop endpoint
US-regions endpoints auth0.us1.signageos.io	https	443	Authentication endpoint for the US1 region
US-regions endpoints weinre.us1.signageos.io	http(s)	443	Optional - Remote debugging in the US1 region

Checking the connection from your network

For devices in the EU region, run these from a computer on the same network as the devices. Both must succeed:

curl -sv https://gateway.root.signageos.io/time
curl -sv -o /dev/null https://upload.root.signageos.io/

The first command returns a JSON timestamp, for example {"timestamp":1793104488536}. If either command times out or fails the TLS handshake, the network is blocking the domain. To test a real device instead, see Testing the connection to the new network endpoint.

Ports

Only port 443 is mandatory. Port 80 is used as a failover option when 443 is not available, for example:

- the device has incorrect time and the SSL certificate is invalid

- SSL root certificate on the device is invalid

- proxy setup blocks WebSocket over SSL

It's highly recommended to allow the traffic on port 80. It's used only in the above-mentioned scenarios and helps mitigate issues without dispatching teams.

Device Network Bandwidth

• The device usually uses between 2kb/s and 4kb/s, depending on the number of additional REST API requests you perform.
• During the first boot up, device needs to perform the whole registration handshake and share initial data. The total initial communication size is about 50kb.
• Average screenshot size, that is uploaded is 500 KB to 1.2 MB.
• Recommended minimum network speed is 2Mbs download, 2Mbs upload with network latency less than 1000ms.

Proxy the device communication

 

Currently, it’s not possible to proxy communication from devices due to High-availability setup and Load balancers configuration. In case of a large project, kindly reach out to signageOS sales rep for further discussion.

Device deployments

All domains in this section are in the category of Global endpoints and must be allowed.

Domain	Protocol	Port	Notes
1.signageos.io, static.signageos.io, 2.signageos.io	http(s)	443	CDN endpoint
hugstatic.blob.core.windows.net	http(s)	443	Deprecated, CDN endpoint
w.signageos.io	http(s)	443	Optional - Endpoint for installing the latest LG webOS application (shortcut)
a.signageos.io	http(s)	443	Optional - Endpoint for installing the latest Android application (shortcut)
t.signageos.io	http(s)	443	Optional - Endpoint for installing the latest Samsung Tizen application (shortcut)
s.signageos.io	http(s)	443	Optional - Endpoint for installing the latest Samsung SSSP 2/3 application (shortcut)
b.signageos.io	http(s)	443	Optional - Endpoint for installing the latest BrightSign application (shortcut)
c.signageos.io	http(s)	443	Optional - Endpoint for installing the latest Chrome application (shortcut)
win.signageos.io	http(s)	443	Optional - Endpoint for installing the latest Windows application (shortcut)
o.signageos.io	http(s)	443	Optional - Endpoint for installing the latest Linux image application (shortcut)
cc.signageos.io	http(s)	443	Optional - Endpoint for installing the latest Cloud Control application (shortcut)
weinre.signageos.io	http(s)	443	Optional - For remote debugging
t.us1.signageos.io	http(s)	443	Optional - Endpoint for installing the latest Samsung Tizen application in the US1 region (shortcut)
w.us1.signageos.io	http(s)	443	Optional - Endpoint for installing the latest LG webOS application in the US1 region (shortcut)
b.us1.signageos.io	http(s)	443	Optional - Endpoint for installing the latest BrightSign application in the US1 region (shortcut)

Device management from CMS ↔ signageOS Cloud

Domain	Protocol	Port	Notes
api.signageos.io	https	443	Primary REST API endpoint
api.us1.signageos.io	https	443	REST API endpoint for the US1 region

Other domains used in signageOS Ecosystem

Domain	Notes
box.signageos.io	Device management console
box.us1.signageos.io	Device management console for the US1 region
npm.signageos.io	Private NPM repository

Synchronizer

signageOS offers a server-less synchronized playback API. To sync content, devices establish UDP communication within the local network. Below are the network requirements.

Communication is happening only in the local network.

Protocol	Port
UDP	60537
TCP	60538

Estimated bandwidth is ~30kbps for 4 synced displays.

Testing tool for synchronized playback communication

To validate that your local network supports synchronized playback, contact us through the signageOS Support Portal for the network testing tool.

Third-party domains

NTP servers on webOS:

Below-mentioned NTP servers are used as default servers on LG webOS devices. If you are using older webOS devices (v. 1.0, 2.0, 3.0), you should enable such domains in your network.

nist1.symmetricom.com, 69.25.96.13, San Jose, California 

nist1-sj.ustiming.org, 216.171.124.36, San Jose, California

nist1-la.ustiming.org, 64.147.116.229, Los Angeles, California

nist1-lv.ustiming.org, 64.250.229.100, Las Vegas, Nevada

HTTP(S) Requests Origins going from Applet

Below is the table containing paths to loading applets on each currently supported platform. These paths are also an origin of any HTTP(S) request.

Platform	Path
Samsung SSSP	file:///mtd_down/common/cache/
Samsung Tizen	file:///opt/usr/media/Documents/data/data/applet/
LG WebOS	file:///media/cryptofs/apps/usr/palm/applications/com.lg.app.signage/
Brightsign	http://localhost:8081/sd/applet/
Android (Philips, Sharp, Panasonic, Elo,...)	https://appassets.android.signageos.io Legacy for CA <4.5: content://io.signageos.android.fileprovider
Raspberry Pi	http://localhost:8081/internal/data/applet/
CLI Emulator	http://localhost:8090
Windows	http://localhost:8090 + http://localhost:3000