Bobcares

WeSupport

Call Us! 1-800-383-5193
Call Us! 1-800-383-5193
Call Us! 1-800-383-5193

Need Help?

Emergency Response Time custom

Our experts have had an average response time of 11.06 minutes in March 2021 to fix urgent issues.

We will keep your servers stable, secure and fast at all times for one fixed price.

Problems Using Nagios With Proxies – How to resolve

by | Apr 24, 2021

Having Problems Using Nagios With Proxies? We can help you.

Problems can arise if proxies are not configured correctly while using with Nagios.

As part of our Server Management Services, we assist our customers with several Nagios queries.

Today, let us discuss the problems while we use Nagios with proxies and how to fix them.

 

Problems Using Nagios With Proxies

Generally, most of the problems arise because:

  • Nagios XI requires external access for package installation and updates. Package installation and updates may not work when proxies are configured incorrectly.
  • Nagios XI code makes several internal HTTP calls to the local Nagios XI server to perform. These will not work properly if we deploy a proxy that is not configured properly. It can also result in a non-functional Nagios XI installation.

 

Solutions

Initially, we need to configure the yum and wget configurations to make XI installation work with a proxy.

In addition, to update the following files, we need to access the Nagios XI server in an SSH session.

  • /etc/yum.conf
proxy=http://someproxyserver:port/ # Shouldn’t need to be quoted, remember the trailing slash
proxy_username=myname # The username we authenticate to our proxy with, if applicable
proxy_password=mypass # The password we provide to our 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 we 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

We don’t have to quote in any of these. However, if we have special characters in passwords, we need to escape them with backslashes.

Our Support Techs suggest another method as well:

  1. Prior to running any installation script, install the php-pear package manually.
  2. Set proxy for PHP Pear
    pear config-set http_proxy ‘http://example.com:8080’
  3. Then run Nagios installation scripts sequentially
  4. Before running E-importnagiosql script, unset the system proxy.

Update Check Behind A Proxy

For systems behind a proxy, update checks are known to fail.

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

To configure the proxy settings, navigate to Admin > Proxy Configuration.

[Need help with the configuration? We are available 24*7]

 

Conclusion

In short, problems can arise if we do not configure proxies correctly while using Nagios. Today, we saw effective methods our Support Techs employ in order to fix them.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF