My server has been rebooting several times because of power cuts.
I lost https because i reach the limit of certificates that caddy can pull from lest’s encrypt when the server reboots.
Why is caddy pulling news certificates instead of using the certificates that it already have in ~/Home?
How can i resolve this? I know i can use a -ca thing to pull unlimited certificates i guess but its not a solution i guess.
Hi João, what does the log/output say? (Specific error messages)
If i reboot my server mor than a few times i got because caddy is pushing news certificates from letsencrypt instead of using the existing ones.
This happens when i run my caddyfile from caddy -conf path to caddy file
https://acme-v02.api.letsencrypt.org/acme/new-order :: urn:ietf:params:acme:error:rateLimited :: Error creating new order :: too many certificates already issued for exact set of domains: mendesnas.myqnapcloud.com: see Rate Limits - Let's Encrypt, url:
CADDYPATH is consistent between starts, this can happen when Caddy can’t read existing certificates (or - perhaps it can read but can’t write to them, and the ones on disk are expired?).
I’d be looking into storage permissions as the most likely cause.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.