Need help?

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

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

Could not bind to the LDAP server error in Nagios

by | Apr 7, 2021

Wondering how to fix the ‘could not bind to the LDAP server’ error in Nagios? We can help you fix it.

Here at Bobcares, we have seen several such Nagios-related issues as part of our Server Management Services for web hosts and online service providers.

Today we’ll take a look at the causes for this problem and see the fix.


When and why does ‘could not bind to the LDAP server’ error occurs

Recently, we had a customer who was trying and executing the check_ldaps plugin:

/usr/local/nagios/libexec/check_ldaps -H dc01.domain.local -b ” -p 636

As a result, he received the below error message.

Could not bind to the LDAP server

Also, he tried to enable the verbose mode -v for the plugin:

/usr/local/nagios/libexec/check_ldaps -H dc01.domain.local -b ” -p 636 -v

But it returned the below error message:

ldap_bind: Can’t contact LDAP server (-1)
additional info: TLS error -8179:Peer’s Certificate issuer is not recognized.
Could not bind to the LDAP server

Through this, we could find that the plugin did not have a CA certificate to validate the certificate. Now let’s see how to use certificate authority (CA) certificates with the check_ldaps plugin.


How to fix ‘could not bind to the LDAP server’ error

Now let’s see how our Support Engineers resolve this error for our customers.

The check_ldap plugin makes use of OpenLDAP. However, the OpenLDAP package is installed as part of the Nagios installation because the plugins have dependencies on it but it is left in a non-configured state.

So we need to create the CA certificate on the Nagios server and configure OpenLDAP to use the certificate.

We obtain the CA certificate from our CA and copy the contents of the certificate into a file on the Nagios XI server.

For that, we open an SSH session to the Nagios server.

* Create Certificate

Here we will create a certificate file called /etc/openldap/certs/windows_ca.cer and this is from a Microsoft Windows server.

So, we execute this command:

vi /etc/openldap/certs/windows_ca.cer

Then we paste the contents of our CA certificate into the SSH session.

After pasting the text, if a blank line is added after every line then we need to delete all of these blank lines. We simply press dd on keyboard to delete a blank line.

Finally, we save the changes and close the file.

* Update ldap.conf

The next step would be telling OpenLDAP to use this certificate.

So we execute the below command.

vi /etc/openldap/ldap.conf

After the file opens, we press the Down arrow until we reach the end of the file.

On a new line, we type the following:

TLS_CACERT /etc/openldap/certs/windows_ca.cer

Finally, we save the changes and close the file.

* Test Plugin

Now, the check_ldaps plugin should work:

/usr/local/nagios/libexec/check_ldaps -H dc01.domain.local -b ” -p 636

If it works, the following message is produced:

LDAP OK – 0.043 seconds response time|time=0.042861s;;;0.000000

[Need any further assistance in fixing Nagios errors? – We are here to help you]



Today, we saw the solution our Support Engineers provide a solution this Nagios problem.


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.


var google_conversion_label = "owonCMyG5nEQ0aD71QM";


Submit a Comment

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

Privacy Preference Center


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]


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


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


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.