Hello - I am using letsencrypt staging and getting following while getting the certificate -
error picking challenge type to use for domain ‘www.myspaceti.me’: no configured and supported challenge type found, error waiting for key to be available for domain “myspaceti.me”: context deadline exceeded
Can someone explain what does it mean and how can i get around this?
When you created this post, there were several questions, such as what command you ran, the exact output of that command, your domain name, operating system, etc.
Without the answers to those, it’s very difficult for anyone here to support you. Could you please provide that information for us?
Here are more logs from the container that is managing certificates
Warning ErrorCheckCertificate 7h (x2 over 7h) cert-manager-controller Error checking existing TLS certificate: secret “myspacetime-tls” not found
Normal PrepareCertificate 7h (x2 over 7h) cert-manager-controller Preparing certificate with issuer
Normal PresentChallenge 7h (x2 over 7h) cert-manager-controller Presenting http-01 challenge for domain myspaceti.me
Warning ErrorPrepareCertificate 7h cert-manager-controller Error preparing issuer for certificate: [error picking challenge type to use for domain ‘www.myspaceti.me’: no configured and supported challenge type found, error waiting for key to be available for domain “myspaceti.me”: context deadline exceeded]
Normal SelfCheck 7h (x2 over 7h) cert-manager-controller Performing self-check for domain myspaceti.me
This still isn’t helpful without context. Please complete the following questions as best you can:
My domain is:
I ran this command:
It produced this output:
My web server is (include version):
The operating system my web server runs on is (include version):
My hosting provider, if applicable, is:
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):
I also think it would be helpful to fill in these questions.
This problem is likely related to
Looks like they are using this K8S addon
From a quick glance it doesn’t appear to have ever supported TLS-SNI.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.