Collect Now Does Nothing and Changes Take Minutes

Normal updates arrive: you add a layout, wait a few minutes, and it appears on the screen. But anything meant to happen now does not. Collect Now produces nothing you can see, a remote command has no effect, a requested screenshot never comes back. Nothing errors and the display stays online throughout. That combination is the signature of one blocked network channel, and the fix is on the network rather than anything wrong with the screen.

The pattern that identifies this

Check all four.

Content, schedules and layout changes do arrive, but only after some minutes.
Collect Now, from the row menu on the Displays page, does nothing you can observe.
Request Screenshot never returns an image, or returns a stale one.
The display is listed as online, with a recent last accessed time.

What the instant-update channel is

easyCMS talks to your screens in two separate ways.

The first is the check-in. On its collection interval the player calls the CMS, asks what has changed and downloads it. This runs over outbound TCP 443 and decides whether a display shows as online.

The second is push messaging, a channel the player holds open so easyCMS can reach it between check-ins. It is what makes Collect Now, remote commands and screenshot requests feel instant. Players carry it one of two ways, both outbound to app.myeasycms.com. Either as a secure WebSocket over the 443 you already allow, or, where a player cannot do that, over TCP 9505. Nothing needs opening inbound to the player: no port forwarding, no static IP, no VPN.

Why it fails silently

A firewall that permits staff web browsing permits 443, because everything on the internet needs it. Neither form of the push channel survives on that alone. Port 9505 is not a web port, appears in no default allow rule and is dropped without comment. The WebSocket does travel on 443, but a proxy that re-signs HTTPS breaks the persistent connection it needs.

Everything else looks correct: the screen registers, downloads its content, plays it, and shows as online. The failure surfaces only the first time somebody needs a change to land immediately, often weeks after installation, which is why it reaches us as “it worked, now the buttons do nothing”.

Check it on the screen itself

The player states this outright.

Go to the screen and open the status window. On Android or Windows, press i on a connected keyboard. On an LG webOS panel, press the yellow button, then Status. See Reading the Player Status Window.
Find the XMR line.
Photograph it.

What the line means:

What it says	What it means
Names an address, ends Waiting for messages	Working
Disconnected, waiting to reconnect, last activity: and a timestamp	Blocked. This is your problem.
Not configured or Disabled	Switched off for this screen rather than blocked. That is a setting on our side, so tell us.

Tip Photographing that line turns a vague complaint into a rule your IT team can act on.

What you still have without it

Judge the urgency honestly: this is an inconvenience, not an outage. Content, schedules, layouts and media all still arrive, and scheduled events start and end at the times you set. Nothing is lost, no screen goes dark. Only the speed of a manual change is affected.

The collection interval is your fallback

Every change lands eventually, on the player’s collection interval, five minutes by default. That is the cadence you drop back to, and most sites find it liveable.

The interval is set on the display settings profile, an administrator area that stays on our side and will not appear on your login. If the push channel genuinely cannot be allowed through and five minutes is too slow, ask us and we will look at shortening it. A shorter interval means every player talks to the CMS more often, for a benefit the push channel gives free.

The line to hand your IT team

Send this word for word.

Please exempt app.myeasycms.com from HTTPS inspection. The digital signage players hold a persistent secure WebSocket to that host over the outbound TCP 443 you already permit, and an inspecting proxy breaks it.

Please also allow outbound TCP 9505 from those players to the same host, which some of them use for that channel instead. No inbound access is required.

The full checklist, covering proxies, certificates and captive portals, is Network Requirements and Firewall Rules.

When it is not this

If the display shows offline, or its last accessed time is not recent, this article does not apply: an offline screen receives nothing at all, instant or otherwise. Go to Display Shows as Offline.

If content never arrives even on the collection interval while the display stays online, that is Display Is Online but Content Never Changes instead.

If the status line says connected and pushes still do nothing, restart the player app, which clears it more often than it should. If it returns, send us the display name and a photo of the status window through the support request form.