Nagios Support Forum

Thanks. I figured it was somewhere that the port was not being specified. I'm not sure if any of these fixes will truly fix it for us, because we'll be accessing it locally, customers through port forwarding, and sometimes we'll be doing it remotely through VPN. So the lack of a specific port in the URI means that proper coding needs to assume port 80 if no port is specified and add it in.

Can we open a dev ticket for this? I get why it is the way it is (as opposed to localhost) but it really should respect any port that was used (or not used) to access the original container.

That's why you may have to hard-code in ://127.0.0.1/nagioslogserver/index.php/api/backend into there or even just directly to the ES backend at http://127.0.0.1:9200/ which would be directly into the ES API which is normally how it would be connected to it if we were using standard ELK and didn't have all the Nagios overlays.

We can definitely add it to the bug fixes and get the port to be added to the ajax request.