Nagios Support Forum

I am very new to all this. Right now I have a nagios xi server up and running and use http://xx.x.x.x/nagiosxi/index.php?# to login but I would like to be able to use my own url blablabla.com/nagios or something like that. Any guilds or tutorials on how to do this for stupid people (well maybe for people new to this)? right now am using centos 6.8 and running the latest nagios xi version.

Hello, @joeylockie. Let's clarify something first. Nagios by default runs locally on your network unless you use VPN or port rerouting. Are you looking to add nagiosxi to your external website url? Or are you trying to change the Nagios IP address to a custom name to access it locally? In that case, I think you can only change it to your external FQDN. Unless you have an internal DNS server and you set it up to reroute xxxxx.com requests to the nagios ip address.

am trying to let people login into it from my external website www.jhdfsdfshf.com so I can show use it kind of like a demo showcase

That's a big question involving lots of different networking concepts. The tip(s) of the iceberg being routing and DNS.

I don't know of any nice neat "step-by-step" guides to do this. Any such guide would need to be modified dramatically depending a lot of different factors. At the very least, you would need to expose ports 80 and 443 publicly. Either via a proxy server or directly on the Nagios XI machine itself. Without knowing at least the network topology it's hard to say what should be done.

There is an official Nagios XI product demo available here:
http://nagiosxi.demos.nagios.com

You may also want to review some of the Nagios XI user rights to make sure whatever you expose publicly is only done so with the "read-only" context:
https://assets.nagios.com/downloads/nag ... Rights.pdf

Thanks, @mcapra!
I would only like to add that if you have an Amazon EC2 subscription, you may install Nagios XI as a cloud instance. Here's the turorial: https://assets.nagios.com/downloads/nag ... -Cloud.pdf This might be the easiest way to allow users on different networks to access your XI, without opening extra ports on your main network. But then you may still need to open ports on a target network to be able to monitor local devices. Or you may have two instances of XI - one running locally and sending a passive check results to the second one on the EC2 server.
This is a complicated question and the answer will depend on what devices and on what networks you're planning to monitor. But, if you just want a demo version of XI on your website then you'd either use the mcapra's demo link or spin up a cloud instance on EC2.