# Reverse Proxy Into Discourse **URL:** \ **Category:** Self-hosting\ **Created:** [October 16, 2024, 1:44pm UTC](https://meta.discourse.org/t/reverse-proxy-into-discourse/331164 "2024-10-16T13:44:14Z")\ **Posts on this page:** 1\ **Showing post:** 1
**Author:** ![mjbergman92](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mjbergman92/32/456324_2.png) [@mjbergman92](https://meta.discourse.org/u/mjbergman92)\ **Post date:** [October 16, 2024, 1:44pm UTC](https://meta.discourse.org/t/reverse-proxy-into-discourse/331164/1 "2024-10-16T13:44:14Z")
I really hate to do something out of the ordinary here. I hate it as much as anyone else, but it’s all I know how to do and how every other self-hosted app I have is running. I have my wildcard A record pointing to an internal IP on my network which has port 80 and 443 exported by nginx proxy manager, which has my ssl certificates all setup. I have most everything on my existing network setup using docker, so nginx proxy manager is safe to use because it just uses the docker network to proxy over http. In the case of discourse, i have tried setting up [discourse.MYDOMAIN.com](http://discourse.MYDOMAIN.com) to the separate local IP address under a separate A record and got it to resolve; however, however nginx proxy manager has lets encrypt setup works and how discourse has it setup does not for internal IPs. So… I just want to reverse proxy. I am going to be attempting all sorts of nginx proxy configurations to get this to work. I am slightly concerned about man in the middle attacks, but I would like to figure out why nginx proxy manager lets encrypt config works with internal config and discourse does not. There has to be a way! (P.S. I know I am frazzle brained. Please ask specific questions and I can give clarity) --- _[View the full topic](https://meta.discourse.org/t/reverse-proxy-into-discourse/331164)._