# How would one go about setting up discourse for tor?

**URL:** <https://meta.discourse.org/t/how-would-one-go-about-setting-up-discourse-for-tor/148639>\
**Category:** Self-hosting\
**Created:** [20 april 2020 om 17:01 UTC](https://meta.discourse.org/t/how-would-one-go-about-setting-up-discourse-for-tor/148639 "2020-04-20T17:01:04Z")\
**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:** [21 april 2020 om 20:15 UTC](https://meta.discourse.org/t/how-would-one-go-about-setting-up-discourse-for-tor/148639/4 "2020-04-21T20:15:40Z")

</div>

> [@jughead](#):
>
> The operator is harder to track down

Discourse explicitly and intentionally reaches out to arbitrary servers as part of rendering post content.

The only reason to run Discourse over Tor is to hide the identity of the participants from the site operator and/or each other. But you still need to log and and provide an email to post, so you need a custom SSO provider as well. Also remember to disable the geoip database features.

> [@jughead](#):
>
> Since the default setup doesn’t allow for a .onion address (since it doesn’t directly point back to the vps) it won’t accept the domain

This is extremely easy to overcome, just do the older install method: copy samples/standalone.yml to containers/app.yml and fill out the fields. Check the setup script for help text if you’re ever unsure what a setting means.

---

_[View the full topic](https://meta.discourse.org/t/how-would-one-go-about-setting-up-discourse-for-tor/148639)._
