How to get a private key of a certificate

Help
1

Hello,

I have generated a certificate using cert-manager to secure the Nginx-ingress controller

in our Kubernetes cluster.
I hit the 'Duplicate Certificate limit' during the deployment test of my service.(I didn't know there is
a ratelimit).
Could anyone please let me know how to retrieve the certificate and private key for the already
issued certificate by letsencrypt? I will add it to Kubernetes secret to bring the service.

Thanks,
-karthi

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: www.marketsnapshot.io

I ran this command: generated certificate using Kubernetes 'issuer' manifest

It produced this output:

My web server is (include version): Nginx-ingress controller

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

My hosting provider, if applicable, is: google domain

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):

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

2

Where does your software store it?

You get it from there.

2 Likes
3

The private key is well, private. So it isn't available to the public nor to Let's Encrypt.

3 Likes
4

It was stored in kubernetes secret. Unfortunately, it was deleted as part of uninstall of my service.

5

Please let me know how can I use the already issued certificate.Should I have to wait for 1week to
request a new certificate? Thanks.

6

Then the only way to recover it is to cryptographically attack the public key.

The probability you'll do that successfully before the certificate expires is pretty much zero.

1 Like
7

Without the corresponding private key, you can't.

You indeed have to wait a week to issue the same certificate again, yes. You can read more about the rate limits in the Let's Encrypt documentation:

Please be more careful in the future. I would like to advise you to also read the other documentation pages.

2 Likes
8

ok. Thanks for your time and response.

1 Like
9

Thanks for your response and time.

1 Like
10

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