When configuring Signagelive to your network you may wish to use either domain names or static IP addresses to gain a connection to our servers depending on your own requirements and configuration. The following guide provides you with the necessary information to connect your Players to Signagelive, depending on your own personal requirements:
Domain Names
To ensure that you continue to be able to use the Signagelive service, please ensure that your firewall is configured to allow the addresses below, you may need to forward this to your internal IT team for assistance with this:
You will need to ensure the following is 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
Specific URLs
If *.signagelive.com cannot be used, the following are the URLs used by Signagelive:
You will need to ensure the following is added to your firewall whitelist:
- api.signagelive.com
- app.signagelive.com
- downloads.signagelive.com
- go.signagelive.com
- login.signagelive.com
- clients.signagelive.com
- legacy.signagelive.com
- m2m.signagelive.com
- sl.signagelive.com
- smilapi.signagelive.com
- static.signagelive.com
- ui.signagelive.com
- networkapi.signagelive.com
- playerdataapi.signagelive.com
- time.signagelive.com
- ui-networkapi.signagelive.com
- screenshotuploadapi.signagelive.com
- betaui.signagelive.com
- widget.signagelive.com
- roombooking.signagelive.com
- proofofplay.signagelive.com
- mm.signagelive.com
- 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-roombookingapi.signagelive.com
- nena-wbtapi.signagelive.com
- nena-weatherapi.signagelive.com
- nena-static.signagelive.com
- Proof-of-Play-1067503443.eu-west-1.elb.amazonaws.com
- time.samsungcloudsolution.com (SSSP only)
- http://time.brightsignnetwork.com (BrightSign only) - Port: 123
- e24d24c729423ef5918c-d3c565362808015a2d9d1d45812934cb.ssl.cf3.rackcdn.com
IP Addresses
Alternatively, if your company IT policy requires IP Addresses rather than domain names these are:
You will need to ensure the following is 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
Note that when IP addresses are used the automatic update feature on the Samsung Smart Screen Platform won't work as the updates are delivered via a CDN network. This is something we are actively investigating how to improve.
Required for Web Triggers
- wbtapi.signagelive.com
- *.pusher.com
Required for Apps/Widgets that require Proxy access (e.g. News)
URL
- corsproxy.signagelive.com/
IP addresses
- 34.254.41.254
- 34.243.137.199
Screenfeed Urls
If you are using Screenfeed content ensure these URLs are allowed on your firewall:
You will need to ensure the following is added to your firewall whitelist:
- screenfeed.com
- api.screenfeed.com
- kitchen.screenfeed.com
- direct.screenfeed.com
- knife.screenfeed.com
- bowl.screenfeed.com
- fridge.kitchen.screenfeed.com
- fridge.knife.screenfeed.com
- fridge.bowl.screenfeed.com
Please Note: If you are interested in direct IP addresses for Screenfeed then it's best to speak directly with them. We know they recently moved to the cloud with Microsoft Azure services and only have one dedicated IP for their main domain. The many different subdomains in which content is stored and distributed from the feeds is part of Azures CDN network, meaning the IP's can be one of many each time the feed is called depending on geographic location etc.
How can I find out more?
You can learn more about Signagelive Security within this Help Centre section. You can also ask the Support Team any questions you may have via Live Chat or by emailing support@signagelive.com
Comments
0 comments
Please sign in to leave a comment.