Stall at "Created new CertificateRequest resource"

Help
1

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.

My domain is: potternet.tk

I ran this command: I am running a k3s node on a homelab. I have installed Cert-manager, and I am trying to use ACME HTTP01 challenge, and it seems that I can set up an issuer fine, but creating a certificate stops at "Created new CertificateRequest resource..."

I also don't know if I am doing my ingresses right at all, as right now I have multiple namespaces with one ingress per namespace, each pointed at a nodeport service, pointed at a deployment. Just figured I would mention that in case that is where my problem is at.

It produced this output:

My web server is (include version): not really sure, currently trying to apply ssl to OMBI and Code Server services.

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

My hosting provider, if applicable, is: Self-hosted, domain through freenom

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

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

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

2

Hi @rpotter6298 and welcome to the LE community forum :slight_smile:

Regardless of ACME client, when trying to validate via HTTP-01, you must have a working HTTP site.

curl -Ii http://potternet.tk/
HTTP/1.1 404 Not Found

curl -Ii http://www.potternet.tk/
HTTP/1.1 404 Not Found
3

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