Nagios Support Forum

I have an issue with monitoring the Website URL to know the status .Kindly your advise on this


1.(CRITICAL - Cannot make SSL connection.)

Host is reachable but the service getting ssl connection error it seems it requires SSL certificate to connect to it
Is there a way to include the certificate when calling the endpoint URL from Nagios?

2.(HTTP CRITICAL - No data received from host)
Host is reachable but we don’t receive data from the service

Hi,

In the "Website URL" configuration wizard, on the second screen, make sure the "Use SSL" box is checked and that
the port is set to 443.
Let me know the results.

Thanks

Take the URLs for both of the failing ones and run this command against them from the CLI and send us the full output:
Additionally, try adding -v to your check command for both services and then run the check and send the full output.

Please PM one of us a copy of your profile as well and let us know the service names so we can see how they are configured, you can download the profile.zip from Admin > System Profile by clicking the Download Profile button.

Hello ,

please find the required output that has requested.

Looks like your system is set up to route all HTTP traffic thru a Squid HTTP proxy running on IP 100.x.x.x:3128 (i.e. NOT the same server as the Nagios XI server), and it's the proxy server that's having problems connecting to the remote HTTP server. Specifically it's getting a 502 Bad Gateway error.

Questions:
1. Did you mean to set up your server this way?
2. Do you have shell access to the Squid server (IP is 100.x.x.x)? Can we test some things out to maybe help you get it so the Squid proxy can work? If not, can you get in touch with that server's administrator?

yes Nagios server is connected via proxy to the internet , and this is the way other URL has configured and its working fine with no issues.

Also I have checked the other URL that has same output and its showing the status of https services .

Since you have an open ticket, #862072, I'm closing this issue. Any further replies should be directed there.