Thank you for the info. Will this be an 2.4.0 only thing or will this be added to 2.3.0 as well?
Will be available only from Checkmk 2.4.0 on
1 Like
Being able to ignore certificates is much needed, for situations where I know the certificate on the URL is bad (self-signed or whatever), and for the purposes of check_httpv2, I only care that the website is working (search for text in body), ignoring any SSL issues.
We can use the āCheck certificatesā check when we want to validate SSL certs are ok.
Great to see this will be added, wish it would come to v2.3 as we just upgraded, now have to wait until v2.4.
2 Likes
Why this is not added to 2.3 too? I want to do the migration to the new httpv2 before I upgrade to 2.4 - so I donāt got even more problems I have to look after.
Would be nice if that also can be added in 2.3.
1 Like
You can do the migration also during 2.4. There is also a helper tool to do the migration in 2.4.
The old check_http is identical in 2.4, so you shouldnāt run into any problems.
New features are only added to new releases, so that we minimize stability issues in a current major release.
Ok, I donāt really see a stability issue to put that one more parameter. So the new check_httpv2 then only can be used with 2.4.
Please then fix the version in 2.4 because it is broken. It does not show the reason anymore and without knowing why a check does not work I cannot test all my rules.
Can you clarify? E.g. show the error message
The problem is the summary:
2.3.0p30: error sending request for url (): error trying to connect: invalid peer certificate: UnknownIssuer
2.4.x: error sending request for url
With that error I cannot work and donāt know why the check is critical.
Gotcha. I will check why this was changed.
The fix will come with the next release.
The following point is also importantā https://ideas.checkmk.com/suggestions/707161/checkhttpv2-certificate-validity-by-age-ignore-validation-against-rootca
1 Like