All Collections
FAQs and Best Practices
Platform | FAQ
How to connect Players to Signagelive on a secure network
How to connect Players to Signagelive on a secure network
Ian Maison avatar
Written by Ian Maison
Updated over a week ago

Requirements before you begin:

  • Ensure that any additional endpoints for accessing the Signagelive User Interface have also been whitelisted by your firewall as per the steps in this article.

This article contains the following sections:

The following guide will provide you with the necessary endpoints to ensure your chosen Media Player devices can reach our servers if connected within a secured network. Depending on your local network’s configuration, you may require domain names or static IP addresses to be added to your firewall’s whitelist in order to connect to our Signagelive servers.

Please ensure the following endpoints have been added to your firewall whitelist:

  • *.signagelive.com

on ports 80 and 443 (please see below for specific URLs if a wildcard is not possible)

  • c274425.ssl.cf3.rackcdn.com - port 443

  • c625782.ssl.cf3.rackcdn.com - port 443

If *.signagelive.com cannot be used, the following are the URLs used by Signagelive:

  • login.signagelive.com

  • app.signagelive.com

  • betaui.signagelive.com

  • ui-networkapi.signagelive.com

  • ui-iam.signagelive.com

  • mm.signagelive.com

  • sl.signagelive.com

  • static.signagelive.com

  • proofofplay.signagelive.com

  • proof-of-play-1067503443.eu-west-1.elb.amazonaws.com

  • upload.signagelive.com

  • weatherapi.signagelive.com

Please Note

If you see a "Confirming Device Support" error message on screen, this is a common indicator that a Player is unable to reach our servers. For a full list of error messages and what they signify, please read this article.

Allowing player connections to Signagelive on a secure network

In order for your chosen Media Player hardware to access our Signagelive servers you must add the following endpoints to your firewall's allowed list. Please refer to your chosen Media Player section as applicable.

BrightSign:

  • api.signagelive.com

  • playerdataapi.signagelive.com

  • screenshotuploadapi.signagelive.com

  • static.signagelive.com

  • time.brightsignnetwork.com

  • time.signagelive.com

LG webOS:

  • api.signagelive.com

  • playerdataapi.signagelive.com

  • screenshotuploadapi.signagelive.com

  • static.signagelive.com

  • time.signagelive.com

  • nena-playerapi.signagelive.com (LG webOS 1.0 and 2.0)

  • nena-playerdataapi.signagelive.com (LG webOS 1.0 and 2.0)

  • nena-screenshotuploadapi.signagelive.com (LG webOS 1.0 and 2.0)

  • nena-static.signagelive.com (LG webOS 1.0 and 2.0)

Samsung Tizen:

  • api.signagelive.com

  • playerdataapi.signagelive.com

  • screenshotuploadapi.signagelive.com

  • static.signagelive.com

  • time.signagelive.com

Samsung SSSP (C, D and E-Series):

  • nena-playerapi.signagelive.com

  • nena-playerdataapi.signagelive.com

  • nena-screenshotuploadapi.signagelive.com

  • nena-static.signagelive.com

  • time.samsungcloudsolution.com

  • time.signagelive.com

ChromeOS + ChromeOS Flex:

  • api.signagelive.com

  • playerdataapi.signagelive.com

  • static.signagelive.com

  • time.signagelive.com

Signagelive for Windows Client:

  • api.signagelive.com

  • playerdataapi.signagelive.com

  • screenshotuploadapi.signagelive.com

  • static.signagelive.com

  • time.signagelive.com

Amazon Fire TV:

  • api.signagelive.com

  • playerdataapi.signagelive.com

  • static.signagelive.com

  • time.signagelive.com

SMIL Players (Viewsonic/Planar/IAdea):

  • go.signagelive.com

  • nena-go.signagelive.com

  • smilapi.signagelive.com

  • nena-smilapi.signagelive.com

  • static.signagelive.com

  • nena-static.signagelive.com

  • playerdataapi.signagelive.com

  • nena-playerdataapi.signagelive.com

  • widget.signagelive.com

  • time.signagelive.com

Philips:

  • api.signagelive.com

  • playerdataapi.signagelive.com

  • screenshotuploadapi.signagelive.com

  • static.signagelive.com

  • time.signagelive.com

  • nena-playerapi.signagelive.com (D-Line models running Android 4.4)

  • nena-smilapi.signagelive.com (D-Line models running Android 4.4)

  • nena-go.signagelive.com (D-Line models running Android 4.4)

  • nena-m2m.signagelive.com (D-Line models running Android 4.4)

  • nena-playerdataapi.signagelive.com (D-Line models running Android 4.4)

  • nena-screenshotuploadapi.signagelive.com (D-Line models running Android 4.4)

  • nena-static.signagelive.com (D-Line models running Android 4.4)

Legacy PC Client

  • m2m.signagelive.com

  • nena-m2m.signagelive.com

  • sl.signagelive.com

  • login.signagelive.com

  • playerdataapi.signagelive.com

  • nena-playerdataapi.signagelive.com

  • screenshotuploadapi.signagelive.com

  • nena-screenshotuploadapi.signagelive.com

  • static.signagelive.com

  • nena-static.signagelive.com

  • time.signagelive.com

macOS:

  • api.signagelive.com

  • playerdataapi.signagelive.com

  • screenshotuploadapi.signagelive.com

  • static.signagelive.com

  • time.signagelive.com

Broadcast/Browser Player:

  • api.signagelive.com

  • playerdataapi.signagelive.com

  • static.signagelive.com

  • widget.signagelive.com

  • time.signagelive.com

Please Note

Be sure to check the section below for any additional service-specific domains that you also may require depending on your use case.

Domains for specific Signagelive services:

Data Sync Services:

  • dss.signagelive.com

  • dss-gateway-api.signagelive.com

  • dss-data-api.signagelive.com

Web Triggers:

  • *.pusher.com

  • wbtapi.signagelive.com

  • nena-wbtapi.signagelive.com

Room booking:

  • roombookingapi.signagelive.com

  • nena-roombookingapi.signagelive.com

Weather:

  • nena-weatherapi.signagelive.com

  • weatherapi.signagelive.com

IP Addresses

Whilst we strongly recommend allowing the specific domains above. Should your company IT policy require IP addresses, please ensure the following are added to your firewall whitelist:

  • 162.13.104.148

  • 134.213.3.60

  • 46.38.178.155

  • 46.38.179.225

  • 31.222.175.40

  • 134.213.165.52

  • 134.213.79.62

  • 34.243.137.199

  • 34.254.41.254

Please Note

When IP addresses are used, the automatic update feature on the Samsung Smart Screen Platform is not supported as the updates are delivered via a CDN network. This is something we are actively investigating how to improve.

Connecting your Players via a Proxy

If you wish to use a Proxy Server, please check the "System Management Features" tab in this spreadsheet and the final row "Supports Proxy Server" to ensure it is supported by your device.

How can I find out more?

You can always search for answers with the Signagelive Help Centre, but rest assured we have a dedicated Support Team that is ready to assist you with any questions you may have. We are always here to help as best we can, so just contact us for any help you require.

Did this answer your question?