# 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:** [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:** 27

<div class="post-metadata">

**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**Post date:** [12 בנובמבר,‏ 2019,‏ 4:33pm UTC](https://meta.discourse.org/t/how-to-run-discourse-in-apache-vhost-not-nginx/133112/27 "2019-11-12T16:33:23Z")

</div>

The likelihood that `mod_security` will increase your security is very, very, small. The people who maintain Discourse are very concerned with security, so the things that `mod_security` is supposed to fix are likely taken care of already. Further, the likelihood that if you were to get `mod_security` added to your image, it will make Discourse inoperable is significantly greater than zero. If you do install `mod_security` and find that Discourse won’t work, you’ll then be on your own to modify Discourse to work with `mod_security` and either convince the discourse maintainers that you have found a legitimate security concern or be forced to maintain your own fork going forward.

~~No good can come from this.~~ It is highly improbable that any good can come from this.

---

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