【发布时间】:2020-04-30 16:29:10
【问题描述】:
我有一个失败的挑战:
Waiting for http-01 challenge propagation: failed to perform self check GET request,我该如何解决这个问题,或者至少进一步诊断它?
删除质询会导致创建具有相同错误的新质询。令人惊讶的是 URL 以正确的 http 200 和令牌 (http://testabcxyz.ddns.net/.well-known/acme-challenge/8_F7kwZBcjgXPV2pq8GlxHrIcO_WJoNBtyf1hEr4lhk) 响应
什么负责启动自检?
kubectl describe challenges --all-namespaces
Name: testabcxyzingress-cert-1968456099-91847910-2604628612
Namespace: local-testing
Labels: <none>
Annotations: <none>
API Version: acme.cert-manager.io/v1alpha3
Kind: Challenge
Metadata:
Creation Timestamp: 2020-04-30T15:13:37Z
Finalizers:
finalizer.acme.cert-manager.io
Generation: 1
Owner References:
API Version: acme.cert-manager.io/v1alpha2
Block Owner Deletion: true
Controller: true
Kind: Order
Name: testabcxyzingress-cert-1968456099-91847910
UID: 93838384-6f45-42d9-a32f-3b051fad55c4
Resource Version: 1089800
Self Link: /apis/acme.cert-manager.io/v1alpha3/namespaces/local-testing/challenges/testabcxyzingress-cert-1968456099-91847910-2604628612
UID: ac318c10-85ce-4a20-b178-a307fd20a039
Spec:
Authz URL: https://acme-staging-v02.api.letsencrypt.org/acme/authz-v3/52738879
Dns Name: testabcxyz.ddns.net
Issuer Ref:
Group: cert-manager.io
Kind: ClusterIssuer
Name: letsencrypt-staging
Key: zzzzzzzzzzzzzzzzzzzzzzzzzzzzz
Solver:
http01:
Ingress:
Class: nginx
Token: zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz
Type: http-01
URL: https://acme-staging-v02.api.letsencrypt.org/acme/chall-v3/52738879/kysudg
Wildcard: false
Status:
Presented: true
Processing: true
Reason: Waiting for http-01 challenge propagation: failed to perform self check GET request 'http://testabcxyz.ddns.net/.well-known/acme-challenge/8_F7kwZBcjgXPV2pq8GlxHrIcO_WJoNBtyf1hEr4lhk': Get "http://testabcxyz.ddns.net/.well-known/acme-challenge/8_F7kwZBcjgXPV2pq8GlxHrIcO_WJoNBtyf1hEr4lhk": dial tcp 174.138.100.234:80: connect: connection timed out
State: pending
Events: <none>
<Paste>
【问题讨论】:
-
你能检查一下网络中没有东西阻止对 testabcxyz.ddns.net 的请求('dial tcp 174.138.100.234:80: connect: connection timed out')吗?
-
如前所述,当时该 URL 可访问并以 HTTP 200 响应。
-
问题似乎与此处记录的相同:github.com/jetstack/cert-manager/issues/3238