# How to block an IP range? "Screened IPs" not being blocked

**URL:** https://meta.discourse.org/t/how-to-block-an-ip-range-screened-ips-not-being-blocked/386851
**Category:** Support
**Created:** [October 27, 2025, 5:32pm UTC](https://meta.discourse.org/t/how-to-block-an-ip-range-screened-ips-not-being-blocked/386851 "2025-10-27T17:32:58Z")
**Posts on this page:** 1
**Showing post:** 20

<div class="post-metadata">

### Author: ![sb56637](https://avatars.discourse-cdn.com/v4/letter/s/ea5d25/32.png) [@sb56637](https://meta.discourse.org/u/sb56637)
#### Post date: [November 13, 2025, 2:12am UTC](https://meta.discourse.org/t/how-to-block-an-ip-range-screened-ips-not-being-blocked/386851/20 "2025-11-13T02:12:28Z")

</div>

Hi there, I would say that this issue isn’t really solvable at present via “normal” methods. The admin interface for “Screened IPs” doesn’t do what most users would probably expect, and the method that actually works involves messing around with config files inside Discourse’s Docker container, so it’s more like a dirty hack rather than a solution, at least IMHO. It would be great if this got a bit more traction:

> [@GUI for inspecting access logs and IP block lists](https://meta.discourse.org/t/gui-for-inspecting-access-logs-and-ip-block-lists/386981):
>
> This idea comes from: It’s an infrequent occurrence, but when the forum gets hit by a bot/scraper/crawler attack the admin needs to quickly identify the source’s IP address/range and mitigate it, without mucking about in a bunch of config files and arcane commands, especially not levels deep inside a Docker container with all the weird abstraction that takes place there. What I am used to from other forum platforms is an admin GUI with a simple list of the users or IPs with the highest numbe…

---

_[View the full topic](https://meta.discourse.org/t/how-to-block-an-ip-range-screened-ips-not-being-blocked/386851)._