Page 1 of 1

Check Update fails in Web GUI

Posted: Mon Jun 01, 2026 3:21 pm
by stu18
Hello,

Just got 2026R1.5 installed on Ubuntu 24.04 LTS and restored from a previous install running Ubuntu 22.04 LTS. In the Check Updates page, I'm unable to get a check. It would fail instantly.

I am running a proxy and have added the proxy details in the web GUI page as per https://library.nagios.com/docs/nagios- ... th-Proxies. Also note that wget, apt, curl and other commands in terminal work flawlessly and that the proxy settings have been added to /etc/environment

In a very old install of 5.11.2 running CentOS 7, I am able to get update checks on the Web GUI. Weirdly, the proxy page doesn't load at all! LOL.

Any ideas?

Re: Check Update fails in Web GUI

Posted: Mon Jun 01, 2026 4:17 pm
by bbahn
Hello @stu18,

There was an oversight in one of the 2026R1.X updates that broke XI for systems using a proxy. There is a fix that will be out in 2026R1.6.

Re: Check Update fails in Web GUI

Posted: Mon Jun 01, 2026 4:43 pm
by stu18
Perfect, thanks! I thought I was going mad!

Re: Check Update fails in Web GUI

Posted: Tue Jun 02, 2026 1:43 am
by eakdown
stu18 wrote: Mon Jun 01, 2026 3:21 pm Hello,

Just got 2026R1.5 installed on Ubuntu 24.04 LTS and restored from a previous install running Ubuntu 22.04 LTS. In the Check Updates page, I'm unable to get a check. It would fail instantly.

I am running a proxy and have added the proxy details in the web GUI page as per https://library.nagios.com/docs/Nagios-XI-geometry dash lite-Problems-Using-Nagios-XI-With-Proxies. Also note that wget, apt, curl and other commands in terminal work flawlessly and that the proxy settings have been added to /etc/environment

In a very old install of 5.11.2 running CentOS 7, I am able to get update checks on the Web GUI. Weirdly, the proxy page doesn't load at all! LOL.

Any ideas?
The "fails instantly" part is the clue for me :) . When a proxy or network issue is the culprit, I usually expect a timeout or at least a delay. An immediate failure often points to an application-side problem.
I've seen a few cases where everything network-related was configured correctly, but the update checker itself was failing due to a missing dependency or a restore-related configuration mismatch. The logs should tell you pretty quickly which direction to investigate.