-
Bug template doesn't really apply, as this issue is about unclear/missing documentation in https://github.com/nginx-proxy/acme-companion/blob/main/docs/Standalone-certificates.md The process to remove a cert added like that is not clear from the documentation. Presumably, there is no code to automatically detect if the config file has had lines removed when the reload through |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Hi @JKHSDTV The service loop detects if certificate (wether they're standalone or not) are no longer in active use and remove the corresponding symlinks from Certificate in active use means a certificate existing in either the generated |
Beta Was this translation helpful? Give feedback.
Hi @JKHSDTV
The service loop detects if certificate (wether they're standalone or not) are no longer in active use and remove the corresponding symlinks from
/etc/nginx/certs
on every execution (including manual trigger ofsignal_le_service
).Certificate in active use means a certificate existing in either the generated
/app/letsencrypt_service_data
file or the user created/app/letsencrypt_user_data
file. Certificate not in active use are also no longer renewed.