Check_nrpe - Failed to establish secure connection: peer did not return a certificate: 199

Service Monitoring
1

Hey!

I want to run a check_nrpe check from my Icinga2 host on a Windows Server 2016 client through the NSClient++.

When I execute a simple check_nrpe -H xxx.xxx.xxx.xxx I get the following error:

CHECK_NRPE: Error - Could not connect to xxx.xxx.xxx.xxx. Check system logs on xxx.xxx.xxx.xxx

In the logfile for the NSClient++ I get the following error:

error:c:\source\master\include\socket/connection.hpp:276: Failed to establish secure connection : peer did not return a certificate: 199

Researching made it seem pretty straight forward but apparently not for me. I also couldn’t find any troubleshooting advice online that helped me resolve the issue.

2

“I want to run a check_nrpe check from my Icinga2 host on a Windows Server
2016 client through the NSClient++.”

I really do not understand this.

NRPE (which is deprecated, although still functional) and NSClient++ are two
different ways of achieving the same goal - running an Icinga service check on
machines where you cannot install Icinga itself as an Agent.

Why would you need to use both NRPE and NSClient++ for the same check?

Antony.

3

My bad for wording it poorly, I want to use NRPE to run an NSClient++ check.