I can’t seem to get XMR to actually use websockets. It is listening on port 8080. I have the URL set in the CMS. The players seem to connect to it via websocket briefly and then close or disconnect immediately and fall back to ZMQ via TCP. I’ve turned on every bit of debugging and logging I can find or think of and nothing seems to show anything is “wrong” it just doesn’t work. I really wouldn’t care beyond the fact that ZMQ is apparently on the way out and I feel like it would be a good idea to figure out why this seemingly isn’t working. Anybody got any ideas, tips/tricks, suggestions?
Is your CMS a standard docker install? If so then there isn’t any need to set the URL in settings as it defaults to /xmr and the CMS web server proxies that through to the XMR container.
Connecting briefly and then disconnecting points to an authentication issue, the player app will set an auth message to XMR as its first message, and if auth fails it will disconnect and try again later. The auth keys rely on XTR (tasks) running successfully, so you could check there first?
This is an IIS install. I’m pointing it directly to ws://xibo-cms.domain.com:8080
This is the log from the client (Windows):
Info: 2026-02-02 18:44:20XmrSubscriberXmrSubscriber - RunThread Started
Audit: 2026-02-02 18:44:20RequiredFilesAgentThreadScheduleManager - GetScheduleXmlStringGetting the Schedule XML
Info: 2026-02-02 18:44:20RequiredFilesAgentThreadRequiredFiles - ReportInventoryReporting Inventory
Audit: 2026-02-02 18:44:20ScheduleManagerThreadScheduleManager - RunSchedule Timer Ticked
Audit: 2026-02-02 18:44:20ScheduleManagerThreadScheduleManagerClearExpiredCriteria: Clearing any expired criteria
Audit: 2026-02-02 18:44:20ScheduleManagerThreadScheduleManager - LoadNewScheduleSkipping validity test for current layout.
Audit: 2026-02-02 18:44:20ScheduleManagerThreadWeatherAgentEnable: disabled
Audit: 2026-02-02 18:44:20XmrSubscriberXmrSubscriber_webSocket_OnOpen: Open
Info: 2026-02-02 18:44:20XmrSubscriberXmrSubscriber - RunDisconnected, waiting to reconnect.
Audit: 2026-02-02 18:44:25XmrSubscriber_webSocket_OnMessage: Received
Audit: 2026-02-02 18:44:25XmrSubscriber - RunConnected (tcp://xibo-cms.domain.com:9505), last activity: 2/2/2026 6:44:25 PM
If I’m interpreting it correctly it is Opening a websocket and the disconnects, then reconnects over legacy TCP. I can confirm that XMR is listening on port 8080 on the server but I’m not really sure what other debugging I can do.