Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
I don't see any failure exactly? Can you be more elaborate? For example, answer all the questions of the questionnaire to begin with, next to more verbose messages about what's actually going on. And what kind of Docker stuff you're actually running. Currently we can only guess as we don't have anything to work with at all.
image: linuxserver/swag:1.20.0 # was linuxserver/letsencrypt
stdin_open: true # comment out to not see output
tty: true # comment out to not see output
- EXTRA_DOMAINS=labelgear.com, www.labelgear.com, decalgear.com, www.decalgear.com
- STAGING=false # set this value to true to test
Anyway, it seems that SWAG likes to live on the edge:
Here you can clearly see the SWAG renewal script which outputs the message you're seeing too waits until the certificate expires within 86400 seconds. Which is just a SINGLE day. Whereas Let's Encrypt recommends to start to try renewing 30 days (!!!) before expiry, so you have ample time to fix any issues that might have cropped up.
The file above is part of the SWAG Docker image, so I have no clue how to change that. You might want to take this up with SWAG themselves.
In any case, if all goes well, your certificate will be renewed somewhere between Jun 26 00:49:46 2023 GMT and Jun 27 00:49:46 2023 GMT.
I am not at all familiar with that setup but to me it sounds like the one-day renewal is only in emergency. It sounds like it relies on a cron job for normal renewal. Perhaps the cronjob is failing? It's worth asking SWAG about that first.
But, I certainly agree if that is the only renewal mechanism it should be improved.
I do have an entry in that log file, but it looks old. I guess I'll find out tomorrow since the cron job was scheduled to run at 2:08am. Thanks for all the great info from you and Mike, much appreciated.