Checking https urls in nagios

[admincauce]

Good morning,

I have the following problem that I don't know how to solve.

I have some checks on some applications to give me ok if you respond to a certain URL where content is published

The problem is the following:

[root @ GESNAG00 etc] $ / usr / local / nagios / libexec / nagios-plugins / check_https www.domain.es
   HTTP / 1.1 200 OK

[root @ GESNAG00 etc] $ / usr / local / nagios / libexec / nagios-plugins / check_https support.otherdomain.com

The second check does not throw anything as an exit, so I don't know why it doesn't perform the check correctly as the first. These checks are performed on internal servers that have publications in those publicly accessible domains.

That could be happening?

Best regards

[benjaminsmith]

Hello @admincare,

So it's just hanging when you run the plugin and not returning anything? Are you able run an nslookup on this domain ( post the output).

Code: Select all

nslookup support.otherdomain.com

What happens when you try using the check_http plugin instead?

Code: Select all

./check_http -H support.otherdomain.com

[admincauce]

Thank you very much for the reply!

This is the output I get if I do an nslookup from the nagios machine:

[root @ GESNAG00 engineering] $ nslookup support.otherdomain.com
Server: 10.203.228.5
Address: 10.203.228.5 # 53

Non-authoritative answer:
Name: support.otherdomain.com
Address: *. *. 97.67

When I run the check with check_nrpe, I don't get hung up. He executes it well, but returns nothing.

[root@GESNAG00 ingenieria]$ /usr/local/nagios/libexec/nagios-plugins/check_https soporte.atlantistecnologia.com
[root@GESNAG00 ingenieria]$

I have to say that it could be that I am behind a Firewall and there is something in the firewall that is stopping me these requests on that URL.

Thank you very much and we continue investigating.

[benjaminsmith]

Hello @admincauce,

I have to say that it could be that I am behind a Firewall and there is something in the firewall that is stopping me these requests on that URL. Thank you very much and we continue investigating.

Sounds good.You can run a curl command to help diagnose.

Code: Select all

curl -k -L -v  support.otherdomain.com

Let us know if you're able to resolve this.