{"action":"closed","issue":{"url":"https://api.github.com/repos/mholt/caddy/issues/648","repository_url":"https://api.github.com/repos/mholt/caddy","labels_url":"https://api.github.com/repos/mholt/caddy/issues/648/labels{/name}","comments_url":"https://api.github.com/repos/mholt/caddy/issues/648/comments","events_url":"https://api.github.com/repos/mholt/caddy/issues/648/events","html_url":"https://github.com/mholt/caddy/issues/648","id":137224725,"number":648,"title":"regression: 8.2 fails on startup due to acme ratelimiting","user":{"login":"niv","id":11712,"avatar_url":"https://avatars.githubusercontent.com/u/11712?v=3","gravatar_id":"","url":"https://api.github.com/users/niv","html_url":"https://github.com/niv","followers_url":"https://api.github.com/users/niv/followers","following_url":"https://api.github.com/users/niv/following{/other_user}","gists_url":"https://api.github.com/users/niv/gists{/gist_id}","starred_url":"https://api.github.com/users/niv/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/niv/subscriptions","organizations_url":"https://api.github.com/users/niv/orgs","repos_url":"https://api.github.com/users/niv/repos","events_url":"https://api.github.com/users/niv/events{/privacy}","received_events_url":"https://api.github.com/users/niv/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2016-02-29T11:19:32Z","updated_at":"2016-02-29T15:31:07Z","closed_at":"2016-02-29T15:31:07Z","body":"Having deployed the new caddy version 8.2, I tried restarting it - and it tries to refresh all certificates in one go; the problem is, they exceed LE's rate limiting (due to amount of domains). The server fails hard at trying to refresh them all, even though there was still time on the old certs:\r\n\r\ntoo many renewal attempts; last error: acme: Error 429 - urn:acme:error:rateLimited - Error creating new cert :: Too many certificates already issued for: DOMAIN\r\n\r\nWhen I rolled back to 8.1, it tries to request the outdated certificates (not showing any error, but presumably running into the rate limit again) on startup, but runs regardless:\r\n\r\nActivating privacy features...2016/02/29 12:18:06 [INFO] Checking certificates for 22 hosts\r\n2016/02/29 12:12:27 [INFO] Certificate for DOMAIN has 14 days remaining; attempting renewal\r\n2016/02/29 12:12:27 [INFO][fwn.silm.pw] acme: Trying renewal with 340 hours remaining\r\n2016/02/29 12:12:28 [INFO][fwn.silm.pw] acme: Obtaining bundled SAN certificate\r\n2016/02/29 12:12:28 [INFO][fwn.silm.pw] acme: Could not find solver for: tls-sni-01\r\n2016/02/29 12:12:28 [INFO][fwn.silm.pw] acme: Could not find solver for: dns-01\r\n2016/02/29 12:12:28 [INFO][fwn.silm.pw] acme: Trying to solve HTTP-01\r\n2016/02/29 12:12:29 [INFO][fwn.silm.pw] Served key authentication\r\n2016/02/29 12:12:30 [INFO][fwn.silm.pw] The server validated our request\r\n2016/02/29 12:12:30 [INFO][fwn.silm.pw] acme: Validations succeeded; requesting certificates\r\n2016/02/29 12:12:40 [INFO][fwn.silm.pw] acme: Trying renewal with 340 hours remaining\r\n2016/02/29 12:12:40 [INFO][fwn.silm.pw] acme: Obtaining bundled SAN certificate\r\n2016/02/29 12:12:40 [INFO][fwn.silm.pw] acme: Could not find solver for: dns-01\r\n2016/02/29 12:12:40 [INFO][fwn.silm.pw] acme: Trying to solve HTTP-01\r\n2016/02/29 12:12:42 [INFO][fwn.silm.pw] Served key authentication\r\n2016/02/29 12:12:43 [INFO][fwn.silm.pw] The server validated our request\r\n2016/02/29 12:12:43 [INFO][fwn.silm.pw] acme: Validations succeeded; requesting certificates\r\n2016/02/29 12:12:43 [INFO] Certificate for NEXTDOMAIN has 14 days remaining; attempting renewal\r\n...\r\n<server up with partially old certs>!\r\n\r\nIs there a workaround/fix for this? Either back off on cert renewal if running into limits, or - preferably(?) - request multi-domain certs. That would probably have to be configurable globally and not on a per-vhost basis.\r\n\r\nCheers!"}}