Connecting player on xibo docker

Get Help
1

Hello everybody,

I installed xibo on a docker on my synology 218+ nas. Work well, reverse proxy too.
I can access CMS by https://xibo.XXXXX.com and configure everything.

But when i try to connect the player, the message is “La connexion sous-jacente a été fermée : Une erreur inattendue s’est produite lors de l’envoi” (The underlying connection was closed: An unexpected error occurred while sending).

I disabled firewalls on both sides but it’s no better

Someone have a idea? same probleme?

Thank you.

2

Are you using SSL? If so, please use Quallys SSL labs to check your SSL configuration, especially with respect to any certificate chain issues.

3

Thank you Alex for the quick answer.

I don’t know how to interpret the results but it seems good. The note is a A and everything is green

image
image2560×2160 417 KB

4

That all looks OK.

Please can you ensure that the reverse proxy is passing through the Host header, and X-Forwarded headers (including X-Forwarded-Proto) to the container?

5

Whaou ! Alex, I’m not sure I really understand your request.

I followed cslaughter’s tutorial to install XIBO on synology.
How could I verify all that ?

6

You might be best asking him then as that’s not an official guide.

I’ve no idea how you’ve configured your reverse proxy, but it’s that that the Player is connecting to initially, so that’s where I’d start debugging.

If you want direct support from the project, then using our recommended installation method, or using a Cloud CMS will give you the best results.

7

Hi again,
I can’t stand to understand nothing. So, I read some documentations about nginx reverse proxies.
I found my configuration (I’m on a synology nas).

There it is :

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

    server_name xibo.domaine.com;

    ssl_certificate /usr/syno/etc/certificate/ReverseProxy/c9817a70-f8ce129c3213/fullchain.pem;

    ssl_certificate_key /usr/syno/etc/certificate/ReverseProxy/c9817a70-f8ce129c3213/privkey.pem;

    location / {
        proxy_set_header        Host                $http_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;
        proxy_intercept_errors  on;
        proxy_http_version      1.1;

        proxy_pass http://localhost:8888;

    }

From the top of my weak skills in reverse proxy I can see that Host and X-Forwarded headers are well configured.
The container has the 8888 port.
Now, tell you if all informations arrives to the container, I would not be able to do it.
I don’t know if there is a log for that.

Arno.

8

What happens if you drop http2 support?

9

Same result.

When I click on “Display Admin”, I get the cms home page !

10

What OS are you running the Player on?

11

I’m on a windows 7 service pack 1 with IE 11.

12

I’m afraid I don’t know then. My guess is that it’s related to the SSL configuration since the connection is never even established, rather than it being anything related to Xibo.

I’d try without SSL to confirm that, and then you can look at changing available protocol suites etc to get it working.