# Using a certificate when Discourse is installed behind a reverse proxy

**URL:** https://meta.discourse.org/t/using-a-certificate-when-discourse-is-installed-behind-a-reverse-proxy/117226
**Category:** Self-hosting
**Tags:** unsupported-install
**Created:** [5월 9, 2019, 3:01오전 UTC](https://meta.discourse.org/t/using-a-certificate-when-discourse-is-installed-behind-a-reverse-proxy/117226 "2019-05-09T03:01:11Z")
**Posts on this page:** 1
**Showing post:** 22

<div class="post-metadata">

### Author: ![naupe](https://avatars.discourse-cdn.com/v4/letter/n/eb8c5e/32.png) [@naupe](https://meta.discourse.org/u/naupe)
#### Post date: [5월 17, 2019, 4:03오전 UTC](https://meta.discourse.org/t/using-a-certificate-when-discourse-is-installed-behind-a-reverse-proxy/117226/22 "2019-05-17T04:03:46Z")

</div>

> [@Stephen](#):
>
> Alternatively, you could just host Discourse in a $5 DigitalOcean VPS following the [standard install](https://meta.discourse.org/t/142537?silent=true) and be done with it. I set up stuff like this all the time and even then I know which I’d pick.

Because I have a physical Server I could install it on. I don’t want Discourse sitting on a cloud server, but instead installed on my server.

[Tried following this guide just for kicks.](https://meta.discourse.org/t/running-other-websites-on-the-same-machine-as-discourse/17247) Basically “Unable to connect to server” no matter the URL I put in, so that’s a bust. Of course, this guide seems to assume Nginx will be installed on the same machine as Discourse, whereas the two are in separate VMs.

A thought: perhaps it would be better to install Discourse on the same VM as Nginx? I really hate what it could mean for my other VMs on the Server.

---

_[View the full topic](https://meta.discourse.org/t/using-a-certificate-when-discourse-is-installed-behind-a-reverse-proxy/117226)._