How to check https url availability with self signed cert?

hello,

how can i check for example https://myserver/url/path for proper response (http 200 ok), but disable ssl certificate check, for example force ignoring expired or selfsigned certificate ?

“Check HTTP web service” has no appropriate option for ignoring ssl error and “Check Certificates” cannot query a url/path but only a port/cert.

i’m out of ideas.

i’m using raw edition and want to use checkmk for everything and not using uptime kuma as a additional tool ( with that i can activate an option “Ignoriere TLS-/SSL-errors from websites” for the query)

Hi @RolandKL, welcome to the forum !

Add the selfsigned certificate to the server running CMK: https://www.baeldung.com/linux/add-self-signed-certificate-trusted-list#2-debian-based-distributions

  • Glowsome
1 Like

mhh, but after adding it i still get

“The certificate’s owner does not match hostname”

when trying to connect with wget

Adding a self-signed certificate to the truststed list will not solve the ‘host-mismatch’ unfortunately.

would you be able to re-generate that self-signed with a/the correct hostname ?

to be honest, i don’t like the idea to regenerate all sort of self-signed certs just for the stupidity that a monitoring system can reach an url on that device like a user is also able to. we won’t even need to have https there, but it’s the default often now and you be redirected to https from http port.

we have dozens of devices with such certs, i would prefer if i can override that in checkmk like i can do that in uptime kuma.

until checkmk is able to do that we will need to run uptime kuma in parallel then…

For the check itself, there are still features/capabilities added, and there has been a lot of discussion about it.
Looking at suggestions made (on https://ideas.checkmk.com and status changes / features will be (or already are) added.
However this is only in the upcoming major release of CMK ( so that would be 2.4).

So until 2.4 is released your workaround with kuma will have to do i guess.

1 Like

thanks for the pointer, i found Werk #15520: check_httpv2: Added new options to HTTP monitoring and checked 15520 check_httpv2: Added new options to HTTP monitoring · Checkmk/checkmk@7a149f3 · GitHub and that looks promising

:slight_smile:

1 Like