In your screenshot, the address 172.29.1.5 is where your CMS installed/hosted, instead of the domain name you had in previous post? If so, is that domain resolved into this internal IP?
Is the port 9505 opened and forwarded to this address?
Simply put, CMS is the server and Player is the client. The client must be able to connect to the server in order to get the layouts and schedule.
If you run “Xibo Player Options” program, and try to connet from there, did you see the message “Display is active and ready to start”? (like in my previous post)
Another way to know if the player is connected properly is in your CMS > “Displays”. You should see them there and its status.
I have start wonder if the CMR address is the real issuue here. In my server I have to docker container the first one is hosting a website and the second contrainer is hosting Xibo cms, see bellow:
appmt.order.se/
web
xibo
The NGINX is like the switch between these two.
The xmr address as we now is just appmt.order.se:9505. Should not the xmr address be like appmt.order.se/xibo:9505 since the address https://appmt.order.se/xibo is working in the Player Option but not the https://appmt.order.se?
It sounds like you need to config the nginx reverse proxy
Xibo CMS cannot be hosted in the format of “folder”, like a web site
Just to give you an example:
In our environment, we deploy the docker compose for Xibo on a single Ubuntu server internally. We set a static IP address for it 192.168.10.10.
We have our domain name as abc.domain.com
We then use NGINX Proxy Manager to forward the port (we choose 8331) and the domain from outside to the CMS. So, from outside, we can get to CMS by https://abc.domain.com:8331
However internally, we can access the CMS by going to http://192.168.10.10:80. You can omit the port 80 as it’s a standard port for http. The XMR therefore is tcp://192.168.10.10:9505
Hope it helps
