# Setting up Let's Encrypt for multisite

**URL:** <https://meta.discourse.org/t/setting-up-lets-encrypt-for-multisite/44980>\
**Category:** Self-hosting\
**Created:** [19 במאי,‏ 2016,‏ 5:13pm UTC](https://meta.discourse.org/t/setting-up-lets-encrypt-for-multisite/44980 "2016-05-19T17:13:47Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![shri](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/shri/32/197750_2.png) [@shri](https://meta.discourse.org/u/shri)\
**Post date:** [16 ביולי,‏ 2016,‏ 2:07am UTC](https://meta.discourse.org/t/setting-up-lets-encrypt-for-multisite/44980/11 "2016-07-16T02:07:13Z")

</div>

> [@fuerst](#):
>
> I recommend using Nginx Proxy together with the LetsEncrypt companion container for nginx-proxy. This setup allows me to run many containerized web apps at ports 80 or 443 as well as automatic certificate renewal.

@fuerst - so, let me see if I got this correct.

- You have a data container for redis / pgsql
- You have a multisite web\_only type container for your websites say [abc.com](http://abc.com), [def.com](http://def.com) and [xyz.com](http://xyz.com) with SSL and letsencrypt templates being used.

You then optionally have a VM which runs nginx\_proxy and the letsencrypt companion container and these proxy to the web\_only container?

I really don’t want to complicate my install so much. Would love to see a web\_only multisite which supports letsencrypt for the domains. I’ll look at the templates / yml file .. should not be rocket science as we do this day in and day out on nginx for php based apps, without docker.

---

_[View the full topic](https://meta.discourse.org/t/setting-up-lets-encrypt-for-multisite/44980)._