Having issues running CERTBOT Docker Container via CRONJOB but fine when ran through terminal

[Osiris]

@MikeMcQ

It has already been mentioned to run certbot more often. And, this isn't causing your primary problem. But, as you work on your final configuration please see below FAQ topic on why '0 0 ...' especially should be avoided.

FAQ - Let's Encrypt

@petercooperjr

Oh! That explains everything. Probably that's when Let's Encrypt is most under load, so that's when you're most likely to hit a case where the replication of your order isn't up-to-date.

While I agree with you both that using 0 0 should be avoided, Certbot should wait for a random amount of time before it would actually start renewing. But I'm not sure if running Certbot in Docker would mess up the whole non-interactive detection code

@eros

I'm assuming if the cert does require renewal, it will do so without requiring user input?

You're using the run subcommand in your Docker code. For renewals, you should use the certbot renew subcommand. run should only be used for getting/installing new certificates.

You can test renewing with the --dry-run option. But that might not detect spurious problems with the production environment.