# Problem with renewing SSL

**URL:** <https://community.letsencrypt.org/t/problem-with-renewing-ssl/58115>\
**Category:** Help\
**Created:** [March 29, 2018, 11:24pm UTC](https://community.letsencrypt.org/t/problem-with-renewing-ssl/58115 "2018-03-29T23:24:54Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![gpia](https://avatars.discourse-cdn.com/v4/letter/g/ea666f/32.png) [@gpia](https://community.letsencrypt.org/u/gpia)\
**Post date:** [March 29, 2018, 11:24pm UTC](https://community.letsencrypt.org/t/problem-with-renewing-ssl/58115/1 "2018-03-29T23:24:55Z")

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

My web server is (include version): Apache/2.4.27 (Unix)

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

My hosting provider, if applicable, is: Amazon Lightsail

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

Hello:

I renewed my certificate before the expiration. However, I noticed on the day it was to expire, the website was no longer secure. I’m wondering how to diagnose and fix the problem.

Thank you

---

<div class="post-metadata">

**Author:** ![schoen](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/schoen/32/79_2.png) [@schoen](https://community.letsencrypt.org/u/schoen)\
**Post date:** [March 29, 2018, 11:28pm UTC](https://community.letsencrypt.org/t/problem-with-renewing-ssl/58115/2 "2018-03-29T23:28:13Z")

</div>

Hi @gpia,

Renewal doesn’t change the expiration of the previous certificate. Instead, it means the issuance of a new certificate referring to the same domain names.

You’ve issued several new certificates for your domain name

[https://crt.sh/?Identity=%shoppotinsurance.com&iCAID=16418](https://crt.sh/?Identity=%25shoppotinsurance.com&iCAID=16418)

but none of the new certificates is in use on your web server. You’ll need to install a new certificate in your web server application in order to make use of it.

---

<div class="post-metadata">

**Author:** ![webprofusion](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/webprofusion/32/85310_2.png) [@webprofusion](https://community.letsencrypt.org/u/webprofusion)\
**Post date:** [March 30, 2018, 2:55am UTC](https://community.letsencrypt.org/t/problem-with-renewing-ssl/58115/3 "2018-03-30T02:55:01Z")

</div>

Maybe try just restarting your apache?

`sudo /opt/bitnami/ctlscript.sh restart apache`

You should also check the certificate file is updating by checking the time on the files:

`sudo ls -al /etc/letsencrypt/live/shoppotinsurance.com/`

I’m assuming your using the letsencrypt-auto command

---

<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:** [April 29, 2018, 2:55am UTC](https://community.letsencrypt.org/t/problem-with-renewing-ssl/58115/4 "2018-04-29T02:55:26Z")

</div>

Closed on April 29, 2018, 2:55am UTC

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