Error presenting challenge: ingress.networking.k8s.io "nginx" not found

Question

I was following tutorial present at - https://www.digitalocean.com/community/tutorials/how-to-set-up-an-nginx-ingress-on-digitalocean-kubernetes-using-helm .When I try securing my ingress using Cert-Manager, I am able to create certificate but it is not working. Upon “kubectl describe certificate -o wide” I see Ready=False for the certificate and the reason/status it shows is **Issuing certificate as Secret does not contain a private key.**Looking deeper and troubleshooting, I found that “kubectl describe challenges -o wide” gives STATE=pending and REASON=Error presenting challenge: ingress.networking.k8s.io “nginx” not found .Please suggest the cause as well as solution for this issue as I am unable to get any insight from anywhere for this.Thanks!

KFSys · Answer

Heya, The error you’re encountering relates to the cert-manager challenge process for obtaining an SSL/TLS certificate from Let’s Encrypt. The message “Error presenting challenge: ingress.networking.k8s.io ‘nginx’ not found” suggests there’s an issue related to the Ingress resource in your Kubernetes cluster. Here are some steps to troubleshoot and possibly resolve the issue: Check the Ingress Controller : Make sure you’ve successfully deployed the Nginx Ingress Controller. If it’s not running or encountering errors, it could lead to such issues. Use the following command to check: kubectl get pods -n nginx-ingress Ensure all pods under the nginx-ingress namespace are running correctly. Review Ingress Resources : List your Ingress resources with: kubectl get ingress Confirm that the ‘nginx’ Ingress resource exists. If it doesn’t, it could be the root cause of the error message you’re seeing. Ensure Correct ClusterIssuer or Issuer : If you’re using the ClusterIssuer resource, make sure you’ve created it correctly. If you’re using a ClusterIssuer, it will work across all namespaces. If you’re using an Issuer, it’s namespace-specific. Use the following to list ClusterIssuers: kubectl get clusterissuers And for Issuers: kubectl get issuers --all-namespaces Ensure the configuration is correct, especially the solvers field, which should be correctly set up for the HTTP01 challenge (or DNS01, depending on your setup). Inspect Certificate and Secret : Check the Secret associated with the certificate: kubectl get secrets Ensure the Secret name matches the one you’ve set in your Certificate resource. If it exists but the certificate claims the Secret doesn’t contain a private key, you might want to delete the Secret and Certificate and recreate them. Check Logs for Cert-Manager : Dive deeper into the logs of the cert-manager pod(s) to gather more insight: kubectl logs -n cert-manager <name-of-the-cert-manager-pod> This can provide more specific information about what might be failing. Recreate Resources : In some cases, recreating the resources can help. Delete the existing Ingress, Certificates, and Secrets, and then recreate them. Make sure you have a backup or configuration-as-code to avoid losing any configurations. Version Compatibility : Ensure that the versions of cert-manager and the Nginx Ingress Controller are compatible. In some cases, upgrading or downgrading one or the other might solve compatibility issues. Lastly, remember to ensure that your domain is correctly pointing to the external IP of your Nginx Ingress Controller, and your DNS settings are correct. If the domain isn’t accessible or correctly configured, Let’s Encrypt won’t be able to verify and issue the certificate. I hope these steps help in identifying and resolving the issue!

Become a contributor for community

DigitalOcean Documentation

Resources for startups and AI-native businesses

The developer cloud

Start building today

Report this

Error presenting challenge: ingress.networking.k8s.io "nginx" not found

Related questions

How to change existing certbot/nginx to wildcard domain?

SSL Certificate not updateable

Is there any way to delete duplicate Let's Encrypt certificates from Plesk Admin?

Rebuilt a Wordpress OpenLiteSpeed + Ubuntu 24 droplet and /opt is missing

Issue with Let's Encrypt Certificate on Web App

Encrypted at rest? What are the encryption protocol and key strength used on Digital Ocean?

Best approach to migrate server from droplet to droplet with floating/reserved ip

SSL caddy with droplet

What token should I create for let's encrypt?

Easy Certificate Question

"Failed to validate nameserver records: a non DigitalOcean Name Server was found for [domainname].info domain"

easy cerbot question

Report this

Error presenting challenge: ingress.networking.k8s.io "nginx" not found

Related questions

How to change existing certbot/nginx to wildcard domain?

SSL Certificate not updateable

Is there any way to delete duplicate Let's Encrypt certificates from Plesk Admin?

Rebuilt a Wordpress OpenLiteSpeed + Ubuntu 24 droplet and /opt is missing

Issue with Let's Encrypt Certificate on Web App

Encrypted at rest? What are the encryption protocol and key strength used on Digital Ocean?

Best approach to migrate server from droplet to droplet with floating/reserved ip

SSL caddy with droplet

What token should I create for let's encrypt?

Easy Certificate Question

"Failed to validate nameserver records: a non DigitalOcean Name Server was found for [domainname].info domain"

easy cerbot question