# Architecture: Use reverse proxy

**URL:** <https://forums.docker.com/t/architecture-use-reverse-proxy/103576>\
**Category:** General\
**Created:** [January 26, 2021, 3:54pm UTC](https://forums.docker.com/t/architecture-use-reverse-proxy/103576 "2021-01-26T15:54:02Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![okoestner](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/okoestner/32/51254_2.png) [@okoestner](https://forums.docker.com/u/okoestner)\
**Post date:** [May 14, 2021, 6:44pm UTC](https://forums.docker.com/t/architecture-use-reverse-proxy/103576/6 "2021-05-14T18:44:53Z")

</div>

The proxy works. But how to setup the network architecture?

> [@Network architecture behind reverse proxy](https://forums.docker.com/t/network-architecture-behind-reverse-proxy/108908):
>
> Hi! I am running a container setup for a reerse proxy configuration where one container is the nginx reverse proxy and another one is the letsencrypt container (following [https://linuxhandbook.com/nginx-reverse-proxy-docker](https://linuxhandbook.com/nginx-reverse-proxy-docker)). Behind the reverse proxy I want to host multiple LAMP stack based web applications. Question is whether all LAMP stacks should / need to be in the same network as the two containers managing the incoming traffic? From different advisories I learned that the different LA…

---

_[View the full topic](https://forums.docker.com/t/architecture-use-reverse-proxy/103576)._
