# How to run Discourse in Apache vhost, not Nginx

**URL:** <https://meta.discourse.org/t/how-to-run-discourse-in-apache-vhost-not-nginx/133112>\
**Category:** Self-hosting\
**Tags:** unsupported-install\
**Created:** [November 11, 2019, 2:18pm UTC](https://meta.discourse.org/t/how-to-run-discourse-in-apache-vhost-not-nginx/133112 "2019-11-11T14:18:14Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![lucasbasquerotto](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/lucasbasquerotto/32/133376_2.png) [@lucasbasquerotto](https://meta.discourse.org/u/lucasbasquerotto)\
**Post date:** [November 12, 2019, 1:22am UTC](https://meta.discourse.org/t/how-to-run-discourse-in-apache-vhost-not-nginx/133112/11 "2019-11-12T01:22:03Z")

</div>

@ledimeo That’s what @pfaffman suggested, and what I think would be better in this case, to not break things badly in the future when new versions are released. But it seems that he already uses another nginx at the front as a reverse proxy and don’t want:

> [@maltfield](#):
>
> nginx → varnish → apache → nginx

That said, I think that proxing apache to nginx (even if it would end up with those 4 layers) would at least be more maintainable than trying to change the way discourse works in the official installation.

---

_[View the full topic](https://meta.discourse.org/t/how-to-run-discourse-in-apache-vhost-not-nginx/133112)._