To be completed by the original poster:
4.5.2
Docker Ubuntu for containers, using cms_remote-mysql.yml MySQL 8.4.11 ubuntu
CMS is Ubuntu 24.04.4 MySQL is Ubuntu 24.04.5
Since upgrading to 4.5.2 to fix the “carbon” issue affecting 4.5.1, my tasks page returns 404 in the screenshot. Whether I access via our public url which uses Apache reverse proxy, or I access directly from a server on the same VLAN in our datacenter the result is the same. It looks like the route to display the Tasks is gone. I am able to add a new task successfully via the GUI wizard, the count increases by one when I do "SELECT * FROM tasks
Has anyone else experienced this. I can also confirm that all the cron jobs are still firing. Additionally the IP addresses for each player are now reporting the docker IP address when previously it correctly showed the display’s internet IP, as illustrated below with the offline display still showing its WAN ip
I guess it’s just mine then.
{"error":404,"message":"Config file not found for Task","property":null,"help":null}
For the record, this is docker install of cms
0x0
September 17, 2026, 5:51pm
4
I had same docker internal IP 172.x.x.x instead LAN IP on CMS v4.5.x
The fix was covered in the 4.5.1 Security.md file you need to add $trustedProxyIps = ‘#.#.#.#,172.18.0.0/16’ to the custom_settings.php file It’s annoying that i had to hunt for the solution, but c’est la vie.
0x0
September 23, 2026, 11:50pm
6
@Jon_Knowles ;
podman-compose uses other range 10.89.0.x
What if we dont have custom_settings.php ?
Do you maybe know if this patch could apply to be used with podman ?
@0x0 According to Overview · xibosignage/xibo-cms · GitHub you can add the same variable to web/settings.php, at the bottom i did mine right before the end of the file.
Sorry its settings-custom.php
dan
September 24, 2026, 7:44am
9
Jon_Knowles:
The fix was covered in the 4.5.1 Security.md file you need to add $trustedProxyIps = ‘#.#.#.#,172.18.0.0/16’ to the custom_settings.php file It’s annoying that i had to hunt for the solution, but c’est la vie.
We made note of it in the release notes: Changelog | Xibo Docs . How could we have made that better? Happy to take suggestions!
Did you get this part solved too?
This would imply that you have a task in your database which does not have an associated .task file. Did you have a custom task in there perhaps?
±-------±--------------------------±-----------------------------------+
From what i can see all the tasks in the database have their file associated
It seems more so that there are tasks in the directory that are not in our database.
/var/lib/docker/overlay2/668ce32af8a5ac4c00f32e9f6bc50667775b0abcedf3542e0525a7d39c4de7fa/diff/var/www/cms/tasks# findmnt -t overlay -n -o TARGET | grep overlay2 | xargs -I{} sudo find {} -type f -name “*.task” 2>/dev/null
dan
September 24, 2026, 7:32pm
12
Thanks, I’ll raise with the team and see if we can provide further guidance
