Check Certificate expire Wizard: check_xi_service_http_cert

[jdalrymple]

Hi

Ok. No, balancer in the usual sense, is not there. Before working web server Apache work the web server Nginx.
Certificate I opened it and looked composition: CN "www.companyname.com", DNS name is the same "www.companyname.com". I was the last case - contact to support provider, where host our server. Maybe they left a clue somewhere for DNS name "www.my.companyname.com".

I'm not quite following what you're saying here, but in light of that I'll give you a simple example. I personally run a great number of web servers behind a single nginx proxy doing SSL termination.

If I browse to http://<MYIP> I get the SSL certificate for www.mysite.com which hosts my wordpress (certificate validation fails because IP != CN)
If I browse to http://gitlab.mysite.com I get the SSL certificate signed for gitlab.mysite.com which hosts my git repositories
If I browse to http://wiki.mysite.com I get the SSL certificate signed for wiki.mysite.com which hosts my wiki
If I browse to http://www.mywifessite.com I get the SSL certificate signed for www.mywifessite which hosts my wif'e's business site
And if I browse to http://www.mysite.com I get the same SSL certificate I would have gotten in the first example of just browsing to my IP

This is all handled by my nginx reverse proxy using Server Name Identification. The long story shortened is that all of the above sites point to the same server, it just hands out different certificates based upon what the request URI is. In your case I'm suggesting that you find a URI that requests the proper certificate using a web browser (IE/Firefox/Whatever) to troubleshoot the problems you're experiencing before you bother moving into setting up a Nagios check.

[RockerMan]

Yes, you're absolutely right. I "come up to horse on the wrong side" - meaning began to look for the reason in the consequence. And the source of the problem is in the wrong setting (import) certificate "www.companyname.com" company site by the provider. The problem was solved simply - I wrote a letter in support of the provider with a request to bring the answer Nagios monitoring in accordance with the data indicated on the certificate. Half an hour later the problem was resolved.

Code: Select all

SSL Certificate  OK   05-28-2015 11:18:52   2d 16h 57m 57s   1/3   OK - Certificate 'www.companyname.com' will expire on Fri 18 Dec 2015 11:59:00 PM 

I'm sorry for what took so much time you have
Thanks for help

PS. Topic can be closed