# Blocking Tor Users by Default

**URL:** https://meta.discourse.org/t/blocking-tor-users-by-default/240361
**Category:** Feature
**Created:** [September 29, 2022, 3:22am UTC](https://meta.discourse.org/t/blocking-tor-users-by-default/240361 "2022-09-29T03:22:36Z")
**Posts on this page:** 1
**Showing post:** 6

<div class="post-metadata">

### Author: ![Jagster](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jagster/32/192154_2.png) [@Jagster](https://meta.discourse.org/u/Jagster)
#### Post date: [September 30, 2022, 6:23am UTC](https://meta.discourse.org/t/blocking-tor-users-by-default/240361/6 "2022-09-30T06:23:46Z")

</div>

I’ve banned all known Tors at server level using iptables. Or you can use Nginx itself too, or some another reverse proxy.

Using any of those front of Discourse is really trivial task. But Docker is the buggest questionmark because it bypasses UFW/iptables of VPS in way I can’t understand because I’m just climbing up that learning curve (in my books that is the biggest security concern and less spoken)

Here is something about firewall question:

> [@Will UFW limit Discourse too?](https://meta.discourse.org/t/will-ufw-limit-discourse-too/231873):
>
> How can Discourse bypass UFW? I had enabled only port 22 so all other ports should be closed then. But a forum worked anyway. How’s that possible? DigitalOcean droplet, but that should not mean anything. And no one-click install, but official way. This is not a pure support question, but we don’t have here a catogory named Stupid basic questions by beginners wink

Of course someone can make a plugin that stops an IP. I don’t know much but I can’t understand why it would be difficult — even WordPress can do it.

But there is too issues as I see those:

- an app starts do tasks that should do at server
- an app is always late and even it stops something hammering of server has already happened

---

_[View the full topic](https://meta.discourse.org/t/blocking-tor-users-by-default/240361)._