Using cPanel’s IP Blocker to Stop Bad Traffic – A Practical Guide
Learn how to use cPanel’s IP Blocker to deny HTTP traffic from malicious IPs, see a concrete example, and understand the trade‑offs of this built‑in firewall feature.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Learn how to use cPanel’s IP Blocker to deny HTTP traffic from malicious IPs, see a concrete example, and understand the trade‑offs of this built‑in firewall feature.
Learn how to choose between FTP, FTPS, and SFTP in FileZilla based on security, firewall, and authentication needs, with a step‑by‑step FTPS explicit setup and validation.
How pfSense CARP, XMLRPC sync, and pfsync combine to give you a high-availability firewall pair — with a concrete two-node setup, verification steps, and the gotchas that cause split-brain.
Enable UFW on Ubuntu Server while keeping SSH accessible, with verification and rollback steps.
Step‑by‑step guide to create a Cloudflare Rate Limiting rule that shields an API endpoint from abusive traffic while preserving legitimate requests.
Step‑by‑step guide to configure pfSense HA with CARP, including prerequisites, VIP configuration, XMLRPC sync, verification, and failover recovery.
Learn how to implement a default-deny network policy on Ubuntu Server using UFW to block unauthorized access while maintaining SSH and web service connectivity.
For some reason I have no such file on my server.. root@serv:~# uname -a Linux serv 5.4.0-87-generic #98~18.04.1-Ubuntu SMP Wed Sep 22 10:45:04 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux root@serv:~# cat /proc/net/stat/nf_conntrack cat: /proc/net/stat/nf_conntrack: No such file or directory But my conntrack is definitely enabled: root@serv:~# lsmod | grep connt
Goal: Prevent Portainer from being unintentionally exposed to the public internet while still allowing administrators to manage the environment from remote locations. Constraint: Operators can either bind Portainer to 127.0.0.1 (or another private interface) and rely on host‑level firewall rules to block inbound traffic, or bind to 0.0.0.0 and place a revers
answered · 08 Oct 2025, 12:50 UTC