# Discourse installato in VM Ubuntu Server UNRAID dietro proxy inverso NPM non risolve il nome host

**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 Gennaio 2024, 3:45pm 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:** 2

<div class="post-metadata">

**Author:** ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield)\
**Post date:** [29 Gennaio 2024, 4:11pm UTC](https://meta.discourse.org/t/discourse-installed-in-unraid-ubuntu-server-vm-behind-npm-reverse-proxy-not-resolving-hostname/293313/2 "2024-01-29T16:11:51Z")

</div>

> [@randyp](#):
>
> Ho seguito la seguente guida: [discourse/docs/INSTALL-cloud.md at main · discourse/discourse · GitHub](https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md#6-edit-discourse-configuration)

Questa è l’unica installazione di produzione supportata qui.

Ma non sono convinto che sia adatta alla tua situazione dato che hai già un reverse-proxy.

Potresti prendere in considerazione l’utilizzo dell’immagine base di Discourse e fare il reverse engineering della tua composizione personalizzata:

[https://hub.docker.com/r/discourse/base/](https://hub.docker.com/r/discourse/base/)

---

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