# Certificate Expired **URL:** \ **Category:** Help\ **Created:** [April 29, 2019, 6:20am UTC](https://community.letsencrypt.org/t/certificate-expired/92330 "2019-04-29T06:20:27Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![kah\_Wee](https://avatars.discourse-cdn.com/v4/letter/k/839c29/32.png) [@kah\_Wee](https://community.letsencrypt.org/u/kah_Wee)\ **Post date:** [April 29, 2019, 6:20am UTC](https://community.letsencrypt.org/t/certificate-expired/92330/1 "2019-04-29T06:20:28Z")
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](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:yuensmarket.com.au I ran this command: [https://crt.sh/?q=yuensmarket.com.au](https://crt.sh/?q=yuensmarket.com.au) It produced this output: | crt.sh ID | Logged At ⇧ | Not Before | Not After | Issuer Name | | --- | --- | --- | --- | --- | | 1141213511 | 2019-01-24 | 2019-01-24 | 2019-04-24 | C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3 | | 1141213999 | 2019-01-24 | 2019-01-24 | 2019-04-24 | C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3 | | 930478367 | 2018-11-08 | 2018-11-08 | 2019-02-06 | C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3 | | 930477640 | 2018-11-08 | 2018-11-08 | 2019-02-06 | C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3 | | 751487530 | 2018-08-23 | 2018-08-23 | 2018-11-21 | C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3 | | 705204841 | 2018-08-23 | 2018-08-23 | 2018-11-21 | C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3 | | 743997255 | 2018-08-16 | 2018-08-16 | 2018-11-14 | C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3 | | 697590669 | 2018-08-16 | 2018-08-16 | 2018-11-14 | C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3 | | 731001612 | 2018-08-09 | 2018-08-09 | 2018-11-07 | C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3 | | 684750383 | 2018-08-09 | 2018-08-09 | 2018-11-07 | C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3 | | 723016675 | 2018-08-02 | 2018-08-02 | 2018-10-31 | C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3 | | 659942786 | 2018-08-02 | 2018-08-02 | 2018-10-31 | C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3 | | 662362043 | 2018-07-26 | 2018-07-26 | 2018-10-24 | C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3 | | 624699379 | 2018-07-26 | 2018-07-26 | 2018-10-24 | C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3 | | 636156495 | 2018-07-19 | 2018-07-19 | 2018-10-17 | C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3 | | 619421077 | 2018-07-19 | 2018-07-19 | 2018-10-17 | C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3 | | 564868683 | 2018-06-28 | 2018-06-28 | 2018-09-26 | C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3 | | 564910500 | 2018-06-28 | 2018-06-28 | 2018-09-26 | C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3 | | 395214179 | 2018-04-12 | 2018-04-12 | 2018-07-11 | C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3 | | 393493226 | 2018-04-12 | 2018-04-12 | 2018-07-11 | C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3 | | 382222589 | 2018-04-07 | 2018-04-05 | 2018-07-04 | C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3 | | 378380244 | 2018-04-05 | 2018-04-05 | 2018-07-04 | C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3 | | 371768638 | 2018-03-31 | 2018-03-29 | 2018-06-27 | C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3 | | 369937303 | 2018-03-29 | 2018-03-29 | 2018-06-27 | C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3 | | 362502715 | 2018-03-22 | 2018-03-22 | 2018-06-20 | C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3 | | 356128567 | 2018-03-15 | 2018-03-15 | 2018-06-13 | C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3 | | 350386677 | 2018-03-08 | 2018-03-08 | 2018-06-06 | C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3 | | 344900554 | 2018-03-01 | 2018-03-01 | 2018-05-30 | C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3 | | 338408628 | 2018-02-22 | 2018-02-22 | 2018-05-23 | C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3 | | 331724777 | 2018-02-15 | 2018-02-15 | 2018-05-16 | C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3 | | 325812381 | 2018-02-08 | 2018-02-08 | 2018-05-09 | C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3 | | 318582301 | 2018-02-01 | 2018-02-01 | 2018-05-02 | C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3 | | 313230534 | 2018-01-25 | 2018-01-25 | 2018-04-25 | C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3 | | 306859855 | 2018-01-18 | 2018-01-18 | 2018-04-18 | C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3 | | 300233571 | 2018-01-11 | 2018-01-11 | 2018-04-11 | C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3 | | 294989409 | 2018-01-04 | 2018-01-04 | 2018-04-04 | C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3 | | 290594903 | 2017-12-28 | 2017-12-28 | 2018-03-28 | C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3 | | 284207601 | 2017-12-21 | 2017-12-21 | 2018-03-21 | C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3 | | 278432674 | 2017-12-14 | 2017-12-14 | 2018-03-14 | C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3 | | 272908710 | 2017-12-07 | 2017-12-07 | 2018-03-07 | C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3 | | 267609015 | 2017-11-30 | 2017-11-30 | 2018-02-28 | C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3 | | 262815355 | 2017-11-23 | 2017-11-23 | 2018-02-21 | C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3 | | 256384461 | 2017-11-17 | 2017-11-17 | 2018-02-15 | C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3 | My web server is (include version): The operating system my web server runs on is (include version): My hosting provider, if applicable, is: I can login to a root shell on my machine (yes or no, or I don’t know): I dont 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): ---
**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\ **Post date:** [April 29, 2019, 6:32am UTC](https://community.letsencrypt.org/t/certificate-expired/92330/2 "2019-04-29T06:32:58Z")
Hi @kah_Wee > [@kah\_Wee](#): > > My domain is:yuensmarket.com.au yep, the certificate you use is expired ```nohighlight CN=yuensmarket.com.au 24.01.2019 24.04.2019 5 days expired www.yuensmarket.com.au, yuensmarket.com.au - 2 entries ``` Looks like you have used tls-sni-01 validation, that's not longer supported. But how did you create that certificate? What's your environment? Do you have root access or do you use a control panel? Checking your configuration that looks good ( [https://check-your-website.server-daten.de/?q=yuensmarket.com.au](https://check-your-website.server-daten.de/?q=yuensmarket.com.au) ): | Domainname | Http-Status | redirect | Sec. | G | | --- | --- | --- | --- | --- | | • [http://yuensmarket.com.au/](http://yuensmarket.com.au/) | | | | | | 52.63.155.196 | 301 | [https://yuensmarket.com.au/](https://yuensmarket.com.au/) | 0.713 | A | | | | | | | | • [http://www.yuensmarket.com.au/](http://www.yuensmarket.com.au/) | | | | | | 52.63.155.196 | 301 | [https://www.yuensmarket.com.au/](https://www.yuensmarket.com.au/) | 0.780 | A | | | | | | | | • [https://www.yuensmarket.com.au/](https://www.yuensmarket.com.au/) | | | | | | 52.63.155.196 | 301 | [https://yuensmarket.com.au/](https://yuensmarket.com.au/) | 3.873 | N | | Certificate error: RemoteCertificateChainErrors | | | | | | | | | | | | • [https://yuensmarket.com.au/](https://yuensmarket.com.au/) | | | | | | 52.63.155.196 | 200 | | 3.644 | N | | Certificate error: RemoteCertificateChainErrors | | | | | | | | | | | | • [http://yuensmarket.com.au/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de](http://yuensmarket.com.au/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de) | | | | | | 52.63.155.196 | 301 | [https://yuensmarket.com.au/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de](https://yuensmarket.com.au/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de) | 0.720 | A | | Visible Content: 301 Moved Permanently nginx/1.13.3 | | | | | | | | | | | | • [http://www.yuensmarket.com.au/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de](http://www.yuensmarket.com.au/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de) | | | | | | 52.63.155.196 | 301 | [https://www.yuensmarket.com.au/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de](https://www.yuensmarket.com.au/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de) | 0.743 | A | | Visible Content: 301 Moved Permanently nginx/1.13.3 | | | | | | | | | | | | • [https://www.yuensmarket.com.au/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de](https://www.yuensmarket.com.au/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de) | 301 | [https://yuensmarket.com.au/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de](https://yuensmarket.com.au/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de) | 3.077 | N | | Certificate error: RemoteCertificateChainErrors | | | | | | Visible Content: 301 Moved Permanently nginx/1.13.3 | | | | | | | | | | | | • [https://yuensmarket.com.au/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de](https://yuensmarket.com.au/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de) | 404 | | 3.016 | N | | Not Found | | | | | Port 80 is open, checking a not existing file in /.well-known/acme-challenge answers with a working redirect http -\> https (that's ok) and the expected http status 404 - Not Found. So http-01 validation should work in combination with Certbot. Perhaps try to update your certbot or install certbot-auto: > **[Certbot](https://certbot.eff.org/)** > > Tagline ---
**Author:** ![kah\_Wee](https://avatars.discourse-cdn.com/v4/letter/k/839c29/32.png) [@kah\_Wee](https://community.letsencrypt.org/u/kah_Wee)\ **Post date:** [April 29, 2019, 9:34pm UTC](https://community.letsencrypt.org/t/certificate-expired/92330/3 "2019-04-29T21:34:41Z")
The certificate was created and managed via Forge Lavarel by a development house and I am not trying to track down the account credential. Without the account credential, I can’t access the server in AWS via SSH. I do have root access to AWS console. Regards ---
**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\ **Post date:** [April 29, 2019, 11:03pm UTC](https://community.letsencrypt.org/t/certificate-expired/92330/4 "2019-04-29T23:03:55Z")
> [@kah\_Wee](#): > > I do have root access to AWS console. Then first read the basics about using Letsencrypt. > **[How It Works - Let's Encrypt](https://letsencrypt.org/how-it-works/)** > > The objective of Let’s Encrypt and the ACME protocol is to make it possible to set up an HTTPS server and have it automatically obtain a browser-trusted certificate, without any human intervention. This is accomplished by running a certificate... Then select a client. > **[ACME Client Implementations - Let's Encrypt](https://letsencrypt.org/docs/client-options/)** > > Last updated: Jul 22, 2023 | See all Documentation Let’s Encrypt uses the ACME protocol to verify that you control a given domain name and to issue you a certificate. To get a Let’s Encrypt certificate, you’ll need to choose a piece... If you have root access, that should be possible. Or check, if there is a Forge Lavarel integrated solution. You don't need the old account. You can create a new. ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [May 29, 2019, 11:04pm UTC](https://community.letsencrypt.org/t/certificate-expired/92330/5 "2019-05-29T23:04:01Z")
Closed on May 29, 2019, 11:04pm UTC This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.