# Apache w/ SSL + Discourse: Next steps?

**URL:** <https://meta.discourse.org/t/apache-w-ssl-discourse-next-steps/158049>\
**Category:** Self-hosting\
**Created:** [July 17, 2020, 3:04pm UTC](https://meta.discourse.org/t/apache-w-ssl-discourse-next-steps/158049 "2020-07-17T15:04:47Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![neounix](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/neounix/32/215617_2.png) [@neounix](https://meta.discourse.org/u/neounix)\
**Post date:** [July 17, 2020, 4:07pm UTC](https://meta.discourse.org/t/apache-w-ssl-discourse-next-steps/158049/5 "2020-07-17T16:07:17Z")

</div>

FWIW, I have done extensive testing with both Apache2 and nginx as reverse proxies in front of Discourse in production (using unix sockets) and nginx is not “much faster” .

In this configuration, nginx is “slightly faster” and the speed diff is not noticeable to the user.

In addition, Google pagespeed tests in webmaster tools (lightspeed), averaged over time, do not show any significant differences between the two reverse proxies.

This FWIW comment is not based on theory or repeating what others have written; it is based on real world production tests.

We run all our Discourse instances behind Apache2 reverse proxies (originally they were nginx reverse proxies) because we like running many web sites (virtual hosts) on our servers where we have LAMP apps already hosted.

Anyone and everyone who want to use Apache2 as a reverse proxy instead of nginx will be just fine! This fact makes Discourse easily available to a wide base of users / hosts (Apache2 and nginx).

---

_[View the full topic](https://meta.discourse.org/t/apache-w-ssl-discourse-next-steps/158049)._