Nagios Support Forum

All URLs prefixed with "https://<nagiosserver>/nagiosxi/tools" and all entries in the URL field are passed URL encoded when clicked

In order for the URLs entered to work you're only allowed to reference files in the "/usr/local/nagiosxi/html/tools" path

What is the proper formatting for using external URLs as tools with this feature.

Hello Snapier3,

The tools page is created to offer quick access to utilities on your Nagios web server. You can choose between using full URL links or relative links. Regarding external links beyond your Nagios web server, you should be able to utilize full URL links aswell. Some full URL links may or may not work from my experience. Check out this documentation for more information.

To guarantee proper display of Nagios XI links on the tools page, adhere to these steps:

1) Go to any side menu on the NagiosXI webserver.
2) Right-click it, and choose "Copy link address" from the context menu.
3) Access your tool configuration and click "Add Tool".
4) Paste the copied link into the designated field and click "Save".
5) Refresh the tools page or click the tools tab again.
6) Your newly added tool should now appear on the tool's side menu. Test it to ensure it displays as expected.

Best regards,

It's currently not working as described in the docs.
XI 2024R1

The MyTools configuration is broken.

As per the docs, External URL URL Encoding of local file paths ope!

If you want to use an external URL as a tool, you must precede it with http:// or https://. This will inform the tools component that you're trying to access a website. As for accessing local files, I believe you must put them inside of your /usr/local/nagiosxi/html directory or a subdirectory of that directory as this will allow them to be accessed through http://[nagiosxi-ip/hostname]/nagiosxi

Tool Configuration
Add Link to NRDP

http://nagiosserver/NRDP <-- default Port 80, non forced SSL
In this instance XI2024R1 Server

Still Broken:
The URL encoded form value is appended to the tools URL.

Nothing that exists outside of the folder "/usr/local/nagiosxi/html/tools/" will render properly within the tools component.

URLs <-- Fail

Files on the XI instance above or below the absolute path "/usr/local/nagiosxi/html/tools/" <-- Fail
Configured Tool The Nagios Server File Struct XI Interface for Tool Validated service of static HTML --SN

Hello snapier3,

In reference to NRDP, simply input /nrdp/ into the entry field; there's no requirement for an IP address.

Concerning other external links, they should function with the full URL. However, it's crucial to note that the site owner must permit embedding for it to work. This is why Google did not work for you, as they do not allow embedding.

For instance, if you use https://chat.openai.com, it will work.

Also in reference to /usr/local/nagiosxi/html/tools/

Have you followed the initial instructions I provided? If you have, please give it a try and check if it works. You shouldn't be restricted to HTML/tools for this process.

For example, give this a try The homepage should now be accessible as a tool. Hope this makes sense and helps!

kvang wrote: ↑Thu Dec 07, 2023 4:51 pm For instance, if you use https://chat.openai.com, it will work.

Embedding foobar was a good theory but, didn't work either.
Same outcome with the URL. I have tried using absolute paths to the include shares and they don't work either.

Core of the problem is, it's appending the URL-Encoded value of the form field to the end of the base path for the component as the link to load in the new tab loaded outside XI.

For the web server on the nagios host to serve local files, they have to be under documentroot (with a subdir as desired). This is just normal web server stuff. The permissions on the local dir have to allow the web server to access the page. /usr/local/nagios has never worked for me because it isn't defined in the local web server config. /var/www/html/... has.
To open an external page, make sure the URL is valid and can be fetched w/ wget/curl from the nagios host (same for local files).

The idea is regardless, the URL has to be valid from the nagios host.