Website still looks ssl expired after renew

Help
1

Hello everyone, I reinstall my certificates cause of expired. I’m using nginx. I successfully installed certs. But when I run this command I got this error ( on below ) . When I try to access website, It looks still using old certs.(expired one).
I see some certs in /acme-challenge folder but they’re not same as /acme-challenge/InLmiHeyocdp15LKbQenGEPufV4nPzy4hFDrm5TtujQ (in error output )

My domain is: socksunited.com

I ran this command: sudo certbot renew --dry-run

It produced this output:
aving debug log to /var/log/letsencrypt/letsencrypt.log

Processing /etc/letsencrypt/renewal/socksunited.com.conf

Cert not due for renewal, but simulating renewal for dry run
Plugins selected: Authenticator nginx, Installer nginx
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for socksunited.com
http-01 challenge for www.socksunited.com
Waiting for verification…
Challenge failed for domain socksunited.com
Challenge failed for domain www.socksunited.com
http-01 challenge for socksunited.com
http-01 challenge for www.socksunited.com
Cleaning up challenges
Attempting to renew cert (socksunited.com) from /etc/letsencrypt/renewal/socksunited.com.conf produced an unexpected error: Some challenges have failed… Skipping.
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/socksunited.com/fullchain.pem (failure)

** DRY RUN: simulating ‘certbot renew’ close to cert expiry
** (The test certificates below have not been saved.)

All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/socksunited.com/fullchain.pem (failure)
** DRY RUN: simulating ‘certbot renew’ close to cert expiry
** (The test certificates above have not been saved.)

1 renew failure(s), 0 parse failure(s)

IMPORTANT NOTES:

My web server is (include version):
nginx version: nginx/1.14.0 (Ubuntu)
The operating system my web server runs on is (include version):
Linux www 4.15.0-45-generic #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
My hosting provider, if applicable, is:
digitalocean
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):

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

1 Like
2

Hi @arc

looks like the problem doesn't longer exist.

You have two new certificates ( https://check-your-website.server-daten.de/?q=socksunited.com )

CRT-Id Issuer not before not after Domain names LE-Duplicate next LE
1360677581 CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US 2019-04-07 11:19:54 2019-07-06 11:19:54 socksunited.com, www.socksunited.com duplicate nr. 2
1360623657 CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US 2019-04-07 10:53:12 2019-07-06 10:53:12 socksunited.com, www.socksunited.com duplicate nr. 1
1088130984 CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US 2019-01-07 02:55:17 2019-04-07 01:55:17 socksunited.com, www.socksunited.com

both connections use one

CN=socksunited.com
	07.04.2019
	06.07.2019
expires in 90 days	
socksunited.com, www.socksunited.com - 2 entries

so both connections are secure.

So I don't see a problem.

Did you change the authenticator to webroot?

1 Like
3

Thanks for helping, I fixed the problem

1 Like
4

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