I noticed the certs are expired on my site (almost exactly 3 months since I started using caddy ). It’s been great so far.
Restarting caddy and looking in /var/log/syslog I see
Nov 29 10:28:32 greggman systemd[1]: Started Caddy HTTP/2 web server.
Nov 29 10:28:33 greggman caddy[2533]: Activating privacy features...2017/11/29 10:28:33 [WARNING] Stapling OCSP: no OCSP stapling for [www.greggman.com]: ocsp: error from server: unauthorized
which is the only error message I noticed.
Any idea what I need to do to get it to work again? I can post my Caddyfile and service.caddy if it would help but I don’t think there is anything weird in either.
Checking I only see logs since nov 22. Either than or I don’t know what happens to older logs. (I assume they get deleted). Do you really need to see something from 3 months ago?
Here’s the log from the 22nd to the 29th if you don’t mind taking a look
I see stuff about trying to get certs and getting rate limited. No idea why caddy would be asking for too many certs. Also I see where it apparently get new certs (says cert written to disk) but they messages about ignoring the new certs because there are already certs. Hmmm
My Caddyfile is a little convoluted but not that bad. Note SCHEME and PORT_URI_PART are not set (they’re only set when I’m running on my notebook to test. That way I don’t need a separate Caddyfile for just running locally without https
It did. But the rate limit effects will have to wear off naturally with time. Give it a week from the time of upgrade. For good measure you can clear out your ~/.caddy/ocsp folder, which is a cache of OCSP staples.