Remote web interface blank

[villager]

I have a rhel 6 server with Nagios installed. It's all happy. On the server I can bring up the web interface, login, change pages and it's all fine. When I try to access the web interface remotely though it prompts for a username/password and then hangs. It eventually gives a

Some Background
- selinux and iptables are not running on the server (I'm on a closed network, I turned them off for testing anyway)
- I'm not using SSL and have not changed default ports or anything
- httpd is ok. I have some other web based tools installed and they are all fine both via the server and remotely.
- the username/password is ok as I can use the same details on the server to access the web interface
- rhel 6.5
- Nagios 4.3.4
- Apache 2.2.15
- I can't really update the apache or rhel version.

When I try to connect to either the hostname or ip, the status line shows 'waiting for response from <hostname> and then after a few minutes it throws the following into the httpd error log file

[error] [client myip ] Invalid method in request

Does anyone have any idea what 'the invalid method' might be? Suggestions for how to dig further? Use a browser on the server and it works perfectly.

[kyang]

Could you post your httpd error logs? (You can wrap this output in "code" blocks to make it easier for us to read. Thanks!)

Code: Select all

tail -50 /var/log/httpd/error_log

Along with the output of curl and wget towards your nagios server.

Code: Select all

curl http://ip/nagios

Code: Select all

wget http://ip/nagios

Thanks!

[villager]

I'm afraid that although I have admin rights on the server, I don't have access to curl, wget etc on remote clients where I'm trying to run explorer/chrome to the nagios admin page.

The admin page looks fine when I run firefox on the server. On the remote windows client is just hangs at 'waiting for server...' for ages and then fails. I tried from another Linux host

There is nothing in the httpd error log file, nothing in the messages file.

I think it's maybe somethiing being blocked by a network firewall (not on the server, selinux and iptables off) but it's odd because I do get the username/password page. It's the authentication that doesn't get through.

Does it use any other port other than http to communicate with the admin console that might be getting blocked?

[scottwilkerson]

Does it use any other port other than http to communicate with the admin console that might be getting blocked?

No it does not.

You mentioned

but it's odd because I do get the username/password page

Is this Nagios Core or Nagios XI? Because you posted in the Core forum, but only Nagios XI has a login page