cert: Proxy config missing

[thesefer]

This issue respects the following points:

• This is a bug, not a question or a setup/configuration issue.
• This issue is not already reported on Github (I've searched it).
• I use the latest release of the Monitoring Plugins (https://github.com/Linuxfabrik/monitoring-plugins/releases).
• I agree to follow Monitoring Plugins's Code of Conduct.

Which variant of the Monitoring Plugins do you use?

• .rpm/.deb package from repo.linuxfabrik.ch
• Compiled for Windows from download.linuxfabrik.ch
• Source Code from GitHub

Bug description

Previously at https://github.com/Linuxfabrik/monitoring-plugins/blob/b32d9a8a08f99d7d81e7d74a92b6118c40cd3b97/assets/icingaweb2-module-director/all-the-rest.json#L1505-L1549 the template was pointing at cmd-check-url. This changed in 136fda5 with the new certificate inspection plugin.

The tpl-service-cert now imports generic, tpl-service-cert-no-agent imports tpl-service-cert. The new template and check are missing a way to add a proxy into the play. This is important for us to check certs for an external website but not the internal certificate (same fqdn).

I never noticed until now that the check now reports the internal certificate for the external check.

Previous config preview for tpl-service-cert-no-agent on the host

    vars.cert_source = "url"
    vars.cert_url = "https://$host.address$"
    vars.criticality = "A+"
    vars.http_address = "proxy.address.net"
    vars.http_certificate = "20,10"
    vars.http_host = "$host.address$"
    vars.http_method = "CONNECT"
    vars.http_port = "5678"
    vars.http_sni = true
    vars.http_ssl = true

Steps to reproduce - Plugin call

Old call not recoverable

Steps to reproduce - Data

No response

Environment

Linux alp52 5.15.0-141-generic #151-Ubuntu SMP Sun May 18 21:35:19 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux

Plugin Version

cert: v2026080601 by Linuxfabrik GmbH, Zurich/Switzerland

Python version

No response

List of Python modules

No response

Additional Information

If not considered, using the tpl-service-url(-no-agent) is the way to go