I've made my own cron using an external Bash-Skript running the renewal using post-hook and renew-hook (per domain-hook to create combined.pem) now.
The skript is running in @daily in cron.d and in my opinion (I hope so...) it should not fire up any issues now.
I'm running this command:
test -x /usr/bin/certbot & /usr/bin/certbot
renew --standalone $@
--renew-hook "cat $RENEWED_LINEAGE/privkey.pem $RENEWED_LINEAGE/cert.pem $RENEWED_LINEAGE/fullchain.pem > $RENEWED_LINEAGE/combined.pem;"
--post-hook "/usr/sbin/service haproxy restart"
getting this output of certbot now:
/usr/local/bin/certbot-renew
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Processing /etc/letsencrypt/renewal/gitlab.typoworx.de.conf
Cert not yet due for renewal
The following certs are not due for renewal yet:
/etc/letsencrypt/live/gitlab.typoworx.de/fullchain.pem (skipped)
No renewals were attempted.
No renewals attempted, so not running post-hook
I think this is fine now and should not unneccesarily generate requests anymore.