sec_error_expired_certificate on the clients landing page. auto-renew was supposed to prevent this!
with Certbot, run
sudo certbot renew --dry-runto see whether renewal would work right now 😂 check the timer withsystemctl list-timers | grep certbot. Common failures: port 80 blocked by a firewall, a redirect rule that breaks/.well-known/acme-challenge/, or DNS now poniting somewhere else. hope that helps :)ok so see exactly what the server prseents:
openssl s_client -connect example.com:443 -servername example.com </dev/null | openssl x509 -noout -subject -issuer -dates -ext subjectAltName... that shows the expiry date and which names the cert coevrs ;) if it differs from the files on disk, teh web server isnt using the renewed cert.
same tbh
hmmmm quick q is clients even worth bothering with or sholud i just leave it ??
nah tbh id consider switching to the DNS challenge... it doesnt need port 80 open and works for wildcard certs, though it requires API access to ur DNS provider. just my 2 cents
followed this step by step and it worked:
▶ How to Fix the NET::ERR_CERT_DATE_INVALID Error: 7 Proven Solutionsis certificate even worth bothering with or should i just leave it

@nimbus_garage384 thank u this worked!!. @amara.kowalski what did u end up doing in the end thank u thank u thank u

@nimbus_garage384 reloaded the web server and teh new certificate showed up instantly. added the deploy hook so it happens automatically from now on. thank you!
Reply to this topic
Sign in or create an account to reply.
