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

This article provides you with the relevant domains to be whitelisted when connecting Signagelive players via a secure network connection.

Ian Maison avatar
Written by Ian Maison
Updated over a week 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.

The domains you'll need to add to your firewall's whitelist will depend on which server you're accessing Signagelive from.


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

AWS (London, United Kingdom)

ap-southeast-2-1 (Sydney, Australia)

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

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

AWS

(London, United Kingdom)

The AWS instance of Signagelive is accessed via https://login.signagelive.com

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

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

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

  • ui-iam.signagelive.com

  • ui.signagelive.com

  • betaui.signagelive.com

  • sl.signagelive.com

  • widgetpreviews.signagelive.com

  • static.signagelive.com

  • ui-networkapi.signagelive.com

  • upload.signagelive.com

  • exports.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

ap-southeast-2-1

(Sydney, Australia)

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

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

If 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-ui-iam.signagelive.com

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

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

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

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

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

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

  • ap-southeast-2-1-exports.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.


AWS (London, United Kingdom)

Below are all relevant domains for connecting Signagelive Players to a secure network via the AWS (London) server.

Our Media Player End Points (AWS - London, United Kingdom)

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.

What are "Optional" domains?

Any domains listed as "Optional" in the section below should be whitelisted if you use any of the following: Weather apps, Room Booking apps, Proof of Play, Web Triggers, or Data Sync Services.

Media Player

End Points

BrightSign

All Series 4 and 5.

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

  • clients.signagelive.com (Requires Port 80)

  • api.signagelive.com

    static.signagelive.com

  • time.signagelive.com (Requires Port 80)

  • screenshotuploadapi.signagelive.com

  • widget.signagelive.com

  • corsproxy.signagelive.com

  • firmware.signagelive.com

  • Vendor required - see here.

Optional:

  • weatherapi.signagelive.com

  • roombookingapi.signagelive.com

  • playerdataapi.signagelive.com

  • wbtapi.signagelive.com

  • dss-data-api.signagelive.com

LG webOS

Models 3.0 and above

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

  • clients.signagelive.com (Requires Port 80)

  • api.signagelive.com

  • static.signagelive.com

  • time.signagelive.com (Requires Port 80)

  • screenshotuploadapi.signagelive.com

  • widget.signagelive.com

  • corsproxy.signagelive.com

  • firmware.signagelive.com

Optional:

  • weatherapi.signagelive.com

  • roombookingapi.signagelive.com

  • playerdataapi.signagelive.com

  • wbtapi.signagelive.com

  • dss-data-api.signagelive.com

LG webOS

(1.0 and 2.0)

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

  • clients.signagelive.com (Requires Port 80)

  • nena-playerapi.signagelive.com

  • nena-static.signagelive.com

  • time.signagelive.com (Requires Port 80)

  • nena-screenshotuploadapi.signagelive.com

  • nena-widget.signagelive.com

  • nena-proxy.signagelive.com

  • nena-firmware.signagelive.com

Optional:

  • nena-weatherapi.signagelive.com

  • nena-roombookingapi.signagelive.com

  • nena-playerdataapi.signagelive.com

  • nena-wbtapi.signagelive.com

Samsung Tizen
All Supported Tizen Series

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

  • clients.signagelive.com (Requires Port 80)

  • api.signagelive.com

  • static.signagelive.com

  • time.signagelive.com (Requires Port 80)

  • screenshotuploadapi.signagelive.com

  • widget.signagelive.com

  • corsproxy.signagelive.com

  • firmware.signagelive.com

Optional:

  • weatherapi.signagelive.com

  • roombookingapi.signagelive.com

  • playerdataapi.signagelive.com

  • wbtapi.signagelive.com

  • dss-data-api.signagelive.com

Samsung Tizen 2.4

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

  • clients.signagelive.com (Requires Port 80)

  • nena-playerapi.signagelive.com

  • nena-static.signagelive.com

  • nena-time.signagelive.com (Requires Port 80)

  • nena-screenshotuploadapi.signagelive.com

  • widget.signagelive.com

  • nena-firmware.signagelive.com

Optional:

  • nena-weatherapi.signagelive.com

  • nena-roombookingapi.signagelive.com

  • nena-playerdataapi.signagelive.com

  • nena-wbtapi.signagelive.com

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:

  • clients.signagelive.com (Requires Port 80)

  • nena-playerapi.signagelive.com

  • nena-static.signagelive.com

  • time.signagelive.com (Requires Port 80)

  • nena-screenshotuploadapi.signagelive.com

  • nena-widget.signagelive.com

  • nena-firmware.signagelive.com

  • time.samsungcloudsolution.com

Optional:

  • nena-weatherapi.signagelive.com

  • nena-roombookingapi.signagelive.com

  • nena-playerdataapi.signagelive.com

  • nena-wbtapi.signagelive.com

ChromeOS and
ChromeOS Flex

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

  • api.signagelive.com

  • static.signagelive.com

  • time.signagelive.com (Requires Port 80)

  • screenshotuploadapi.signagelive.com

  • widget.signagelive.com

  • corsproxy.signagelive.com

  • firmware.signagelive.com

  • Vendor required - see here.

Optional:

  • Weather - weatherapi.signagelive.com

  • Room Booking / Calendars - roombookingapi.signagelive.com

  • Proof of Play - playerdataapi.signagelive.com

  • Web Triggers - wbtapi.signagelive.com

  • Data Sync Services - dss-data-api.signagelive.com

Philips

All Supported Models

(Unless Specified)

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

  • clients.signagelive.com (Requires Port 80)

  • api.signagelive.com

  • static.signagelive.com

  • time.signagelive.com (Requires Port 80)

  • screenshotuploadapi.signagelive.com

  • widget.signagelive.com

  • corsproxy.signagelive.com

  • firmware.signagelive.com

Optional:

  • weatherapi.signagelive.com

  • roombookingapi.signagelive.com

  • playerdataapi.signagelive.com

  • wbtapi.signagelive.com

  • dss-data-api.signagelive.com

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

  • clients.signagelive.com (Requires Port 80)

  • nena-playerapi.signagelive.com

  • nena-static.signagelive.com

  • time.signagelive.com (Requires Port 80)

  • nena-screenshotuploadapi.signagelive.com

  • nena-widget.signagelive.com

  • nena-firmware.signagelive.com

Optional:

  • nena-weatherapi.signagelive.com

  • nena-roombookingapi.signagelive.com

  • nena-playerdataapi.signagelive.com

  • nena-wbtapi.signagelive.com

Sony

All Supported Models

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

  • clients.signagelive.com (Requires Port 80)

  • api.signagelive.com

  • static.signagelive.com

  • time.signagelive.com

  • screenshotuploadapi.signagelive.com

  • widget.signagelive.com

  • corsproxy.signagelive.com

  • firmware.signagelive.com

Optional:

  • weatherapi.signagelive.com

  • roombookingapi.signagelive.com

  • playerdataapi.signagelive.com

  • wbtapi.signagelive.com

  • dss-data-api.signagelive.com

Signagelive for Windows (HTML5)

Supported Appliance Players

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

  • clients.signagelive.com (Requires Port 80)

  • api.signagelive.com

  • static.signagelive.com

  • screenshotuploadapi.signagelive.com

  • widget.signagelive.com

  • corsproxy.signagelive.com

Optional:

  • weatherapi.signagelive.com

  • roombookingapi.signagelive.com

  • playerdataapi.signagelive.com

  • wbtapi.signagelive.com

  • dss-data-api.signagelive.com

Windows Legacy PC Client

Supported Windows 10/11 Players

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

  • clients.signagelive.com (Requires Port 80)

  • static.signagelive.com

  • nena-static.signagelive.com

  • screenshotuploadapi.signagelive.com

  • nena-screenshotuploadapi.signagelive.com

  • legacy.signagelive.com

Optional:

  • playerdataapi.signagelive.com

  • nena-playerdataapi.signagelive.com

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

  • smilapi.signagelive.com

  • nena-go.signagelive.com

  • nena-smilapi.signagelive.com

  • static.signagelive.com

  • nena-static.signagelive.com

  • Not Supported

  • screenshotuploadapi.signagelive.com

  • nena-screenshotuploadapi.signagelive.com

  • widget.signagelive.com

  • nena-widget.signagelive.com

  • corsproxy.signagelive.com

  • widgets.signagelive.com

  • nena-widgets.signagelive.com

  • proxy.signagelive.com

  • nena-proxy.signagelive.com

  • firmware.signagelive.com

  • nena-firmware.signagelive.com

Optional:

  • weatherapi.signagelive.com

  • nena-weatherapi.signagelive.com

  • roombookingapi.signagelive.com

  • nena-roombookingapi.signagelive.com

  • smilplayerdataapi.signagelive.com

  • nena-smilplayerdataapi.signagelive.com

  • wbtapi.signagelive.com

  • nena-wbtapi.signagelive.com

Broadcast and
Browser Player

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

  • clients.signagelive.com (Requires Port 80)

  • api.signagelive.com

  • static.signagelive.com

  • screenshotuploadapi.signagelive.com

  • widget.signagelive.com

  • corsproxy.signagelive.com

  • widgets.signagelive.com

  • proxy.signagelive.com

Optional:

  • weatherapi.signagelive.com

  • roombookingapi.signagelive.com

  • playerdataapi.signagelive.com

  • wbtapi.signagelive.com

  • dss-data-api.signagelive.com

Amazon FireTV

Supported Amazon FireTV Players

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

  • api.signagelive.com

  • static.signagelive.com

  • screenshotuploadapi.signagelive.com

  • widget.signagelive.com

  • corsproxy.signagelive.com

Optional:

  • weatherapi.signagelive.com

  • roombookingapi.signagelive.com

  • playerdataapi.signagelive.com

  • wbtapi.signagelive.com

macOS

Supported macOS Players

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

  • clients.signagelive.com (Requires Port 80)

  • api.signagelive.com

  • static.signagelive.com

  • screenshotuploadapi.signagelive.com

  • widget.signagelive.com

  • corsproxy.signagelive.com

Optional:

  • weatherapi.signagelive.com

  • roombookingapi.signagelive.com

  • playerdataapi.signagelive.com

  • wbtapi.signagelive.com


Domains for specific Signagelive services (AWS - London, United Kingdom):

Service

AWS (London, United Kingdom)

Data Integrations

(Secure Dashboards)

The following is information specifically required for Data Integrations:

  • dss.signagelive.com

  • dss-gateway-api.signagelive.com

  • dss-powerbi-oauth.signagelive.com (if using Power BI integration)

  • signagelive-dss-powerbi-prod.s3.eu-west-2.amazonaws.com (if using Power BI integration)

  • dss-sharepoint-oauth.signagelive.com (if using Sharepoint integration)

  • prod-dss-screenshots.s3.eu-west-2.amazonaws.com (if using Secure Dashboards)

  • signagelive-dss-prod-tableau.s3.eu-west-2.amazonaws.com (if using Tableau integration)

  • The fixed outbound IP address for Data Integrations is 3.9.166.241

For additional domains, please see the Player-specific URLs section.

Web Triggers

The following is information specifically required for Web Triggers:

  • *.pusher.com

  • wbtapi.signagelive.com

For additional domains, please see the Player-specific URLs section.

Room Booking

The following is information specifically required for Room Booking:

  • roombookingapi.signagelive.com

For additional domains, please see the Player-specific URLs section.

Weather

The following is information specifically required for Weather:

  • weatherapi.signagelive.com

For additional domains, please see the Player-specific URLs section.

Marketplace

  • marketplace.signagelive.com

  • marketplaceapi.signagelive.com

Network API Integrators

  • iam.signagelive.com

  • networkapi.signagelive.com

  • upload.signagelive.com

  • mediaupdateapi.signagelive.com

Message Manager

  • mm.signagelive.com

Proof of Play

  • proofofplay.signagelive.com

  • proofofplayapi.signagelive.com

For additional domains, please see the Player-specific URLs section.

SAML SSO

  • samlapi.signagelive.com

OCSP Validation

  • ocsp.digicert.com

  • status.thawte.com

  • status.geotrust.com

  • status.rapidssl.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.


ap-southeast-2-1 (Sydney, Australia)

Below are all relevant domains for connecting Signagelive Players to a secure network via the ap-southeast-2-1 (Sydney, Australia) server.

Our Media Player End Points (ap-southeast-2-1, Sydney, Australia)

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:

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

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

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

  • ap-southeast-2-1-time-api.signagelive.com (Requires Port 80)

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

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

  • corsproxy.signagelive.com

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

  • Vendor required - see here.

Optional:

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

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

  • ap-southeast-2-1-player-data-api.signagelive.com

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

LG webOS

Models 3.0 and above

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

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

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

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

  • ap-southeast-2-1-time-api.signagelive.com (Requires Port 80)

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

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

  • corsproxy.signagelive.com

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

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

Optional:

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

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

  • ap-southeast-2-1-player-data-api.signagelive.com

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

LG webOS

(1.0 and 2.0)

Currently unsupported. Please contact our Sales Team if you have any more questions.

Samsung Tizen
All Supported Tizen Series (Excluding Tizen 2.4)

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

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

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

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

  • ap-southeast-2-1-time-api.signagelive.com (Requires Port 80)

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

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

  • corsproxy.signagelive.com

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

Optional:

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

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

  • ap-southeast-2-1-player-data-api.signagelive.com

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

Samsung Smart Signage Player (SSSP)

All C, D and E Series Panels

Samsung Tizen 2.4

Currently unsupported. Please contact our Sales Team if you have any more questions.

ChromeOS and
ChromeOS Flex

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

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

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

  • ap-southeast-2-1-time-api.signagelive.com (Requires Port 80)

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

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

  • corsproxy.signagelive.com

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

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

  • Vendor required - see here.

Optional:

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

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

  • ap-southeast-2-1-player-data-api.signagelive.com

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

Philips

All Supported Models

(Unless Specified)

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

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

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

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

  • ap-southeast-2-1-time-api.signagelive.com (Requires Port 80)

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

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

  • corsproxy.signagelive.com

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

Optional:

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

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

  • ap-southeast-2-1-player-data-api.signagelive.com

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

Philips D-Line (Running Android 4.4)

Currently unsupported. Please contact our Sales Team if you have any more questions.

Sony

All Supported Models

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

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

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

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

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

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

  • corsproxy.signagelive.com

Optional:

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

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

  • ap-southeast-2-1-player-data-api.signagelive.com

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

Signagelive for Windows (HTML5)

Supported Appliance Players

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

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

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

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

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

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

  • corsproxy.signagelive.com

Optional:

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

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

  • ap-southeast-2-1-player-data-api.signagelive.com

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

SMIL Players

IAdea, Planar or Viewsonic

Currently unsupported. Please contact our Sales Team if you have any more questions.

Broadcast and
Browser Player

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

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

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

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

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

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

  • corsproxy.signagelive.com

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

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

Optional:

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

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

  • ap-southeast-2-1-player-data-api.signagelive.com

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

Domains for specific Signagelive services (ap-southeast-2-1, Sydney, Australia)

Service

ap-southeast-2-1 Domain

Data Integrations

(Secure Dashboards)

  • Not currently supported. Please speak to our Sales Team.

Web Triggers

The following is information specifically required for Web Triggers:

  • *.pusher.com

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

For additional domains, please see the Player-specific URLs section.

Room Booking

The following is information specifically required for Room Booking:

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

For additional domains, please see the Player-specific URLs section.

Weather

The following is information specifically required for Weather:

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

For additional domains, please see the Player-specific URLs section.

Marketplace

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

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

Network API Integrators

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

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

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

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

Message Manager

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

Proof of Play

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

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

    For additional domains, please see the Player-specific URLs section.URLs

SAML SSO

  • Not currently supported. Please speak to our Sales Team.

OCSP Validation

  • ocsp.digicert.com

  • status.thawte.com

  • status.geotrust.com

  • status.rapidssl.com

Downloads

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

Did this answer your question?