Hello, good news !
Adding this line seems to solve the problem:
RequestHeader set X-Forwarded-Proto expr=%{REQUEST_SCHEME}
I have only tried it on my “test” display but I have good hope it will work on my active displays as well.
I just have a remark to make about this guide as you’re mentionning it: Xibo CMS with Docker on Ubuntu 18.04 | Xibo Open Source Digital Signage (to make it better if there’s indeed an error)
I was planning to use it when I first tried to setup my Xibo CMS. But I ran into a couple issues.
- First one (which is quite specfic) is that I wanted to use my own cert. If somebody is having trouble doing that, this thread helped me a lot: Xibo 1.8.1 config to force https with own cert
- Second one which is my main point is that in the given config (the one you’ve screenshoted in your previous message), they only edit the <VirtualHost *:80>. I’m clealy not an expert so it’s maybe not an error but I don’t see how it could work without having the <VirtualHost *:443> configured.
I also have a question about “Automating CMS Credentials for the Tizen player” in R203 but I don’t know if I should ask it here or ask the helpdesk as I don’t want to go too far from the main subject here.