Skip to main content
All CollectionsUsing your Signagelive NetworkFrequently Asked QuestionsPlatform | 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 2 weeks ago

The following guide will help you connect your chosen Media Player devices to our Signagelive service, providing you with the necessary endpoints to ensure you can use the solution within a secured network. Depending on the nature of your local network configuration, you may prefer or require using Domain Names or Static IP addresses to ensure access, and we provide both routes in this article.

We’ve broken the guide down into various ways to help you:

Before you begin, please ensure that your firewall has also whitelisted any additional endpoints for accessing the Signagelive User Interface, as per the steps in this article.


Signagelive Domains and IP Addresses

If your preference is to use Domains to connect your Media Player devices to Signagelive, please ensure the following endpoints have been added to your firewall whitelist:

Data

Centre

Domain

IP Addresses

Rackspace

(London)

The Rackspace (London) instance is accessed via https://login.signagelive.com

-----------------------------

  • *.signagelive.com
    (Ports 80 and 443)

In the event that you cannot use the wildcard *.signagelive.com, 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

In addition, the following must be added:

  • c274425.ssl.cf3.rackcdn.com (Port 443)

  • c625782.ssl.cf3.rackcdn.com (Port 443)

  • ocsp.digicert.com

  • status.thawte.com

  • status.geotrust.com

  • status.rapidssl.com

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

  • 192.229.211.108

  • 192.229.221.95

  • 152.195.38.76

  • 192.16.49.85

ap-southeast-2

(Sydney, Australia)

The AP-Southeast-2 instance is accessed via https://ap-southeast-2-1-login.signagelive.com

-----------------------------

In the event that you cannot use the wildcard *.signagelive.com, the following are the URLs used by Signagelive:

  • ap-southeast-2-1-login.signagelive.com

  • ap-southeast-2-1-web-service.signagelive.com

  • ap-southeast-2-1-ui.signagelive.com

  • ap-southeast-2-1-ui-networkapi.signagelive.com

  • ap-southeast-2-1-networkapi.signagelive.com

  • ap-southeast-2-1-ui-iam.signagelive.com

  • ap-southeast-2-1-mm.signagelive.com

  • ap-southeast-2-1-sl.signagelive.com

  • ap-southeast-2-1-static.signagelive.com

  • ap-southeast-2-1-proofofplayui.signagelive.com

  • ap-southeast-2-1-proofofplay-api.signagelive.com

  • ap-southeast-2-1-upload.signagelive.com

  • ap-southeast-2-1-weatherapi.signagelive.com

  • ap-southeast-2-1-calendarintegration.signagelive.com

  • ap-southeast-2-1-marketplaceapi.signagelive.com

  • ap-southeast-2-1-marketplace-ui.signagelive.com

  • ap-southeast-2-1-saml-api.signagelive.com

  • ap-southeast-2-1-media-update-api.signagelive.com

  • ap-southeast-2-1-proxy.signagelive.com

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


Our Media Player End Points

If you would like to know the specific endpoints needed depending on your selected Media Player hardware, please refer to your chosen Media Player section as applicable, and this detailed information will be presented to you.

Media Player

End Points

BrightSign

All Series 4 and 5.

If using a BrightSign Media Player with Signagelive, the following must be allowed:

  • api.signagelive.com

  • playerdataapi.signagelive.com

  • screenshotuploadapi.signagelive.com

  • static.signagelive.com

  • time.brightsignnetwork.com

  • clients.signagelive.com (Requires Port 80)

  • time.signagelive.com (Requires Port 80)

LG webOS

All Supported Models

(Unless Specified)

If using an LG webOS Media Player with Signagelive, the following must be allowed:

  • api.signagelive.com

  • playerdataapi.signagelive.com

  • screenshotuploadapi.signagelive.com

  • static.signagelive.com

  • clients.signagelive.com (Requires Port 80)

  • time.signagelive.com (Requires Port 80)

The following are also required for LG webOS 1.0 and 2.0 Panels

  • nena-playerapi.signagelive.com

  • nena-playerdataapi.signagelive.com

  • nena-screenshotuploadapi.signagelive.com

  • nena-static.signagelive.com

Samsung Tizen
All Supported Tizen Series

If using a Samsung Tizen Media Player with Signagelive, the following must be allowed:

  • api.signagelive.com

  • playerdataapi.signagelive.com

  • screenshotuploadapi.signagelive.com

  • static.signagelive.com

  • clients.signagelive.com (Requires Port 80)

  • time.signagelive.com (Requires Port 80)

Samsung Smart Signage Player (SSSP)

All C, D and E Series Panels

If using a Samsung Smart Signage Player with Signagelive, the following must be allowed:

  • nena-playerapi.signagelive.com

  • nena-playerdataapi.signagelive.com

  • nena-screenshotuploadapi.signagelive.com

  • time.samsungcloudsolution.com

  • clients.signagelive.com (Requires Port 80)

  • time.signagelive.com (Requires Port 80)

ChromeOS and
ChromeOS Flex

If using a ChromeOS or ChromeOS Flex Media Player with Signagelive, the following must be allowed:

  • api.signagelive.com

  • playerdataapi.signagelive.com

  • static.signagelive.com

  • clients.signagelive.com (Requires Port 80)

  • time.signagelive.com (Requires Port 80)

Philips

All Supported Models

(Unless Specified)

If using a Philips Player with Signagelive, the following must be allowed:

  • api.signagelive.com

  • playerdataapi.signagelive.com

  • screenshotuploadapi.signagelive.com

  • static.signagelive.com

  • clients.signagelive.com (Requires Port 80)

  • time.signagelive.com (Requires Port 80)

The following are also required for Philips D-Line Models running Android 4.4

  • nena-playerapi.signagelive.com

  • nena-smilapi.signagelive.com

  • nena-go.signagelive.com

  • nena-m2m.signagelive.com

  • nena-playerdataapi.signagelive.com

  • nena-screenshotuploadapi.signagelive.com

  • nena-static.signagelive.com

Sony

All Supported Models

If using a Sony Media Player with Signagelive, the following must be allowed:

  • api.signagelive.com

  • playerdataapi.signagelive.com

  • screenshotuploadapi.signagelive.com

  • static.signagelive.com

  • clients.signagelive.com (Requires Port 80)

  • time.signagelive.com (Requires Port 80)

Signagelive for Windows (HTML5)

Supported Appliance Players

If using a Windows (HTML5) Media Player with Signagelive, the following must be allowed:

  • api.signagelive.com

  • playerdataapi.signagelive.com

  • screenshotuploadapi.signagelive.com

  • static.signagelive.com

  • clients.signagelive.com (Requires Port 80)

  • time.signagelive.com (Requires Port 80)

Windows Legacy PC Client

Supported Windows 10/11 Players

If using a Windows (Legacy PC Player) with Signagelive, the following must be allowed:

  • 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

  • clients.signagelive.com (Requires Port 80)

  • time.signagelive.com (Requires Port 80)

SMIL Players

IAdea, Planar or Viewsonic

If using a SMIL Player (IAdea, Viewsonic or Planar) with Signagelive, the following must be allowed:

  • 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

  • clients.signagelive.com (Requires Port 80)

  • time.signagelive.com (Requires Port 80)

Port 80 will be required when using a SMIL player and the above-listed URLS.

Broadcast and
Browser Player

If using a Broadcast or Browser Player with Signagelive, the following must be allowed:

  • api.signagelive.com

  • playerdataapi.signagelive.com

  • static.signagelive.com

  • widget.signagelive.com

  • clients.signagelive.com (Requires Port 80)

  • time.signagelive.com (Requires Port 80)

Amazon FireTV

Supported Amazon FireTV Players

If using an Amazon Fire TV Media Player with Signagelive, the following must be allowed:

  • api.signagelive.com

  • playerdataapi.signagelive.com

  • static.signagelive.com

  • clients.signagelive.com (Requires Port 80)

  • time.signagelive.com (Requires Port 80)

macOS

Supported macOS Players

If using a macOS Player with Signagelive, the following must be allowed:

  • api.signagelive.com

  • playerdataapi.signagelive.com

  • screenshotuploadapi.signagelive.com

  • static.signagelive.com

  • clients.signagelive.com (Requires Port 80)

  • time.signagelive.com (Requires Port 80)


Domains for specific Signagelive services:

Media Player

Models

Data Integrations

(Secure Dashboards)

The following is information specifically required for Data Integrations:

  • dss.signagelive.com

  • dss-gateway-api.signagelive.com

  • dss-data-api.signagelive.com

  • The fixed outbound IP address for Data Integrations is 3.9.166.241

Web Triggers:

The following is information specifically required for Web Triggers:

  • *.pusher.com

  • wbtapi.signagelive.com

  • nena-wbtapi.signagelive.com

Room booking:

The following is information specifically required for Room Booking:

  • roombookingapi.signagelive.com

  • nena-roombookingapi.signagelive.com

Weather

The following is information specifically required for Weather:

  • nena-weatherapi.signagelive.com

  • weatherapi.signagelive.com

Remote firmware updates

This feature is not supported on every player type. Those that do support remote firmware updates will need access to:

  • firmware.signagelive.com

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 your device supports it.

Did this answer your question?