When a created SSL expiry problem was manually closed instead of fixed through certificate renewal, the plugin checl didn't reopen a new problem if the certificate didn't get fixed.
This was due to the error event being constantly refreshed and thus didn't trigger a new problem opening.
Now the error events use a lower timeout which is only refreshed if a open problem exists. So if the problem gets manually closed the event also times out and a subsequent check will trigger a new problem.
Also, the problem and event APIs for these checks have be switched to APIv2. this means currently the used api token also needs these additional scopes (v2):
reinhard-brandstaedter
commented
2 years ago
When a created SSL expiry problem was manually closed instead of fixed through certificate renewal, the plugin checl didn't reopen a new problem if the certificate didn't get fixed. This was due to the error event being constantly refreshed and thus didn't trigger a new problem opening. Now the error events use a lower timeout which is only refreshed if a open problem exists. So if the problem gets manually closed the event also times out and a subsequent check will trigger a new problem.
Also, the problem and event APIs for these checks have be switched to APIv2. this means currently the used api token also needs these additional scopes (v2):