Nagios Support Forum

Today I can see the upgrade announce to 1.4.3 version.

I try to upgrade by UI and it fails.

Then I try by manual upgrade and when I execute the wget it returns me:

[09:28 Fri May 23 /tmp]$ wget http://assets.nagios.com/downloads/nagi ... est.tar.gz
--2025-05-23 09:28:42-- http://assets.nagios.com/downloads/nagi ... est.tar.gz
Resolving assets.nagios.com (assets.nagios.com)... 104.18.0.245, 104.18.1.245, 2606:4700::6812:1f5, ...
Connecting to assets.nagios.com (assets.nagios.com)|104.18.0.245|:80... connected.
HTTP request sent, awaiting response... 403 Forbidden
2025-05-23 09:28:42 ERROR 403: Forbidden.

I did not make any change since the last upgrade to the system.
If I download the 1.4.3 from a browser and launch the update, it works.
But after that, in UI I get "Update Check Problem: Last update check failed" parhaps becouse it cannot reach the download server.

I repeat. I did not change anything!

Regards,
Graziano.

Both issues could be due to the proxy not working, if you have one.

No proxies... no changing since the last upgrade.
Yesterday my server could check for upgrade.
Today nothing to do.
I think Nagios admin may have changed something in the last 24h...

No one of my other Nagios Log server... one on premise and the other on cluod could reach the address...

wget http://assets.nagios.com/downloads/nagi ... est.tar.gz

Please check if you have some problem...

Regards,
Graziano.

I'm having the same issue. Yesterday I was able to run from my server successfully, but not today. I get a 403 now.

As a test I ran successfully from the same server today, so it does not appear to be a general issue with connecting to assets.nagios.com.

When I check for updates from my instance (https://www.nagios.com/checkforupdates/ ... 1741367335), I get "An error occurred while attempting to process your request. This looks to be a transient error. Try your request at a later time."

Please advise. Thanks.

EDIT: Both the download and the update check are working now.

Since this seems to be resolved, I will now lock this thread.