# Forwarding to Discourse container with nginx proxy\_pass and links from Discourse to host server

**URL:** <https://meta.discourse.org/t/forwarding-to-discourse-container-with-nginx-proxy-pass-and-links-from-discourse-to-host-server/169851>\
**Category:** Self-hosting\
**Created:** [November 11, 2020, 8:17pm UTC](https://meta.discourse.org/t/forwarding-to-discourse-container-with-nginx-proxy-pass-and-links-from-discourse-to-host-server/169851 "2020-11-11T20:17:00Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![riking](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/riking/32/170938_2.png) [@riking](https://meta.discourse.org/u/riking)\
**Post date:** [November 12, 2020, 11:01am UTC](https://meta.discourse.org/t/forwarding-to-discourse-container-with-nginx-proxy-pass-and-links-from-discourse-to-host-server/169851/4 "2020-11-12T11:01:37Z")

</div>

This is due to the Ember.JS router knowing the complete list of paths supported by the Discourse application, and the 404 page is being rendered clientside because it knows the server has no content there.

Place your files on another subdomain.

---

_[View the full topic](https://meta.discourse.org/t/forwarding-to-discourse-container-with-nginx-proxy-pass-and-links-from-discourse-to-host-server/169851)._
