Network requirements
If your network controls outgoing connections with an allowlist or a proxy, your players and the people working in the CMS need to reach certain addresses. This page lists them.
All connections go from the player outwards and are encrypted via HTTPS or WSS. No incoming connections to the player are needed.
Summary
Section titled “Summary”| You use … | Allow |
|---|---|
| viewneo | *.viewneo.com, TCP 443 |
White label (CMS under cms-typer.com or your own domain) | *.cms-typer.com, TCP 443 – additionally *.viewneo.com if your players are registered via cloud.viewneo.com (see below) |
| RFID hub or Diwa (IoT) | additionally TCP 9443 to cloud.viewneo.com and broadcast.viewneo.com |
If you allow the domain with a wildcard, you are done. If you can only allow individual addresses, you’ll find them in the following sections.
Individual addresses for players
Section titled “Individual addresses for players”| Address | Port | Used for |
|---|---|---|
cloud.viewneo.com | 443 | Registration, synchronisation, commands, real-time connection (WebSocket), screenshots and logs, checking for player updates |
media.viewneo.com | 443 | Media: images, videos, fonts, Slide content |
apk.viewneo.com | 443 | Update files of the Android player |
<app>.apps.viewneo.com | 443 | Apps (content plugins), one address per app – see Apps |
Fixed IP addresses
Section titled “Fixed IP addresses”Only cloud.viewneo.com has fixed IP addresses: 75.2.35.149 and 166.117.252.219. All other addresses sit behind content delivery networks with changing IP addresses. Allow them by name, not by IP address.
White-Label
Section titled “White-Label”For white label there is a counterpart under cms-typer.com for every address:
| viewneo | White label |
|---|---|
cloud.viewneo.com | cloud.cms-typer.com |
media.viewneo.com | media.cms-typer.com |
apk.viewneo.com | apk.cms-typer.com |
<app>.apps.viewneo.com | <app>.apps.cms-typer.com |
Which of the two families a player uses depends on the address it is registered through – not on the contract:
- If the player is registered via
cloud.viewneo.com, it uses only addresses underviewneo.com. - If it is registered via
cloud.cms-typer.com, it uses only addresses undercms-typer.com.
A player never uses both families. cloud.cms-typer.com has no fixed IP addresses.
Your own domain for the CMS (e.g. signage.fjordlicht-hotels.de) is only used by the people working in the CMS, not by the players. They load thumbnails, media and app previews from the addresses under cms-typer.com.
If you use apps such as Weather or YouTube, the player needs the address of the respective app. *.viewneo.com or *.cms-typer.com covers all of them. Individually they are called <app>.apps.viewneo.com or <app>.apps.cms-typer.com, e.g. weather.apps.viewneo.com:
basketball · facebook · factsnack · instagram · linkedin · paxconnect · powerbi · sharepoint · soccer · stockmarket · weather · youtube
Apps that show content from platforms such as YouTube, Instagram or Facebook may additionally need addresses of these platforms.
CMS in the browser
Section titled “CMS in the browser”For most office networks this is not an issue. If you also control browser traffic with an allowlist, the CMS needs:
| Address | Used for |
|---|---|
cloud.viewneo.com | CMS and Designer |
media.viewneo.com, <app>.apps.viewneo.com | Thumbnails, media, app previews |
js.stripe.com, hooks.stripe.com | Payment pages |
fonts.googleapis.com, fonts.gstatic.com | Fonts |
With white label, use your CMS address (under cms-typer.com, e.g. fjordlicht.cms-typer.com, or your own domain) as well as media.cms-typer.com and <app>.apps.cms-typer.com instead of the addresses under viewneo.com.
Destinations outside viewneo
Section titled “Destinations outside viewneo”Some destinations are not operated by us:
| Address | Who | Used for |
|---|---|---|
timeapi.io | Android player | Time zone lookup |
www.speedtest.net, c.speedtest.net | Android player | Speed test that you start directly in the player interface (the speed test from the CMS runs via media.viewneo.com) |
fonts.googleapis.com, fonts.gstatic.com | Player | Fonts that some older Slides load from Google |
Time: the device needs the correct time, otherwise encrypted connections and schedules fail. Which time server (NTP, UDP 123) it uses is defined by the device’s operating system.
Your own content: websites, RSS feeds, videos from platforms and other content you embed yourself are loaded by the player directly from their addresses. Allow these depending on the content.
Proxy, TLS inspection and WebSocket
Section titled “Proxy, TLS inspection and WebSocket”- TLS inspection: players check the certificates of the other side. If a proxy breaks up HTTPS, the device must trust the proxy’s certificate – otherwise all connections fail. The easiest way is to exclude the addresses above from inspection.
- TLS version: at least TLS 1.2.
- WebSocket: the real-time connection runs via
wss://on port 443. If a proxy blocks WebSocket, the player instead checks for changes at regular intervals – commands and routines then arrive late or not at all.
Previous addresses
Section titled “Previous addresses”Players used to also use addresses under cloudfront.net, awsapprunner.com and amazonaws.com. They keep working for now, so you lose nothing if they are still allowed. Still, switch to the list above.