# 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:** 5

<div class="post-metadata">

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

</div>

> [@EricGT](#):
>
> The first thing I learned was that if you view the certificate with Chrome it may show invalid when in fact it is valid.

Couple notes about this:

- in the referenced situation, the browser _doesn’t actually show it as invalid_ in the address bar
- depending on OS, it may not complain about the certificate date if you look at it

---

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