# Discourse geïnstalleerd in UNRAID Ubuntu Server VM achter NPM reverse proxy lost hostnaam niet op

**URL:** https://meta.discourse.org/t/discourse-installed-in-unraid-ubuntu-server-vm-behind-npm-reverse-proxy-not-resolving-hostname/293313
**Category:** Self-hosting
**Created:** [29 januari 2024 om 15:45 UTC](https://meta.discourse.org/t/discourse-installed-in-unraid-ubuntu-server-vm-behind-npm-reverse-proxy-not-resolving-hostname/293313 "2024-01-29T15:45:40Z")
**Posts on this page:** 1
**Showing post:** 9

<div class="post-metadata">

### Author: ![randyp](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/randyp/32/358521_2.png) [@randyp](https://meta.discourse.org/u/randyp)
#### Post date: [29 januari 2024 om 20:55 UTC](https://meta.discourse.org/t/discourse-installed-in-unraid-ubuntu-server-vm-behind-npm-reverse-proxy-not-resolving-hostname/293313/9 "2024-01-29T20:55:51Z")

</div>

> [@merefield](#):
>
> No, I would look at creating a completely bespoke docker compose (or whatever you are using for orchestration) and use a custom dockerfile for discourse

i have never done this before and sounds a little intimidating. i have no idea where i would start. i wonder if anyone has been down the path im going down before and already done and published a fix.

I wonder if doing similar to what this guy here did could isolate the containers built in reverse proxy so that i could complete an install, or resolve properly to my external reverse proxy running in its own docker container?

> [@Run other websites on the same machine as Discourse](https://meta.discourse.org/t/run-other-websites-on-the-same-machine-as-discourse/17247):
>
> @pfaffman edited this heavily 2022.02.24. Blame me if it’s broken. If you want to run other websites on the same machine as Discourse, you need to set up an extra NGINX or HAProxy proxy in front of the Docker container. NOTE: This is for advanced admins This guide assumes you already have Discourse working - if you don’t, it may be hard to tell whether or not the configuration is working. You cannot use ./discourse-setup to set up Discourse if another server is using port 80 or 443. You will…

---

_[View the full topic](https://meta.discourse.org/t/discourse-installed-in-unraid-ubuntu-server-vm-behind-npm-reverse-proxy-not-resolving-hostname/293313)._
