Problems to renew certificates

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. https://crt.sh/?q=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: gleich.spdns.de

I ran this command: sudo letsencrypt renew

It produced this output:

Saving debug log to /var/log/letsencrypt/letsencrypt.log

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Processing /etc/letsencrypt/renewal/gleich.spdns.de-0001.conf
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Cert not yet due for renewal

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

The following certs are not due for renewal yet:
  /etc/letsencrypt/live/gleich.spdns.de-0001/fullchain.pem expires on 2020-06-08 (skipped)
No renewals were attempted.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

My web server is (include version): Nginx

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

My hosting provider, if applicable, is: none

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

1 Like

You issued two certificates on Saturday and another one today. You don’t need to renew your certificate a fourth time. (And you are close to the duplicate certificate rate limit.)

Can you explain what’s wrong?

If I access https://gleich.spdns.de/, I get an Apache server using an expired Let’s Encrypt certificate.

If that’s the problem, you should make sure your web server – Apache or Nginx – is configured to use the correct files, and that it has been reloaded or restarted.

3 Likes

Thanks for helping. This is the solution.
I dont know why a second certificate was created, but it was the wrong one used by my nextcloud instance.

Topic can be closed.

1 Like

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