Uneeded certificate renewal makes the service go down

[janmaroto]

Hello and thanks for such an awesome project.

Today I upgraded my compose setup, with Nginx proxy and Acme companion, via podman-compose pull.
I then restarted these two container with podman-compose up -d --force-recreate.

Unexplainably for me the Acme container started renewing the certificate (ZeroSSL) for the only running service in that machine (a custom Angular site), which ad been issued on may 15th 2025 (almost 2 mo. left).

This made my site unavailable, due to TLS not resolving a TLS certificate which lasted until the renewal finished, which took about five minutes (way more than a testing local VM I have, which is setup with LE, tough this might be something about LE vs ZeroSSL).

The question would like to ask is as follows:

Why restarting the containers as mentioned made Acme renew a certificate with plenty of time left?
When does by default Acme decide it is time to renew a certificate?

Why was Nginx, which still had a valid certificate in the certs volume not serving the site and only did once the new certificate was issues and installed?
Is this the expected behavior while the certificate is being issued?

Thanks in advanced for any feedback on this!

Cheers!