LG webOS Player 4.16 stops receiving layout updates with Docker CMS 4.4.4

Get Help Xibo Player for webOS
1

Hi everyone,

I am currently evaluating Xibo for a hospital Digital Signage deployment and I’m testing different player platforms before purchasing commercial licences.

At the moment, I have found a problem that only affects the LG webOS player, while Windows and Android players work exactly as expected.

Environment

  • Xibo CMS 4.4.4

  • Self-hosted on Ubuntu Server 24.04

  • Docker Compose (official installation)

  • LG webOS Signage Player v4.16

  • CMS running on standard ports:

    • HTTP: 80

    • XMR: 9505

  • No reverse proxy

  • Default Docker networking

Problem description

The webOS player installs and connects successfully.

It:

  • Registers with the CMS.

  • Can be authorised.

  • Appears correctly in the Displays list.

  • Downloads and displays the Default Layout after a reboot.

  • Sends registerDisplay and notifyStatus requests successfully.

However, after that initial communication, the player appears to stop communicating correctly with the CMS.

The symptoms are:

  • The display status changes to disconnected.

  • The Last Accessed timestamp is only updated when the TV is powered on.

  • Publishing a new layout does not update the display.

  • Scheduling a different layout does not update the display.

  • The display continues showing the previously downloaded layout.

If I reboot the TV, it downloads the latest Default Layout again, proving that communication with the CMS is possible, but afterwards it stops receiving updates.

Comparison with other players

Using exactly the same CMS installation:

  • Windows Player works perfectly.

  • Android Player works perfectly.

  • Both receive layout changes almost immediately.

  • Only the LG webOS player fails to receive updates after the initial connection.

Tests already performed

To eliminate configuration issues I have verified the following:

  • XMDS communication is working.

  • registerDisplay requests succeed.

  • notifyStatus requests succeed.

  • Display Profile is correctly set to WebOS.

  • Display has been authorised.

  • CMS and XMR containers have been restarted.

  • TV has been restarted several times.

  • XMR container is running.

  • The CMS can reach the XMR service internally (curl ``http://cms-xmr:9505).

  • Scheduling works correctly.

  • Publishing layouts works correctly.

  • Manual layout assignment works correctly on Windows and Android players.

I also tested scheduling two different layouts only a few seconds apart:

  • Windows switched correctly.

  • Android switched correctly.

  • LG webOS never changed from the previous layout.

XMR

The XMR container only reports:

XMR Starting (Memory Limit: 256M)...

after each restart.

No additional activity is logged.

The CMS configuration contains:

XMR_HOST=cms-xmr

and the service is reachable from the CMS container.

Questions

Has anyone successfully deployed LG webOS Player v4.16 with Xibo CMS 4.4.4 running in Docker on Linux?

Is there any additional logging that can be enabled on the webOS player to determine why it stops receiving updates after the initial connection?

Any suggestions would be greatly appreciated, as this is currently the only issue preventing us from selecting webOS displays for our deployment.

Thank you.

2

Hi, thank you for posting.

Could you try the suggestion here: WebOS clients connection error with Docker CMS - #6 by alex

3

Resolved in the other thread