# SSL LetsEncrypt vernieuwing werkt niet (vanwege een extra reverse proxy aan de buitenkant)

**URL:** <https://meta.discourse.org/t/ssl-letsencrypt-renewal-not-working-due-to-an-extra-reverse-proxy-on-the-outside/164236>\
**Category:** Self-hosting\
**Created:** [16 september 2020 om 15:03 UTC](https://meta.discourse.org/t/ssl-letsencrypt-renewal-not-working-due-to-an-extra-reverse-proxy-on-the-outside/164236 "2020-09-16T15:03:30Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![ti0](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ti0/32/184402_2.png) [@ti0](https://meta.discourse.org/u/ti0)\
**Post date:** [16 september 2020 om 15:03 UTC](https://meta.discourse.org/t/ssl-letsencrypt-renewal-not-working-due-to-an-extra-reverse-proxy-on-the-outside/164236/1 "2020-09-16T15:03:30Z")

</div>

The cert for my discourse instance expired today, and it’s giving an error in the browser. I tried running the renewal manually as per:

> [@How to force letsencrypt cert renewal](https://meta.discourse.org/t/how-to-force-letsencrypt-cert-renewal/143223/6):
>
> You’re right, I did not check all my domains, I assumed all were concerned, but the one with Discourse can be ignored. That’s said, I’ve also figured out how to force renew: cd /var/discourse ./launcher enter app "/shared/letsencrypt"/acme.sh --cron --home "/shared/letsencrypt" --force exit I don’t know if there is a more direct way, but it worked after refreshing website cache.

It showed that the cert renewed, I can see it in the /shared/letsencrypt folder and it renewed correctly. I restarted nginx within docker. I did a rebuild of the instance, even after that it appears to be sending the old certificate.

I checked the domain with several sites, all say that the cert is expired, so it’s not just local.

Am I missing something ?

---

_[View the full topic](https://meta.discourse.org/t/ssl-letsencrypt-renewal-not-working-due-to-an-extra-reverse-proxy-on-the-outside/164236)._
