Nagios Support Forum

We have an installation of xi and all is working fine. We wanted to provide a simpler view for some management users and wanted to get the simple Core status view but we tried https://ournagios.domain.com/nagios and get an "Unauthorized" error.

Attempted to change the /etc/httpd/nagios.conf to allow all basically without restrictions and still nothing.

Turned on the AuthName-"Nagios Core, AuthType Basic and AuthUserFile /usr/local/nagiosxi/etc/htpasswd.users with valid entries in there and still receiving the "Unauthorized" error.

This is a pretty standard out of the box xi install on RedHat 8.

Hi @AngeloMileto,

I don't think this should make a difference, but try going back to that url with a trailing "/".

https://ournagios.domain.com/nagios/

You should get a login prompt when you hit that endpoint, and using the same credentials as your "nagiosadmin" account for Nagios xi should provide access to the Core UI.

Thanks for the suggestion and I wouldn't have thought it to make a difference either, it did (??) I also dumped all the caches and did a new private window so ......

But now: It did NOT prompt for a username/password, just went to the Nagios home page and if I try to go to hosts, services, anything, it says "It appears as though you do not have permission to view information ....." So it clearly needs the authentication.

Not sure which config file it should be but I'll go poking around at those.

Still getting "do not have permission" error. I've checked everything I can and don't see anything in the log that would indicate an error so any help would be greatly appreciated. The home page comes up without any prompt for a login which is probably why I have permission denied. So how would I fix the login issue as this will probably fix the access denied message.

BTW, the nagiosxi page prompts for userid/password.

What is the correct configuration to allow for the nagios core web interface to work? This is a new installation and the xi interface works fine - it prompts for user credentials and all access is as expected. Going to https://site/nagios/ though does not even prompt for credentials.

I tried to copy the config from /etc/httpd/conf.d/nagiosxi.conf but that didn't seem to work either - I left the alias for /nagios pointing to /usr/local/nagios/share

There is nothing in any of the /var/log/httpd/*error* logs and there is a request in ssl_request.log but still it never prompted for credentials and still "no permission" error.

The ssl request is attempting a 'GET /nagios/cgi-bin/status.cgi?hostgroup=all' but there is no cgi-bin directory in the /nagios/ alias which should be /usr/local/nagios/share/. And in fact, there is only one cgi-bin on the system and that is in /var/www/ but it's empty. There is also no file 'status.cgi' anywhere on the system so clearly something didn't get installed properly.

BTW, this is a completely disconnected system so it was an offline install following the installation manual using the ISO and is the old version 5.9.3 - that's what we have a current license for so I'm limited for now.

Hi @AngleoMileto,

At this point I would recommend, since your issue is simplified views for managers, that you investigate dashboarding and reports in xi. You can give them dedicated dashboards and views.

We haven't initially been able to replicate this issue, though we haven't tried with 5.9.3. If you absolutely are committed to this route, I would recommend working directly with our support team. My guess is that if you don't have a more current version, though, that you also don't have current support and maintenance benefits.

xi would seem to provide the functionality you require, at least according to your initial post, so as far as Nagios staffers on the forum, we are not going to do deep troubleshooting on this issue here on the forum in this case.

Please see this doc: https://assets.nagios.com/downloads/nag ... ios-xi.pdf .

Aaron

Wasn't really expecting it to be a deep dive troubleshooting issue since this is an initial installation directly from tarball so it has to be a simple configuration issue that is causing it to not even prompt for credentials.