Nagios Support Forum

Hello,

I have a question that i cannot figure out from the demo version here, and maybe it is a locked feature until a full license is purchased. But I am needing to monitor a few different internal and external webapps we have and a majority of them are HTTPS based, and when I configure the site through the wizard it starts always with an "http://" if i change it to "https://" it wont check that the site is up on 443 and just checks port 80 and is getting a socket connection error. I have turned on certificate monitoring and it hasnt changed the outcome.

Thanks
Nate

I believe this is actually a bug in the check command, and not your fault - it's one of the things on our agenda to address right now.

Thank you for the reply wasnt sure if I was missing something. I will watch for an update to come out and go form there.

We have "reverified" this is the case. The certificate check does not pass a URL, so if you disable port 80 then you are unable to get an accurate check. However if you port 80 and 443 server the same content then the Wizard is capable, though it will fail to alert if the content serves is not the same any more.

Unfortunately a few of the apps we have run only on 443. Something else I have noticed and maybe it wasnt intended to do this. We have several apps that dont even run on a standard port. Some run on 4343,8080, etc etc. And if we add those into the command line for the checks it doesnt seem to function either for accurate checks.

Thanks
Nate

The Wizards are meant to reflect the most common configurations. HTTPS without HTTP being a good example of a non-common configuration.

We will sometimes opt to increase the coverage of a Wizard to accommodate, however I don't see support for non-standard ports coming any time soon. You will have to spend some time in the Core Config Manager, for example HTTPS w/o HTTP is a simple delete and then add an option to ARGx after using the wizard. For non-standard ports it's also a simple edit of the ARGx fields.

Thanks for the heads up on that.

We will be looking into the HTTP monitoring and come to a resolution as part of the projects we are currently working on.