Update appears to be stuck (it's not) BUT.....

[vornado]

UPDATE: since updating Nagios XI to version 2024R1.2.2, I can no longer get to the UI in a browser using a URL with the server name. I must use the IP address instead. With the server name, I get "Invalid Host Header" on a white page

In the UI for updating Nagios, There is a text box that display the upgrade log. The log did not get to the end where it typically says:

Nagios XI Upgrade Complete!
---------------------------

You can access the Nagios XI web interface by visiting:
http://##.##.##.##/nagiosxi/

Above the text box was the indicator showing that the update was in progress. It seemed stuck at

Installing 'wizards/windowswmi.zip'


When I closed and re-opened the Nagios browser window, I got a white screen with "Invalid Host Header" in the upper left corner. I restored from the backup that the update created and tried again with the same result. Then I tried again with a backup made earlier and let it run a bit longer. While checking things on the Linux server, I stumbled across the upgrade.log file in a tmp folder. I displayed the contents with 'cat' and it looked like the update had completed, though the UI still showed that it was in progress. I opened another instance of Nagios XI in a new tab and ran 'Check for updates' and the complete log was in the text box. The first two times, I must have interrupted the update prematurely.

Anyway, if you could figure out why the text box stopped being updated with the log file contents, that would be great. I should mentioned that this issue occurred on two servers (DR and dev).

Steve

[jsimon]

Hi Steve,

It could be that you hit a php-fpm or apache limitation that prevented all of the output from the upgrade from being printed to the UI. You could diagnose this by taking a look at your log files for mentions of a timeout or other related error at the time you ran the upgrade and saw this issue. Due to the variance in system configuration, we generally recommend performing manual upgrades from the CLI, as described on page 2 of our upgrade instruction document.

For the "Invalid Host Header" issue -- this is caused by new security measures added in this release to prevent host header injection attacks. Values that are considered "valid" for your host value are the IP address of the server as you noted, as well as "localhost" and the value you input for your "External URL" (located on the General tab of System Settings).

You can fix this issue by changing External URL to the server name you use.

[vornado]

Thank you, "jsimon". I followed your advice and entered a URL with the server name we use in External URL. I will look into the php limitation you described when I have a chance. Thanks again for your help. This topic can be closed.

Steve