CMS 4.5 non-docker installation issues

Get Help CMS Installation
1

There are some problems with this update if you’re doing it on a Windows Server using IIS. In particular you will get stuck in an infinite login loop where you login, will get sent the dashboard URL and immediately kicked back out. You’ll need to remove the {HTTP_AUTHORIZATION} line in the URL Rewrite Imported Rule 1 to make that work (the .htaaccess rule that you use to import the rules apparently as not updated).

The second issue you’ll find is you’ll have 404’s for theme.css and logo.png because they reference a /brand folder that does not exist, you’ll have to create that yourself. Create a “brand” folder under the “library” folder, go into IIS and create a new Virtual Directory under your Xibo site, alias as “brand” and point it to that brand folder you just created. Load in a theme.css (mine is empty) and a logo.png file and this will solve the 404’s and the broken logo image in the top left corner.

2

And here’s another one: XMR will be broken due to invalid keys. The documentation states that the XMR Private Address should be 127.0.0.1:8081 but…apparently you enabled SSRF Protection which blocks traffic to the loopback address. If you change the address to the the same IP of the server, XMR will be able to retrieve the correct key and resume working.

3

For anyone new reading this, Xibo is not intended to run outside of our Docker environment

Thank you for documenting these additional steps, I am sure they will be helpful to others using IIS.

4

I understand that it is only supported to be run in the Docker configuration. I don’t understand why it is becoming increasingly difficult to run it outside of the Docker configuration.

5

Xibo is under active development and maintenance, meaning we continue to improve it, update it and keep it safe and secure. We do that on Docker and test it on Docker+Linux. We do not intentionally put breaking changes into the software, but it is not designed to be run on IIS, or outside of Docker, and that is the reason it becomes harder to run over time.

6

I have now managed to get 4.5.0 completely working on a manual install on Debian Trixie.

7

me too,

So I returned 4.4.4 and waited for 4.5 to mature

The current Xibo is more like two branch versions, 4.4.4 with long-term stable maintenance and 4.5 full of future

8

For anyone wondering, this isn’t the case :smiley:

We know that the UI change is a big one, so 4.4 will receive security updates for a period of time, however all other maintenance will be in 4.5 and beyond :rocket:

9

I have solved by placing the public address of the server, there is no need for port 8081 to be accessible from outside. Now it work flawless in my environment.

BTW My xibo server is running in a lxc container inside proxmox, making docker run in proxmox inside a LXC container is really a pity…