Configuring SSL for Nagios XI - Just did it but...
Posted: Thu Jan 19, 2017 6:26 pm
Since I just set up a new Nagios XI system, and had to basically start from the ground floor and build it up, I am finding many little tweaks here and there that I needed to make in order for everything to be as close to perfect as I can get them.
I have now setup my system to always use SSL. It now expects every link I go to from the GUI to also be secure.
We use Dashboards quite a bit, and many are using the Custom URL Dashlet. Any new Custom URL dashboards added, if you are not careful, will end up using http. I would suggest to anyone who implements the SSL solution to consider making this minor change. Change the default.
Edit the dashlet and add an s to http - near line 60
In the past I had to deal with web browsers protecting me from evil dashboards until I changed this.
Just something to be aware of.
Maybe this could be added to the formal Nagios Doc. It is no show stopper, but can make things confusing for folks who are unaware of how to work around it in their browser. The browser will simply not load the page, and unless they know to look in the URL bar for the clue of how to browse unsafe pages, they will think the page is broken.
Thanks
Steve B
I have now setup my system to always use SSL. It now expects every link I go to from the GUI to also be secure.
We use Dashboards quite a bit, and many are using the Custom URL Dashlet. Any new Custom URL dashboards added, if you are not careful, will end up using http. I would suggest to anyone who implements the SSL solution to consider making this minor change. Change the default.
Edit the dashlet and add an s to http - near line 60
Code: Select all
cd /usr/local/nagiosxi/html/includes/dashlets/custom-dashlet
vi custom-dashlet.inc.php
<input type="text" name="url" id="url" value="http://">
should become
<input type="text" name="url" id="url" value="https://">
Just something to be aware of.
Maybe this could be added to the formal Nagios Doc. It is no show stopper, but can make things confusing for folks who are unaware of how to work around it in their browser. The browser will simply not load the page, and unless they know to look in the URL bar for the clue of how to browse unsafe pages, they will think the page is broken.
Thanks
Steve B