Player not downloading files issue

To be completed by the original poster:

CMS Version

3.0.6 running with docker

Player Type

tested with both Linux and Windows players

Player Version

Linux V1.8 R6 and Windows player V3 R301.1


after solving some issues with tasks not running in my docker CMS installation from a previous post, i started to create layouts and tried to deploy them on Windows and Linux players i installed for test. I can connect both players to my CMS server, i see the displays perfectly, i can authorize them and configure some default layout to be displayed. I see the XMR registration going on, even if i revoke it, it get registered back correctly and i can request a screenshot to the players which will show the default player screen. When i go to manage menu, i see that the displays download some files, but not all of them, and it stays like that for ever. I already checked a lot of topics in the forum around problems like mine, i had no success.
I am running my docker environment behind a reverse nginx proxy with the following configuration :

server {
listen 443 ssl;
listen [::]:443 ssl;

server_name xibo.****;

include /config/nginx/ssl.conf;

client_max_body_size 0;

location / {
    include /config/nginx/proxy.conf;
    resolver valid=30s;
    set $upstream_app xibo;
    set $upstream_port 80;
    set $upstream_proto http;
    proxy_set_header        X-Forwarded-Proto $http_x_forwarded_proto;
    proxy_pass $upstream_proto://$upstream_app:$upstream_port;
    client_max_body_size 200M;

What am i doing wrong ?

Found the issue, which wasn’t related to the proxy-conf and the reverse proxy, but to my XMR docker deployment which wasn’t accessible from the public network obviously. Now it is all understood and running well. Thanks for all. I would just have a last question, can we run multiple display on the linux player. I found an entry in the documentation about the Windows player how to do it, but not the Linux one.
Thanks for the help.

Hi again, anyone for the player over multiple screens ? I looked over a lot of threads, but didn’t found a solution. Thanks.

All right, some feedback from my side, i tried to install 2 players like in Windows running this experimental parameter for snap “snap set system experimental.parallel-instances=true” which allows you to install either different version of the same software of the same software multiple times. I succeeded in installing the app 2 times, i succeeded in registering it 2 times in CMS, however it wasn’t possible to run it 2 times, the second instance was throwing a lot of exceptions in the log.
I changed the approach then and created a display setting for 2 screens with the resolution of 3840x1080. I modified my layouts accordingly with the same resolution and placed the 2 contents side by side. I am able to run the player with this configuration, however i have a lot of instability of the player and i don’t really know what is the issue. Moreover to the exceptions in the logs, i also see often the player crashing, with no other chance to resurrect it than restart the process.
Is this coming from my configuration or does it ring a bell to someone ?
Gtk-Message: 19:26:38.097: Failed to load module “xapp-gtk3-module”
[xcb] Unknown sequence number while processing reply
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
[xcb] Aborting, sorry about that.
player: …/…/src/xcb_io.c:639: _XReply: Assertion `!xcb_xlib_threads_sequence_lost’ failed.
0# signalStacktraceHandler(int) in /snap/xibo-player/108/bin/player
1# 0x00007F793F2A3040 in /lib/x86_64-linux-gnu/
2# gsignal in /lib/x86_64-linux-gnu/
3# abort in /lib/x86_64-linux-gnu/
4# 0x00007F793F29448A in /lib/x86_64-linux-gnu/
5# 0x00007F793F294502 in /lib/x86_64-linux-gnu/
6# _XReply in /snap/xibo-player/108/usr/lib/x86_64-linux-gnu/
7# 0x00007F793A704194 in /var/lib/snapd/lib/gl/

Player exited with code 6
Gtk-Message: 19:26:50.705: Failed to load module “xapp-gtk3-module”
** Message: 19:26:53.468: console message: http://localhost:9697/251.html @6: Viewport argument value “[[viewportwidth]]” for key “width” is invalid, and has been ignored.

The Xibo Community site uses cookies. What are cookies?