-
Notifications
You must be signed in to change notification settings - Fork 824
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Certificates not renewed when using custom ACME Endpoint #853
Comments
Just today I had trouble renewing the certificate as well. Unfortunately, I run the acme-companion update every day, so I exceeded the maximum number of new requests, I have to wait for the log week. |
@steilerDev is the renewal date given by acme.sh in the acme-companion logs correct or not ? @hufhend this issue is about using acme-companion with a custom ACME CA, not with Let's Encrypt. |
Where/When would the date be printed in the logs? |
Those lines in the nginxproxy/acme-companion container logs: [Sat Aug 14 14:34:00 UTC 2021] Skip, Next renewal time is: Fri Sep 24 20:41:17 UTC 2021 |
@buchdag in that case: no the date reflected in the log is not correct (one example, but this is true for all domains):
As you see I set the default and max cert duration to 720hrs and it seems that the acme-companion is always a month off. |
Running
|
I'm starting to suspect that the default We used to have environment variables to configure this but I had to ditch this feature when moving to |
Changing it to 840 hours gave me the following:
Then I adjusted the time to 90 days (2160 hours), in order to match the default behaviour of letsencrypt:
This still does not match, is this expected? Otherwise I will only be able to report back in 3 months time |
Hey all, |
It looks like acme.sh just defaults to a renewal period of 60 days. This matches the timestamps I'm seeing where the "Skip, Next renewal time" is 60 days out. It also appears to match @steilerDev's logs as well. I think adding an environment variable back to configure the "--days" argument of acme.sh will allow us to resolve this issue. |
Bug description
For my internal network (where I cannot get letsencrypt certificates) I've set up a step-ca server exposing an ACME endpoint. This works flawlessly, until the certificates expire and the companion would need to refresh them. This does not happen automatically and I need to run the
force_renew
script manually (which works 100% of the time).Maybe I am missing some parameter, but could not find anything in the docs. Looking for advice on how I'll be able to automate the cert refreshing.
Thanks!
acme-companion image version
nginx-proxy's Docker configuration
Containers logs
The acme-companion logs (this is repeated hundreds of times)
Not sure if the nginx-proxy logs are of any use:
Docker host
The text was updated successfully, but these errors were encountered: