THIS KNOWLEDGE BASE HAS BEEN ARCHIVED AND IS NO LONGER BEING UPDATED
Please visit library.nagios.com/docs for the latest and most up-to-date documentation.
Home » Categories » Products » Nagios XI » Troubleshooting » Common Problems

Nagios XI - Problems Using Nagios XI With Proxies

Overview

We do not officially support Nagios XI when you install and use proxy software that restricts traffic to or from the Nagios XI server. There are several reasons for this. First, Nagios XI requires external access for package installation and updates. Package installation and updates may not work when proxies are configured incorrectly. Additionally, the Nagios XI code makes several internal HTTP calls to the local Nagios XI server to import configuration data, apply configuration changes, process AJAX requests, etc. These functions may not work properly when you deploy a proxy if it is not configured properly, which could result in a non-functional Nagios XI installation.

 

Solutions

There are two things that need to be configured to make XI installation work with a proxy; the yum and wget configurations. Do both of these before starting anything about the installation process. You will need to access the Nagios XI server in an SSH session to update the following files.

/etc/yum.conf

proxy=http://someproxyserver:port/ # Shouldn't need to be quoted, remember the trailing slash
proxy_username=myname  # The username you authenticate to your proxy with, if applicable
proxy_password=mypass  # The password you provide to your proxy, if applicable

 

/etc/wgetrc

http_proxy=http://myname:mypass@someproxyserver:port/ # All in one string this time
https_proxy=https://myname:mypass@someproxyserver:port/ # Only required if you have a HTTPS proxy
no_proxy=localhost,127.0.0.0/8,10.0.0.0/8,172.16.0.0/12,192.168.0.0/16 # Hosts to exclude from proxying

 

Quoting is not needed (or helpful) in any of these, but if you have special characters in passwords (especially : or @) and are having problems you probably need to escape them with backslashes.

 

Solution Provided By Customer

Here is a proxy install solution reported by forum user TSCAdmin:

  1. Before running any installation script install php-pear package manually
  2. Set proxy for PHP Pear
  3. Run Nagios installation scripts sequentially
  4. Unset system proxy before running E-importnagiosql script
    pear config-set http_proxy 'http://example.com:8080'

 

Update Check Behind A Proxy

Updates checks are known to fail for systems behind a proxy.

We have a proxy component that should allow the update check to work behind most proxies.

Navigate to Admin > Proxy Configuration to configure the proxy settings.

 

Final Thoughts

For any support related questions please visit the Nagios Support Forums at:

http://support.nagios.com/forum/



Special Offer For Knowledgebase Visitors! Get a huge discount on Nagios Log Server by clicking below.

Get 60% Off Nagios Log Server!

Did you know? Nagios provides complete monitoring of: Windows, Linux, UNIX, Servers, Websites, SNMP, DHCP, DNS, Email, Storage, Files, Apache, IIS, EC2, and more!

1 (2)
Article Rating (2 Votes)
Rate this article
  • Icon PDFExport to PDF
  • Icon MS-WordExport to MS Word
Attachments Attachments
There are no attachments for this article.
Related Articles RSS Feed
Disabling Port 113 IDENT Requests
Viewed 8476 times since Tue, Mar 12, 2019
Nagios XI - Defining Global Environment Variables
Viewed 13517 times since Thu, Mar 17, 2016
API changes in Nagios XI 5.7
Viewed 5939 times since Tue, Feb 23, 2021
Pages Not Displaying Correctly
Viewed 10982 times since Mon, Jan 25, 2016
Nagios XI - STRICT_TRANS_TABLES
Viewed 11507 times since Thu, Nov 16, 2017
Nagios XI - ERROR: PostgresQL not running - exiting
Viewed 7094 times since Tue, Jan 26, 2016
NRPE - Agent and Plugin Explained
Viewed 79486 times since Fri, Jul 14, 2017
Nagios XI - HTTP 500 Error / White Screen After Login
Viewed 9074 times since Mon, Feb 29, 2016
Nagios XI - Upgrade errors - root.crontab.orig: cannot overwrite existing file
Viewed 6497 times since Tue, Jan 26, 2016
Web Browser Reports 330 Error Content Encoding
Viewed 10607 times since Tue, Mar 7, 2017