# חידוש SSL LetsEncrypt לא עובד (בגלל reverse proxy חיצוני נוסף)

**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 בספטמבר,‏ 2020,‏ 3:03pm 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:** 2

<div class="post-metadata">

### Author: ![EricGT](https://avatars.discourse-cdn.com/v4/letter/e/f1d935/32.png) [@EricGT](https://meta.discourse.org/u/EricGT)
#### Post date: [16 בספטמבר,‏ 2020,‏ 3:11pm UTC](https://meta.discourse.org/t/ssl-letsencrypt-renewal-not-working-due-to-an-extra-reverse-proxy-on-the-outside/164236/2 "2020-09-16T15:11:01Z")

</div>

I just did the same instructions 15 days ago.

```plaintext
cd /var/discourse
./launcher enter app
"/shared/letsencrypt"/acme.sh --cron --home "/shared/letsencrypt" --force
exit

```

The first thing I learned was that if you view the certificate with Chrome it may show invalid when in fact it is valid. See: [Chrome / Chromium bug: SSL certificates show incorrect (expired) dates](https://meta.discourse.org/t/chrome-chromium-bug-ssl-certificates-show-incorrect-expired-dates/163394)

I then tried

```plaintext
me@site:/var/discourse$ sudo ./launcher rebuild app

```

which did not work and finally

```plaintext
sudo reboot

```

The site was then working as expected.

* * *

While I note the step about `rebuild` I am not sure if it is needed, but it was a step I did along the way.

---

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