Hi there, I’m trying to temporarily block an abusive /16 subnet that is slamming a Discourse forum with requests. I tried this… [изображение] How can I block an IP address? are there wildcards? Support Yes, go to Admin, Logs, Screened IPs. either star wildcard…

Does Discourse see that you’re coming from one of the banned IPs if you go look at the user record from /admin/users? (If you’re behind a proxy like cloudflare, then Discourse may be seeing your proxy IP and not the IP of the user.)

Yep, when I connect to the VPN and then look at the last IP of my user account in Discourse it shows the IP that my VPN gave me. However, when I open an incognito browser window and try to register a new account then it doesn’t allow it: New registrations are not allowed from your IP address. So…

And to further complicate things, ufw / nftables on the host server apparently doesn’t block things as expected inside Docker: [изображение] Will UFW limit Discourse too? Installation This is actually a really good question and one I’m surprised nobody else has…

[изображение] sb56637: So it appears that “Screened IPs” are just for registration, not for completely disallowing access to the website. I’m not sure where we document this but it’s come up a couple times recently. “Screened IPs” blocks registrations and logins from blocked IPs that match, …

Thanks for confirming. So what would be the easiest method to deny requests from an IP or range of IPs? I found this, but it appears to be the opposite of what I need (whitelist rather than a blacklist), and messing around with the Nginx config inside the container feels like a total hack job: …

[изображение] sb56637: So what would be the easiest method to deny requests from an IP or range of IPs? I think doing it with UFW or IPTABLES . That removes stops it before Discourse gets involved. I’m always vague terrified mucking with firewalls for fear that I’ll lock myself out, but if yo…

[изображение] pfaffman: I’m always vague terrified mucking with firewalls for fear that I’ll lock myself out, but if you target just port 443 you aren’t in any danger. Exactly my fear as well. But I did enable it on the host and yet it’s still not blocking the problematic IP range. Apparently…

[изображение] sb56637: Apparently it needs a convoluted set of rules to make it apply the deny rules to the Docker containers. Oh. Yeah. That’s totally true. I ended up blocking access from my docker-based web servers to the docker-based postgres database (likely not one of your problems). H…

[изображение] pfaffman: Here’s another idea: Geo Blocking plugin Thanks, I was looking at that too, but it doesn’t appear to allow blocking numeric IP ranges, just entire countries?

[изображение] sb56637: it doesn’t appear to allow blocking numeric IP ranges, I haven’t installed it lately, but I’m pretty sure that it does [изображение] Geo Blocking plugin This can be used to completely block access to your forum for certain countries or networks, for example fraud pr…

Как заблокировать диапазон IP-адресов? "Screened IPs" не блокируются

Поддержка

tobiaseigen (Tobias Eigen) 12.Ноябрь.2025 21:57:15 19

Is this topic now solved? Is there one post @rgj or @pfaffman that I can choose as the solution? Seems you collaborated on this one!

Тема		Ответов	Просм.
Only allow Cloudflare IPs for Discourse server Self-hosting	18	3724	21.06.2023
Genuine user cannot register because of IP block Support	16	1582	01.04.2019
ISP-based anti-spam countermeasures Feature	14	2577	04.12.2025
Discourse shows server IP/localhost as user's IP Self-hosting unsupported-install	19	2115	12.07.2022
Restrict Discourse to IP range Support	3	645	13.09.2017

Как заблокировать диапазон IP-адресов? "Screened IPs" не блокируются

Связанные темы