# Certificate renew not getting done

**URL:** <https://community.letsencrypt.org/t/certificate-renew-not-getting-done/132367>\
**Category:** Help\
**Created:** [August 30, 2020, 2:19pm UTC](https://community.letsencrypt.org/t/certificate-renew-not-getting-done/132367 "2020-08-30T14:19:21Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![adityakamble](https://avatars.discourse-cdn.com/v4/letter/a/76d3ee/32.png) [@adityakamble](https://community.letsencrypt.org/u/adityakamble)\
**Post date:** [August 30, 2020, 2:19pm UTC](https://community.letsencrypt.org/t/certificate-renew-not-getting-done/132367/1 "2020-08-30T14:19:21Z")

</div>

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: [app5.juvlon.com](http://app5.juvlon.com)

I ran this command:./certbot-auto

It produced this output:

My web server is (include version):Apache/2.2.15

The operating system my web server runs on is (include version):CentOS release 6.9

My hosting provider, if applicable, is:aws

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

---

<div class="post-metadata">

**Author:** ![griffin](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/griffin/32/50204_2.png) [@griffin](https://community.letsencrypt.org/u/griffin)\
**Post date:** [August 30, 2020, 4:44pm UTC](https://community.letsencrypt.org/t/certificate-renew-not-getting-done/132367/2 "2020-08-30T16:44:18Z")

</div>

Greetings 🙂

Having read your initial post, I don’t know the issue you’re facing. I visited [app5.juvlon.com](http://app5.juvlon.com) and was redirected to [app6.juvlon.com](http://app6.juvlon.com). It looks like you have a valid Let’s Encrypt certificate that was issued on August 12 for [app6.juvlon.com](http://app6.juvlon.com) that is not yet ready for renewal. You could force a renewal, but you normally don’t want to do that unless you’re changing something (e.g. adding/removing a domain/subdomain, wanting a new private key). Since you’re redirecting [app5.juvlon.com](http://app5.juvlon.com) to [app6.juvlon.com](http://app6.juvlon.com), the Let’s Encrypt certificates you generated on August 29 and August 30 for [app5.juvlon.com](http://app5.juvlon.com) obviously aren’t going to do anything.

You can see the full history of certificates for [juvlon.com](http://juvlon.com) at [https://crt.sh/?q=juvlon.com](https://crt.sh/?q=juvlon.com).

How can we help?

---

<div class="post-metadata">

**Author:** ![adityakamble](https://avatars.discourse-cdn.com/v4/letter/a/76d3ee/32.png) [@adityakamble](https://community.letsencrypt.org/u/adityakamble)\
**Post date:** [August 30, 2020, 5:13pm UTC](https://community.letsencrypt.org/t/certificate-renew-not-getting-done/132367/3 "2020-08-30T17:13:51Z")

</div>

hello thanks for your reply  
but actually [app5.juvlon.com](http://app5.juvlon.com) is different server i had renew but not showing in [https://www.sslshopper.com/ssl-checker.html#hostname=app5.juvlon.com](https://www.sslshopper.com/ssl-checker.html#hostname=app5.juvlon.com) its not showing renew

---

<div class="post-metadata">

**Author:** ![griffin](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/griffin/32/50204_2.png) [@griffin](https://community.letsencrypt.org/u/griffin)\
**Post date:** [August 30, 2020, 5:25pm UTC](https://community.letsencrypt.org/t/certificate-renew-not-getting-done/132367/4 "2020-08-30T17:25:40Z")

</div>

At [https://crt.sh/?q=app5.juvlon.com](https://crt.sh/?q=app5.juvlon.com) I can clearly see two new certificates issued on August 29 and August 30 for [app5.juvlon.com](http://app5.juvlon.com). From the link you posted, I think the following may be misleading you:

> These results were cached from August 2, 2020, 10:26 pm PST to conserve server resources.

 ![Screenshot_20200830-112503_Samsung Internet](https://global.discourse-cdn.com/letsencrypt/original/3X/d/f/df71274ba82ccdacef5632243d55f0e65340496f.jpeg)

---

<div class="post-metadata">

**Author:** ![adityakamble](https://avatars.discourse-cdn.com/v4/letter/a/76d3ee/32.png) [@adityakamble](https://community.letsencrypt.org/u/adityakamble)\
**Post date:** [August 30, 2020, 5:30pm UTC](https://community.letsencrypt.org/t/certificate-renew-not-getting-done/132367/5 "2020-08-30T17:30:17Z")

</div>

> [@griffin](#):
>
> I can clearly see two new certificates dated August 29 an

Hello Sir

i had renewed, but its not showing renewed.

---

<div class="post-metadata">

**Author:** ![griffin](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/griffin/32/50204_2.png) [@griffin](https://community.letsencrypt.org/u/griffin)\
**Post date:** [August 30, 2020, 5:31pm UTC](https://community.letsencrypt.org/t/certificate-renew-not-getting-done/132367/6 "2020-08-30T17:31:10Z")

</div>

The link you posted ~~has~~ had really-outdated, cached results from August 2. I did you a favor and updated your results. Check your link again. 🙂

[https://www.sslshopper.com/ssl-checker.html#hostname=app5.juvlon.com](https://www.sslshopper.com/ssl-checker.html#hostname=app5.juvlon.com)

---

<div class="post-metadata">

**Author:** ![adityakamble](https://avatars.discourse-cdn.com/v4/letter/a/76d3ee/32.png) [@adityakamble](https://community.letsencrypt.org/u/adityakamble)\
**Post date:** [August 30, 2020, 5:50pm UTC](https://community.letsencrypt.org/t/certificate-renew-not-getting-done/132367/7 "2020-08-30T17:50:05Z")

</div>

Thank you sir, for your kind support, its renewed.

---

<div class="post-metadata">

**Author:** ![griffin](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/griffin/32/50204_2.png) [@griffin](https://community.letsencrypt.org/u/griffin)\
**Post date:** [August 30, 2020, 5:52pm UTC](https://community.letsencrypt.org/t/certificate-renew-not-getting-done/132367/8 "2020-08-30T17:52:59Z")

</div>

You’re very welcome. 🙂

I’m still not sure how a certificate for a redirected website will be useful, but at least it’s updating correctly.

---

<div class="post-metadata">

**Author:** ![adityakamble](https://avatars.discourse-cdn.com/v4/letter/a/76d3ee/32.png) [@adityakamble](https://community.letsencrypt.org/u/adityakamble)\
**Post date:** [August 30, 2020, 5:54pm UTC](https://community.letsencrypt.org/t/certificate-renew-not-getting-done/132367/9 "2020-08-30T17:54:21Z")

</div>

somewhere its use internally for program purpose.

---

<div class="post-metadata">

**Author:** ![griffin](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/griffin/32/50204_2.png) [@griffin](https://community.letsencrypt.org/u/griffin)\
**Post date:** [August 30, 2020, 5:55pm UTC](https://community.letsencrypt.org/t/certificate-renew-not-getting-done/132367/10 "2020-08-30T17:55:51Z")

</div>

Ah. OK. Sometimes people generate certificates for staging servers, so I could see that.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [September 29, 2020, 5:55pm UTC](https://community.letsencrypt.org/t/certificate-renew-not-getting-done/132367/11 "2020-09-29T17:55:55Z")

</div>

Closed on September 29, 2020, 5:55pm UTC

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