-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
client: cert renewal errors in a loop until restart #28
Comments
I won't be able to look into this until Jan 6th+, but if useful, certmagic.Default.Logger = rawLogger.Named("default_fixme")
certmagic.DefaultACME.Logger = rawLogger.Named("default_acme_client_fixme")
|
Confirmed same issue at collab-cluster-dc13-2. It seems the redundant cert manager obtained lock, and bricked TCP:
Restarting daemon fixed issue, new cert got renewed correctly:
|
p2p-forge/client seems to fail to renew cert.
restarting kubo node seems to fix it eventually, but we should look into this, as people running long-lived stable servers may have a window of time where old cert expired and new one is not set up yet.
Problem description
I have test node which had cert long enough to trigger reneval.
Kubo 0.33.0-rc1 seems to detect need to refresh correctly:
[email protected]/certificates.go:159 certificate is in configured renewal window based on expiration date
but then it fails to get new one
ERROR autotls.renew [email protected]/config.go:919 could not get certificate from issuer {"identifier": "*.k51qzi5uqu5dgutdk6i1ynyzgkqngpha5xpgia3a5qqp4jsh0u4csozksxel2r.libp2p.direct", "issuer": "acme-v02.api.letsencrypt.org-directory", "error": "[*.k51qzi5uqu5dgutdk6i1ynyzgkqngpha5xpgia3a5qqp4jsh0u4csozksxel2r.libp2p.direct] solving challenges: *.k51qzi5uqu5dgutdk6i1ynyzgkqngpha5xpgia3a5qqp4jsh0u4csozksxel2r.libp2p.direct: no solvers available for remaining challenges (configured=[http-01 tls-alpn-01] offered=[dns-01] remaining=[dns-01]) (order=https://acme-v02.api.letsencrypt.org/acme/order/2028917947/338498640095) (ca=https://acme-v02.api.letsencrypt.org/directory)"}
It then fails the same way (
no solvers available for remaining challenges (configured=[http-01 tls-alpn-01] offered=[dns-01] remaining=[dns-01]
) with backoff.Restarting fixed the issue, and the node was able to get new cert.
ℹ️ For reference, full log (unfortunately was at INFO level and not DEBUG)
Initial thoughts
http-01
andtls-alpn-01
). If not, makedns-01
the default and explicitly disable other ones.no solvers available for remaining challenges (configured=[http-01 tls-alpn-01] offered=[dns-01] remaining=[dns-01]
in logs would be good way to confirm.default_acme_client_fixme
we set in Kubo, it is a smell present only when issue happens – default manager may still run and may be getting lock on the cert store, and the right one is unable to do the job)The text was updated successfully, but these errors were encountered: