Issue with a server running daily build 2.5

Troubleshooting
1

First and foremost, I know 2.5 daily is not in production but I’m liking testing out the new features in a lab. I am hoping I may have found a bug/edge case that reporting would be beneficial.

CMK version: 2.5 daily build, currently 2025.08.27.cce
OS version: Debian 12

Error message: No error presented to the user, but unexpected behavior. When clicking on the unified search fly out, the screen darkens slightly but nothing else is displayed. The rest of the flyouts work as expected. Video on youtube

Environment:

  1. Work: Proxmox 8 cluster hosting a Debian 12 LXC container running 2.5 CCE
  2. Home: Proxmox 8 stand alone host running a Debian 12 LXC container running 2.5 CCE

I converted my home site to 2.5 daily in early August and have had no issues at all.

I cloned my internal work prod 2.4 site and upgraded it to 2.5 daily around the 12th of August. Immediately I could not get the search flyout. I was hoping that a future patch would fix this.

I have performed multiple upgrades to the work lab site to the current daily 2.5 without change to this behavior. I created a fresh 2.5 2025.08.27 site this morning to see if it was a corruption of the cloned site configs. The issue is present on a fresh 2.5 2025.08.27 site as well.

For the “problem” sites, I have tried from three different Windows computers with two different browsers and have tried with their respective private browsing options. There is no change in behavior.

I’m happy to provide logs from the frest test site or sanitized logs from either of the other two sites. Due to CPNI (USA privacy regulations), I cannot release unredacted details from my work lab.

Thanks!

1 Like
2

So I just checked two instances of today’s daily build and I cannot see the same issue.
Did you try any other browser? Do you use any add-ons in the browser?
Is there a firewall or proxy involved?

3

Agreed, this is not a 2.5 wide issue, but seems to be an edge case that could be a big problem if not fixed before p release.

Yes I tried from multiple browsers on different computers. I have minimal extensions that do no affect my ‘working’ 2.5 site.

No proxy. I am VPN’d into the network with wide open 80 tcp/udp and 443 tcp/udp from the VPN subnet to the subnet the sites are one.

4

Hm, that is odd for sure. But I can also not reproduce it when upgrading from 2.4.0 to 2.5.0. So it seems to be a local issue of sorts. Do you see anything in the logs? Or in the browser debugging tools?

5

No. No errors in the develop console in Chrome and nothing in either OS level or site level apache error logs.

6

As of 2025.10.21 (possibly before) this is resolved in my lab with no changes other than updating the daily build.

1 Like