waja

@weiss assigned that to you as you assigned the origin bug to yourself. Maybe you want to have a look again when you have a timeslot.

I think I will try (the workaround) shortly, cause I need to update a buster system to bullseye (at least) but (still) need to monitor vintage systems with broken^Wold cryptography....

This is indeed not a specific problem to this container image but in general for Nextcloud. It was noted already at https://help.nextcloud.com/t/upgrade-to-nextcloud-hub-10-31-0-0-incorrect-row-format-found-in-your-database/218366 and should be applied for every affected Nextcloud...

Hi, I guess you installed the monitoring-plugins package from the Ubuntu repository?

I would recommend to report your issue via launchpad/ubuntu. As this is a distribution specific check, they might have much more knowledge how to deal with this issue. Please link...

What about https://github.com/matteocorti/check_ssl_cert instead inventing the wheel again?

Maybe it does not make sense to include such things into a [dead horse](https://github.com/monitoring-plugins/monitoring-plugins/pull/1806)? :) (Just to keep analogy.)

For me, I would consider `check_http` in a state, where we fix regressions and not adding features into it, which we drop midterm. But that's just my personal opinion.

> If not, then where's the replacement for all of its functionality? I guess you didn't found https://github.com/monitoring-plugins/monitoring-plugins/blob/master/plugins/check_curl.c yet?

puh ... not really related to the issue, but looking into https://build.opensuse.org/package/view_file/server:monitoring/monitoring-plugins/monitoring-plugins.spec?expand=1 makes me feel a bit sad, cause for me it looks like folks at suse seems to carry...