Search found 4 matches
- Wed Jan 22, 2025 9:37 am
- Forum: Open Source Nagios Projects
- Topic: Unable to Access Nagios Web Interface After Updating Nagios Core to 4.5.9
- Replies: 11
- Views: 31094
Re: Unable to Access Nagios Web Interface After Updating Nagios Core to 4.5.9
We also have CentOS 7. I need to find some time to migrate away.
- Tue Jan 21, 2025 9:51 am
- Forum: Open Source Nagios Projects
- Topic: Unable to Access Nagios Web Interface After Updating Nagios Core to 4.5.9
- Replies: 11
- Views: 31094
Re: Unable to Access Nagios Web Interface After Updating Nagios Core to 4.5.9
Thanks @MortenSickel !
Your solution fixed it. There are still some quirks, for instance the "Home" page is completely blank, but the rest of the webpages "Services", "Hosts", etc. all are accessible again.
Your solution fixed it. There are still some quirks, for instance the "Home" page is completely blank, but the rest of the webpages "Services", "Hosts", etc. all are accessible again.
- Mon Jan 20, 2025 4:42 pm
- Forum: Open Source Nagios Projects
- Topic: Unable to Access Nagios Web Interface After Updating Nagios Core to 4.5.9
- Replies: 11
- Views: 31094
Re: Unable to Access Nagios Web Interface After Updating Nagios Core to 4.5.9
When something like that happens, your best bet is to have a look at the web server error logs. On RHEL/CentOS/Oracle distributions they're most likely under /var/log/php-fpm. On Debian and Ubunto they're most likely under /var/log/apache2. If you attach a snippet of the end of the error log, we'll...
- Mon Jan 20, 2025 10:40 am
- Forum: Open Source Nagios Projects
- Topic: Unable to Access Nagios Web Interface After Updating Nagios Core to 4.5.9
- Replies: 11
- Views: 31094
Unable to Access Nagios Web Interface After Updating Nagios Core to 4.5.9
I updated Nagios Core from version 4.5.7 to 4.5.9 by following the instructions at https://assets.nagios.com/downloads/nagioscore/docs/nagioscore/4/en/upgrading.html. However, after the update, I cannot access the Nagios web interface. It returns an HTTP Error 500 "This page isn't working and c...