Order stuck on PENDING

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

This morning my certificate for intelligenthost.net expired. The challenge looks like it went through, as it is no in pending. But the order seems to be stuck. My certs are created by the ClusterIssuer and my ingres. I pasted part of my ingress below.

My domain is:

intelligenthost.net

I ran this command:
This is from my ingress.yaml

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
annotations:
kubernetes.io/ingress.class: nginx
cert-manager.io/cluster-issuer: "letsencrypt"
nginx.org/client-max-body-size: "0"
nginx.ingress.kubernetes.io/proxy-body-size: "0"
\ name: ingress-pacprops
namespace: default
spec:
tls:

It produced this output:

Events:
Type Reason Age From Message


Normal Created 7m54s cert-manager-orders Created Challenge resource "tls-intelligenthost-net-dvkrq-2517195546-2985535495" for domain "intelligenthost.net"

My web server is (include version):

v1.10.0
NAME READY STATUS RESTARTS AGE
pod/cert-manager-84bc577876-nm59k 1/1 Running 0 17m
pod/cert-manager-cainjector-99d4695d7-kpwb7 1/1 Running 0 17m
pod/cert-manager-webhook-7bff7c658f-kvwnh 1/1 Running 0 17m

NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/cert-manager ClusterIP 10.245.163.80 9402/TCP 25d
service/cert-manager-webhook ClusterIP 10.245.159.49 443/TCP 25d

kubectl ClusterIssuer -o wide
NAME READY STATUS AGE
letsencrypt True The ACME account was registered with the ACME server 30m
letsencrypt-staging True The ACME account was registered with the ACME server 30m

The operating system my web server runs on is (include version):

n/a

My hosting provider, if applicable, is:

DigitalOcean

I can login to a root shell on my machine (yes or no, or I don't know):

I'm using a control panel to manage my site (no, or provide the name and version of the control panel):

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):

kubectl version
Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.0", GitCommit:"c2b5237ccd9c0f1d600d3072634ca66cefdf272f", GitTreeState:"clean", BuildDate:"2021-08-04T18:03:20Z", GoVersion:"go1.16.6", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.13", GitCommit:"a43c0904d0de10f92aa3956c74489c45e6453d6e", GitTreeState:"clean", BuildDate:"2022-08-17T18:23:45Z", GoVersion:"go1.16.15", Compiler:"gc", Platform:"linux/amd64"}

in case it is useful, here is the describe on my order that is stuck.

kubectl describe order tls-intelligenthost-net-dvkrq-2517195546
Name: tls-intelligenthost-net-dvkrq-2517195546
Namespace: default
Labels:
Annotations: cert-manager.io/certificate-name: tls-intelligenthost-net
cert-manager.io/certificate-revision: 1
cert-manager.io/private-key-secret-name: tls-intelligenthost-net-vj5tc
API Version: acme.cert-manager.io/v1
Kind: Order
Metadata:
Creation Timestamp: 2022-11-16T15:18:17Z
Generation: 1
Managed Fields:
API Version: acme.cert-manager.io/v1
Fields Type: FieldsV1
fieldsV1:
f:metadata:
f:annotations:
.:
f:cert-manager.io/certificate-name:
f:cert-manager.io/certificate-revision:
f:cert-manager.io/private-key-secret-name:
f:ownerReferences:
.:
k:{"uid":"8b3415f2-fbe5-4947-a6d7-d6805848c755"}:
f:spec:
.:
f:dnsNames:
f:issuerRef:
.:
f:group:
f:kind:
f:name:
f:request:
Manager: cert-manager-certificaterequests-issuer-acme
Operation: Update
Time: 2022-11-16T15:18:17Z
API Version: acme.cert-manager.io/v1
Fields Type: FieldsV1
fieldsV1:
f:status:
.:
f:authorizations:
f:finalizeURL:
f:state:
f:url:
Manager: cert-manager-orders
Operation: Update
Subresource: status
Time: 2022-11-16T15:18:19Z
Owner References:
API Version: cert-manager.io/v1
Block Owner Deletion: true
Controller: true
Kind: CertificateRequest
Name: tls-intelligenthost-net-dvkrq
UID: 8b3415f2-fbe5-4947-a6d7-d6805848c755
Resource Version: 182081405
UID: cdf442e9-d9c1-4189-9389-0d5d63036c64
Spec:
Dns Names:
intelligenthost.net
Issuer Ref:
Group: cert-manager.io
Kind: ClusterIssuer
Name: letsencrypt
Request: LS0tLS1CRUdJTiBDRVJUSUZJQ0FURSBSRVFVRVNULS0tLS0KTUlJQ2d6Q0NBV3NDQVFBd0FEQ0NBU0l3RFFZSktvWklodmNOQVFFQkJRQURnZ0VQQURDQ0FRb0NnZ0VCQUxYcwp0RTFxMjlDd2lmaUJmSDlpZE9HSC80a2RDV1NuZkxUcE5QQkNoS1Q2c0hlTUs1cEhaK1JURUJUdDdLcEpKNEhNCko5Rk1XRU5rcTlqTjNsOFFoK0RHKzd3Tkl5SURReEpPTW9zYTBuNVQ2WTFGK3BjR2F0SEw1bnRRNnY4NE43ZHIKRTY1am90ZWppK2cvd0Y5WlU2R3hsTTZKc0NLemxOYlNsVWc4TUVCeXpKWS9uMFNqVEhJRG9ZOThKcDkzN3Q1KwpmUFNGZ1p6bFl2VmtmQ29WVDV4TFUyRlJOK1duVXhid09LcDNsVXc0VTdyTmJpMUUwV2R2NGRlM3hmd3d5UlBCCndhWXdubXlxVEVGRDdPcHVEMHg5eHdhYjMxQXVkVjlwT05NNG52UWQ3NkZwd2dUM3BUeWhiNzZON0E2QVkrWWgKUWVkeFJyOEEweUNlY2dzSHhoTUNBd0VBQWFBK01Ed0dDU3FHU0liM0RRRUpEakV2TUMwd0hnWURWUjBSQkJjdwpGWUlUYVc1MFpXeHNhV2RsYm5Sb2IzTjBMbTVsZERBTEJnTlZIUThFQkFNQ0JhQXdEUVlKS29aSWh2Y05BUUVMCkJRQURnZ0VCQUFrSDcyUEIraWVPR1dLNC9aVjVuRDVIbTdrWWVsTkZWMWdYY2hFNnRHV2ttTG9sYmRCTXVFRmoKT0ZGbEVMYy9VTXFZdFNVU1JXZDZwcVhpTk16ZHBIR3UyZDB4TFAvZUNvaVlhOVR5L3dmZVdyTTlYYk5pdEhpOApWZ2xaNlFMK29DZU5CTG8zYnlxaU9yUUlmNUZJL0J4L1FHSFZvc1lxQTA3cy9aMEJydENhOTB2YWh5MmJ6UnRuCnpHeG9aSmdPZWFtTVhtK2pmeFJKbHVxWjFjN2dKb0lHZEhGQktYM3hyZUVKclpBUFBiOU5vc3h1TXdGTGk0V1oKZGpCQmVhV09HQVpQZlZmaWlFZHdTSlhxL1QxT3ZJOUpPTkl6M3N4Snl2VmVvYkR0Rk9ha0FVTi9FY2g5N0x2bQpscnUrL0lVQ3VyUnkrRGY3YVc2N1lyeDVQeWxsRHdVPQotLS0tLUVORCBDRVJUSUZJQ0FURSBSRVFVRVNULS0tLS0K
Status:
Authorizations:
Challenges:
Token: tHlJz7Jdbok_MjfLnnMi1Gs5N6sIx_bfg6jH_Dxcy50
Type: http-01
URL: https://acme-v02.api.letsencrypt.org/acme/chall-v3/176894105197/guz8yA
Token: tHlJz7Jdbok_MjfLnnMi1Gs5N6sIx_bfg6jH_Dxcy50
Type: dns-01
URL: https://acme-v02.api.letsencrypt.org/acme/chall-v3/176894105197/6HvO5w
Token: tHlJz7Jdbok_MjfLnnMi1Gs5N6sIx_bfg6jH_Dxcy50
Type: tls-alpn-01
URL: https://acme-v02.api.letsencrypt.org/acme/chall-v3/176894105197/P89H5A
Identifier: intelligenthost.net
Initial State: pending
URL: https://acme-v02.api.letsencrypt.org/acme/authz-v3/176894105197
Wildcard: false
Finalize URL: https://acme-v02.api.letsencrypt.org/acme/finalize/788532552/144621455757
State: pending
URL: https://acme-v02.api.letsencrypt.org/acme/order/788532552/144621455757
Events:
Type Reason Age From Message


Normal Created 15m cert-manager-orders Created Challenge resource "tls-intelligenthost-net-dvkrq-2517195546-2985535495" for domain "intelligenthost.net"

I am creating the certs manually for now. Will start all over from scratch. We can close this ticket. Thank you!!!

4 Likes

Testing and debugging are best done using the Staging Environment as the Rate Limits are much higher. Rate Limits are per week (rolling).

1 Like

Hi @jmart1, and welcome to the LE community forum :slight_smile:

Thanks for the update.
I'll mark your post as the "solution" but the topic will remain open for 30 days.
Please, do keep us posted with your progress.

5 Likes

I'm not familiar with your client or the output above, but I don't see anything that suggests any challenges were completed/triggered.

The ACME Order object starts in a PENDING state, and transitions once (i) all Authorizations are valid (READY), or (ii) any Authorization Challenge fails (INVALID).

The ACME Authorization object starts in PENDING and transitions once (i) any Challenge verifies (VALID), (ii) any Challenge fails (invalid), or the validity timeperiod expires (EXPIRED).

In the above, output it appears that Challenges and Authorizations are all PENDING, which means no Challenge was triggered. Once a Challenge is triggered, it's state transitions to PROCESSING.

Since the challenges/authorizations appear to all be PENDING, my guess is that no challenges were triggered. This is usually due to a client crashing or having a bug.

See RFC 8555: Automatic Certificate Management Environment (ACME) for more information on the state changes.

Note: these pending authorizations count against a weekly rate limit (see Rate Limits - Let's Encrypt ).

5 Likes

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.