When starting the container for the first time, a Let’s Encrypt certificate is successfully issued as expected.
However, on every subsequent container restart, the container attempts to issue a new certificate again instead of reusing the existing one.
According to the logs, the previously generated certificate cannot be read correctly. The logs indicate that the configuration for the domain is either invalid or corrupted. As a result, a new certificate is issued, which creates additional directories such as live/domain-00X/ each time.
This behavior occurs on every container restart until Let’s Encrypt eventually rejects further requests due to rate limits.
I have already tried explicitly setting the CERTBOT_CERT_NAME environment variable to force usage of the existing certificate, but the same issue persists.
When starting the container for the first time, a Let’s Encrypt certificate is successfully issued as expected.
However, on every subsequent container restart, the container attempts to issue a new certificate again instead of reusing the existing one.
According to the logs, the previously generated certificate cannot be read correctly. The logs indicate that the configuration for the domain is either invalid or corrupted. As a result, a new certificate is issued, which creates additional directories such as
live/domain-00X/each time.This behavior occurs on every container restart until Let’s Encrypt eventually rejects further requests due to rate limits.
I have already tried explicitly setting the
CERTBOT_CERT_NAMEenvironment variable to force usage of the existing certificate, but the same issue persists.