XMR Status "Waiting for messages" / downloads at 0%

CMS Version

Specify the full CMS version you are using, including the revision number.

Installation Method


Operating System

Docker is installed on ArchLinux. The client runs on Windows 10 LTSC (1809) with the latest CU.


The CMS itself works great, but my Windows client does not seem to be able to receive any data over XMR (or does 0% mean something different than that?!):

Is there any documentation about debugging XMR/Xibo? Connecting to XMR using Putty (RAW TCP) was successful, but XMR is not responding to any message I send :slight_smile:

The service itself seems to be running.

CONTAINER ID   IMAGE                                COMMAND                  CREATED      STATUS        PORTS                               NAMES
06cbc81f9f0c   xibosignage/xibo-cms:release-2.3.9   "/entrypoint.sh"         7 days ago   Up 7 days>80/tcp                xibo_cms-web_1
ad15b988b453   ianw/quickchart                      "node --max-http-hea…"   7 days ago   Up 7 days   3400/tcp                            xibo_cms-quickchart_1  
bfe8fc4c4627   mysql:5.6                            "docker-entrypoint.s…"   7 days ago   Up 7 days   3306/tcp                            xibo_cms-db_1
137d09bc051c   xibosignage/xibo-xmr:release-0.8     "/entrypoint.sh"         7 days ago   Up 7 days>9505/tcp, 50001/tcp   xibo_cms-xmr_1

Thanks in advance.


Just figured it out myself. The problem was not XMR but an nginx proxy misconfiguration, so that Xibo was returning… URLs which are not resolvable by the player. After adding the correct headers from within nginx, it works :slight_smile:

BTW: This is my nginx config (just in case). Even nginx is behind an reverse proxy, so it is running in HTTP mode. Also, I am specifically settings the Host header which seemed to be necessary in my setup.

server {
    listen 80;

    server_name cms.example.com;

    client_max_body_size 1G;

    location / {
        proxy_set_header Host "cms.example.com";
        proxy_set_header X-Forwarded-Host "cms.example.com";
        proxy_set_header X-Forwarded-Proto "https";
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.