Display (FireTV Stick) is not showing the Content. Always loading status (Using docker with Ubuntu 20.04 LTS on AWS)

Hello, i am new to Xibo but i am very happy about it and excited to use it.

I am having a virtual machine on AWS (Amazon Web Service) running Ubuntu 20.04 LTS. I am using Xibo in a docker with version 3.1.4. Here is my docker-compose file

version: "2.1"

        image: xibosignage/xibo-xmr:0.9
            - "9505:9505"
        restart: always
        env_file: config.env
        mem_limit: 256m
            - schwan
            - vpn
        image: xibosignage/xibo-cms:release-3.1.4
            - "./shared/cms/custom:/var/www/cms/custom:Z"
            - "./shared/backup:/var/www/backup:Z"
            - "./shared/cms/web/theme/custom:/var/www/cms/web/theme/custom:Z"
            - "./shared/cms/library:/var/www/cms/library:Z"
            - "./shared/cms/web/userscripts:/var/www/cms/web/userscripts:Z"
            - "./shared/cms/ca-certs:/var/www/cms/ca-certs:Z"
        restart: always
            - cms-xmr:50001
            - XMR_HOST=cms-xmr
            - CMS_USE_MEMCACHED=true
            - MEMCACHED_HOST=cms-memcached
            - "89:80"
        env_file: config.env
        mem_limit: 1g
            - schwan
            - vpn

        image: memcached:alpine
        command: memcached -m 15
        restart: always
        mem_limit: 100M
            - schwan
            - vpn

      image: ianw/quickchart
      restart: always
            - schwan
            - vpn

    external: true
    external: true

I opened following ports on AWS for Xibo

TCP 9505
TCP 443
TCP 80

all other ports, except system relevant ones, are closed

I am running mySQL docker instance seperatly because it is used by other services as well.

The docker start properly, i can log in and have added a screen. I’ve installed the player on a Amazon Fire HD TV stick and registered on my Xibo instance. Everything looks good so far.

I’ve created a new layout and tried to deploy it to the screen but the screen don’t change. Not even showing the layout when nothing is deployed. The status on Xibo webinterface looks like:

I’ve looked into another thread already and the advice was to enable auditing. After asking for a screenshot i get following log

General Information
Date: 2022-08-20 17:45:46
Version: 3
Code Version: 300 - b67655d (2022-08-07 09:55:46)
Content Management System: https://signage.***.de/xmds.php (tcp://signage.***.de:9505 - 2022-08-20 17:45:40 - 5 Sekunden und 378 Millisekunden ago)
WIFI: rssi = -30, Hz = 2412
Last Heartbeat: 4 Minuten, 4 Sekunden und 720 Millisekunden ago.
Storage Selected: Internal Storage. 83.0%
Display Name: ***_links
Licenced: true (trial, 1 days remaining)
Registered: true
Current Layout: Normal: 0
Screen Size: 1920 x 1080
Memory Limit: 384 MB
Memory Allocation: 25 MB
Image Cache Hit Rate: 1,00
Screen Shot Request Interval: 0
Use Surface View for Video Rendering?: true
Video Engine in use: ExoPlayer
Use multiple video decoders: true
Number of Stats ready to send: 0 - 2021-08-20 17:45:46
Number of Logs ready to send: 0 - 2022-08-20 17:34:07

CMS Status
Register: Registered. Checked at 2022-08-20 17:42:18
Schedule: Skipped
Required Files (Inside Download Window): Skipped. 25/25
Queued Network Connections - F: 0 / N: 0. HTTP: 3 / Idle: 3
Number of Concurrent Failed XMDS Connections: 0

Schedule Status
All layouts (* = not scheduled): 6, 6, 6, 6 (D),
Scheduled Layouts:
Valid Layouts:
Invalid Layouts: 6, 6, 6, 6,
Next Schedule Update: 2022-08-20 17:47:19


Last 5 log messages

Install Service Status
Update Window: 00:00 - 00:00
Version Information from CMS:

I’ve edited the config.env file and added mySQL and STMP informations. Entered official URL as CMS_SERVER_NAME. CMS_QUICK_CHART is commented.

To exclude the Firetv stick I created a trial account for Xibo Cloud and there my layout, which I exported from my Docker and imported into the cloud, loaded on the first try.

I guess its a Nginx problem. I use Neginx to manage the connections to the Dockers. I use HTTPS and created the SSL certs with cerbot of LetsEncrypt.

Here is my Nginx configuration

upstream mf-signage {
  server        localhost:89;

server {
  server_name   signage.***.de;

  location / {
    proxy_pass  http://mf-signage;

    listen 443 ssl; # managed by Certbot
    ssl_certificate /etc/letsencrypt/live/signage.***.de/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/signage.***.de/privkey.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot


server {
    if ($host = signage.***.de) {
        return 301 https://$host$request_uri;
    } # managed by Certbot

  listen        80;
  server_name   signage.***.de;
    return 404; # managed by Certbot

Is anyone able to identify the error or what I am doing wrong? I would be very thankful if you can point me to the right direction to solve this problem.

Thank you very much

p.s. If I have missed any information, please let me know and I will provide it later

best regards

Okay found it. I just had to add following to nginx config

    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;

and activate https forcing in settings.

Thank you very much for Xibo, it is awesome