Skip to content
Screen Pulse Help Center

Network requirements: what your IT team needs to allow

The internet addresses Screen Pulse players and the CMS need, for networks with firewalls or filters.

Updated 2 min read

On this page
  1. Addresses to allow
  2. Schedule and program data
  3. Also check
  4. If the connection drops

Screen Pulse players need an internet connection that can reach the Screen Pulse service, Google Firebase (which sends content updates to screens instantly) and Amazon S3 (where your images and videos are stored). Everything runs over standard secure web traffic on port 443 (HTTPS). If your network uses a firewall or content filter, give your IT team the list below.

Addresses to allow

Address What it's for
app.screenpulse.io The Screen Pulse CMS, and the player signing in and loading content
screenpulse-prod.firebaseapp.com Screen Pulse's Firebase project: signing the player in to live updates
screenpulse-prod.firebasestorage.app Screen Pulse's Firebase storage
*.firebaseio.com and *.firebasedatabase.app The live-update connection itself (a long-lived secure connection)
identitytoolkit.googleapis.com, securetoken.googleapis.com Google's sign-in service for that connection
*.s3.amazonaws.com and *.s3.*.amazonaws.com Your images, videos and app content
fonts.googleapis.com, fonts.gstatic.com Fonts used by some apps

Apps that show outside content need their sites too, for example youtube.com, vimeo.com, canva.com, walls.io, dropbox.com, or the page in a Webpage Embed.

Schedule and program data

Schedules and programs from your scheduling system come through Deyra, Screen Pulse's integration service (orbitron.fivejars.net). Our servers talk to Deyra, not your screens: apps get the data from app.screenpulse.io, so your network doesn't need to allow Deyra.

Also check

  • Long-lived connections: live updates keep one secure connection open. Filters that cut connections after a few minutes make screens flip between Live and Offline.
  • SSL inspection: some security appliances inspect secure traffic, which can break the player's connection. Exclude the addresses above if possible.
  • Guest Wi-Fi with a sign-in page: a player can't click through a sign-in page. Use a network without one, or register the device's MAC address. You can find it on the screen's page; see Check which device is connected.

If the connection drops

Screens keep playing what they've already downloaded, and catch up on their own when the connection returns.

Still need help?

Our support team can walk you through it.

Contact support

Type a question or a few words, such as "screen offline" or "import donors".