# Use Nginx Proxy Manager to manage multiple sites with Discourse

**URL:** <https://meta.discourse.org/t/use-nginx-proxy-manager-to-manage-multiple-sites-with-discourse/206344>\
**Category:** Sysadmins\
**Tags:** how-to\
**Created:** [August 17, 2021, 8:21am UTC](https://meta.discourse.org/t/use-nginx-proxy-manager-to-manage-multiple-sites-with-discourse/206344 "2021-08-17T08:21:04Z")\
**Posts on this page:** 1\
**Showing post:** 28

<div class="post-metadata">

**Author:** ![tophee](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tophee/32/73406_2.png) [@tophee](https://meta.discourse.org/u/tophee)\
**Post date:** [January 23, 2022, 7:59am UTC](https://meta.discourse.org/t/use-nginx-proxy-manager-to-manage-multiple-sites-with-discourse/206344/28 "2022-01-23T07:59:18Z")

</div>

> [@f1r4s](#):
>
> Can you give us your recommendation on using SQLite with NPM,

No, my recommendation is to use NPMs standard setup unless you know what you’re doing. That’s the reason why I’m using the standard setup.

> [@f1r4s](#):
>
> any suggestion to let step 3. working with me ?

You don’t need step 3 if you connect the discourse container via websocket.

> [@f1r4s](#):
>
> `getaddrinfo ENOTFOUND db <-- error when the mySQL in npm compose file defind as "db".`

This is because

> [@tophee](#):
>
> internal DNS resolution for service names (which the docker-compose file relies on) is only available on user created networks

> [@f1r4s](#):
>
> error connect ECONNREFUSED 172.17.0.2:3306

Are you sure that `172.17.0.2` is your db container? - In any case: you can skip this trouble by leaving NPM on its own network and connection discourse via web socket.

---

_[View the full topic](https://meta.discourse.org/t/use-nginx-proxy-manager-to-manage-multiple-sites-with-discourse/206344)._