How to install already generated certificate

I have reached my limit for generating certificates, since i am a noob i keep having to reinstall my VPS and i created new CERT’s everytime. Now i have reached my limit and i need to install my old one’s but i don’t know how

Please help ASAP

My domain is: chossel.club
My cert: https://crt.sh/?id=1732820103

I ran this command:

It produced this output:

My web server is (include version): Apache2

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

My hosting provider, if applicable, is:

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

Hi @MeesterPlus

do you have the private key of one of these certificates?

If not, the download of the public part doesn't help.

You need the private key and the public, signed key of the certificate.

Checking your domain ( https://check-your-website.server-daten.de/?q=chossel.club#ct-logs ):

Issuer not before not after Domain names LE-Duplicate next LE
Let's Encrypt Authority X3 2019-08-02 2019-10-31 chossel.club, www.chossel.club - 2 entries duplicate nr. 5 next Letsencrypt certificate: 2019-08-05 12:51:43
Let's Encrypt Authority X3 2019-08-01 2019-10-30 chossel.club, www.chossel.club - 2 entries duplicate nr. 4
Let's Encrypt Authority X3 2019-07-29 2019-10-27 chossel.club, www.chossel.club - 2 entries duplicate nr. 3
Let's Encrypt Authority X3 2019-07-29 2019-10-27 chossel.club, www.chossel.club - 2 entries duplicate nr. 2
Let's Encrypt Authority X3 2019-07-29 2019-10-27 chossel.club, www.chossel.club - 2 entries duplicate nr. 1

5 identical certificates.

You can wait - next Letsencrypt certificate: 2019-08-05 12:51:43.

Or you can add a third subdomain (test or blog ...), then it's a new set of domain names. But first you need a dns A record with that subdomain and a working port 80 vHost.

3 Likes

is the private key randomly generated? if then i on’t have a single one x0

A key is always a key pair - public part and private part. So you need the correct private key that works with one public key.

Maybe easier if you wait - 2019-08-05 - next Monday.

1 Like

Unless your VPS PRNG isn’t seeded properly by the host and/or by subsequent latency events (hope not!), Certbot will succeed in choosing a completely random, unpredictable private key every time it’s run (unless you use the --reuse-key option on a certificate that you preserve). By design, there is no way to guess or recover this key if it’s deleted; the only copies are on your VPS.

3 Likes

Is it possible to generate a new CERT for my domain on my main pc since it’s a different ip? and then use it on my vps? or is the limit also connected to domain?

i really need my https certificate today since i want to publish tomorrow, is there any other way?

As written: Create one certificate with an additional subdomain.

With --manual certonly and --preferred-challenges dns - that should always work, then you don't need a running webserver.

Check

then

https://certbot.eff.org/docs/using.html

1 Like

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