# Renew worked, but web server not serving new cert **URL:** \ **Category:** Help\ **Created:** [August 7, 2018, 12:47am UTC](https://community.letsencrypt.org/t/renew-worked-but-web-server-not-serving-new-cert/68705 "2018-08-07T00:47:58Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![carloshlopez](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/carloshlopez/32/25305_2.png) [@carloshlopez](https://community.letsencrypt.org/u/carloshlopez)\ **Post date:** [August 7, 2018, 12:47am UTC](https://community.letsencrypt.org/t/renew-worked-but-web-server-not-serving-new-cert/68705/1 "2018-08-07T00:47:58Z")
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: [https://streaming2.popshoplive.com/](https://streaming2.popshoplive.com/) I ran this command: certbot renew It produced this output: It updated the cert, but I dont have the output any more… buy now it outputs this: * * * Processing /etc/letsencrypt/renewal/streaming2.popshoplive.com.conf * * * Cert not yet due for renewal * * * The following certs are not due for renewal yet: /etc/letsencrypt/live/streaming2.popshoplive.com/fullchain.pem expires on 2018-11-04 (skipped) No renewals were attempted. * * * My web server is (include version): Apache The operating system my web server runs on is (include version): EC2 Instance with Ubuntu 16 My hosting provider, if applicable, is: 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): ---
**Author:** ![stevenzhu](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/stevenzhu/32/18864_2.png) [@stevenzhu](https://community.letsencrypt.org/u/stevenzhu)\ **Post date:** [August 7, 2018, 3:16am UTC](https://community.letsencrypt.org/t/renew-worked-but-web-server-not-serving-new-cert/68705/2 "2018-08-07T03:16:36Z")
Hi, Can you try to simply restart your Apache? (The certificate is updated, however you will need to reload Apache in order for Apache to pick up the update…) Thank you ---
**Author:** ![carloshlopez](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/carloshlopez/32/25305_2.png) [@carloshlopez](https://community.letsencrypt.org/u/carloshlopez)\ **Post date:** [August 7, 2018, 2:16pm UTC](https://community.letsencrypt.org/t/renew-worked-but-web-server-not-serving-new-cert/68705/3 "2018-08-07T14:16:20Z")
Al ready done, buy still no luck. ---
**Author:** ![carloshlopez](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/carloshlopez/32/25305_2.png) [@carloshlopez](https://community.letsencrypt.org/u/carloshlopez)\ **Post date:** [August 7, 2018, 2:23pm UTC](https://community.letsencrypt.org/t/renew-worked-but-web-server-not-serving-new-cert/68705/4 "2018-08-07T14:23:37Z")
This are the files that were generated, maybe I need to recreate the tomcat.cer and truststore.jks lrwxrwxrwx 1 root root 50 Aug 6 23:56 cert.pem -\> …/…/archive/streaming2.popshoplive.com/cert2.pem lrwxrwxrwx 1 root root 51 Aug 6 23:56 chain.pem -\> …/…/archive/streaming2.popshoplive.com/chain2.pem lrwxrwxrwx 1 root root 55 Aug 6 23:56 fullchain.pem -\> …/…/archive/streaming2.popshoplive.com/fullchain2.pem -rw-r–r-- 1 root root 4450 May 7 15:40 fullchain\_and\_key.p12 -rw-r–r-- 1 root root 4107 May 7 15:41 keystore.jks lrwxrwxrwx 1 root root 53 Aug 6 23:56 privkey.pem -\> …/…/archive/streaming2.popshoplive.com/privkey2.pem -rw-r–r-- 1 root root 1570 May 7 15:41 tomcat.cer -rw-r–r-- 1 root root 1633 May 7 15:48 truststore.jks ---
**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:** [August 7, 2018, 2:23pm UTC](https://community.letsencrypt.org/t/renew-worked-but-web-server-not-serving-new-cert/68705/5 "2018-08-07T14:23:45Z")
Hi @carloshlopez > [@carloshlopez](#): > > My domain is: [https://streaming2.popshoplive.com/](https://streaming2.popshoplive.com/) > > I ran this command: certbot renew you have a new certificate, created today: [https://transparencyreport.google.com/https/certificates?cert\_search\_auth=&cert\_search\_cert=&cert\_search=include\_expired:false;include\_subdomains:false;domain:streaming2.popshoplive.com&lu=cert\_search](https://transparencyreport.google.com/https/certificates?cert_search_auth=&cert_search_cert=&cert_search=include_expired:false;include_subdomains:false;domain:streaming2.popshoplive.com&lu=cert_search) Your site uses the old certificate. What says: Certbot certificates These urls of your file you have to use in your apache configuration. ---
**Author:** ![carloshlopez](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/carloshlopez/32/25305_2.png) [@carloshlopez](https://community.letsencrypt.org/u/carloshlopez)\ **Post date:** [August 7, 2018, 2:24pm UTC](https://community.letsencrypt.org/t/renew-worked-but-web-server-not-serving-new-cert/68705/6 "2018-08-07T14:24:24Z")
> [@JuergenAuer](#): > > bot certificates * * * Found the following certs: Certificate Name: [streaming2.popshoplive.com](http://streaming2.popshoplive.com) Domains: [streaming2.popshoplive.com](http://streaming2.popshoplive.com) Expiry Date: 2018-11-04 22:56:27+00:00 (VALID: 89 days) Certificate Path: /etc/letsencrypt/live/streaming2.popshoplive.com/fullchain.pem Private Key Path: /etc/letsencrypt/live/streaming2.popshoplive.com/privkey.pem * * * ---
**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:** [August 7, 2018, 2:26pm UTC](https://community.letsencrypt.org/t/renew-worked-but-web-server-not-serving-new-cert/68705/7 "2018-08-07T14:26:00Z")
> [@carloshlopez](#): > > Certificate Path: /etc/letsencrypt/live/streaming2.popshoplive.com/fullchain.pem > Private Key Path: /etc/letsencrypt/live/streaming2.popshoplive.com/privkey.pem Then use these in your apache conf. But: > [@carloshlopez](#): > > maybe I need to recreate the tomcat.cer and truststore.jks Are there special things? ---
**Author:** ![carloshlopez](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/carloshlopez/32/25305_2.png) [@carloshlopez](https://community.letsencrypt.org/u/carloshlopez)\ **Post date:** [August 7, 2018, 2:31pm UTC](https://community.letsencrypt.org/t/renew-worked-but-web-server-not-serving-new-cert/68705/8 "2018-08-07T14:31:24Z")
It’s what was genrated in the begingn first time we installed lets encrytp cert ---
**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:** [August 7, 2018, 2:36pm UTC](https://community.letsencrypt.org/t/renew-worked-but-web-server-not-serving-new-cert/68705/9 "2018-08-07T14:36:18Z")
Now [https://streaming2.popshoplive.com/](https://streaming2.popshoplive.com/) works. What was missing? ---
**Author:** ![carloshlopez](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/carloshlopez/32/25305_2.png) [@carloshlopez](https://community.letsencrypt.org/u/carloshlopez)\ **Post date:** [August 7, 2018, 2:41pm UTC](https://community.letsencrypt.org/t/renew-worked-but-web-server-not-serving-new-cert/68705/10 "2018-08-07T14:41:51Z")
Regenerate those files did it with old commands ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [September 6, 2018, 2:45pm UTC](https://community.letsencrypt.org/t/renew-worked-but-web-server-not-serving-new-cert/68705/11 "2018-09-06T14:45:32Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.