Nagios Support Forum

dwhitfield wrote:It sounds like this issue has been resolved. Is it okay if we lock this thread? Thanks for choosing the Nagios forums!

Yeah, go ahead. Thanks for the help.

Same plugin version and returns a 302 Found on the other server. At this point, I've given up on using check_http to check SSL certificates and have migrated my checks to check_ssl_certificate from the Nagios Exchange as it works.

That output from earlier was from the new server. The old server returns a 302 redirect. Also, the cert is public so shouldn't require a CA install. EDIT: So it occurred to me today to use another CentOS 7 server to test curl to rule out a curl or openssl version issue, which I did. Running curl on ...

I can't open a web browser because I don't install a GUI on my linux servers unless I absolutely need to run an X server environment. That said, the curl behavior should be enough of an analogue to using a web browser. As to what this particular example is, yes, it does land on an authentication URL...

See below. curl https://10.0.10.1:4433 --insecure -vvv * About to connect() to 10.0.10.1 port 4433 (#0) * Trying 10.0.10.1... * Connected to 10.0.10.1 (10.0.10.1) port 4433 (#0) * Initializing NSS with certpath: sql:/etc/pki/nssdb * skipping SSL peer certificate verification * SSL connection using T...

Included below. /check_http -H 10.0.10.1 -p 4433 -C 45 -v SSL initialized SSL OK - Certificate '<removed>' will expire on 2019-06-03 19:59 -0400/EDT. GET / HTTP/1.1 User-Agent: check_http/v2.2.1 (nagios-plugins 2.2.1) Connection: close Host: 10.0.10.1:4433 Accept: */* https://10.0.10.1:4433/ is 903 ...

Yes, those versions match what I have. I started suspecting openssl this morning although I'm not sure how it would cause a different http return code unless there's a bug in that version of openssl. None of the known issues stand out to me. My Fedora 26 box has OpenSSL 1.1.0g-fips 2 Nov 2017 which ...

2.2.1 on both as provided by the EPEL repo. No proxying or NATing that would affect these checks that are failing. Interestingly enough, curl's output mirrors the results of the check_http plugin. The old server returns a 302 while the new one returns a 400.

Hey everyone, New to the forums but not new nagios user here. I recently run into an odd problem that I can't figure out. I just set up a new nagios server on CentOS 7 (my old one was on CentOS6) and several of my website checks have started returning a 400 Bad Request whereas the same exact checks ...