Important Announcement: Inaccurate display status. Additional network requirement for Rise Player.

  • 3
  • Announcement
  • Updated 2 years ago
  • (Edited)
Archived and Closed

This conversation is no longer open for comments or replies and is no longer visible to community members.

Many Users have reported delays with Published changes appearing on their Display and inaccurate Display Status showing when logged into We believe it is possible these issues are a result of a change we made to Rise Player a few days ago and our failure to provide notice on that change.

In order for your Display to show Published changes immediately, and show its Status accurately, a persistent connection between your Media Player and the Rise Vision Server is required. This is handled by Rise Player leveraging Google’s Channel API. Unfortunately, the Channel API is being deprecated in 2017.

As a result, we built a Messaging Service that eliminates the need for the Channel API. The problem is that we failed to recognize the impact this change would have on Users whose Media Players are running behind a firewall that is not configured to allow access to our new Messaging Service.

How do I fix the problem Please update your network to allow traffic from your Media Player to and 443

How do I know if my Media Player is impacted? Displays with Player Version RisePlayerElectron 2016. and newer will be using our new Messaging Service.

Please note that Rise Player with versions beginning with RisePlayerElectron is designed to auto upgrade to the latest version. If your Player Version begins with RisePlayerElectron, but shows a different number version than 2016. your Display will likely auto upgrade on its next reboot.

player verpng

Please accept our apologies for this oversight. If there are any questions please do not hesitate to ask.
Photo of Blake Freeman

Blake Freeman, Official Rep

  • 36,116 Points 20k badge 2x thumb

Posted 2 years ago

  • 3
Photo of Robb

Robb, Official Rep

  • 76,676 Points 50k badge 2x thumb
Official Response
Hello everyone!

We wanted to announce, that the service used for Display Status has been updated to use standard ports (80 and 443), and no longer relies on Port 3000. Thanks!