Fail2Ban
Nginx Proxy Manager
Fail2Ban | Nginx Proxy Manager | |
---|---|---|
57 | 664 | |
14,752 | 27,411 | |
2.6% | 3.8% | |
9.0 | 8.7 | |
9 days ago | 6 days ago | |
Python | JavaScript | |
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Fail2Ban
-
Fighting bots by implementing fast TCP fingerprinting with eBPF
something like https://github.com/renanqts/xdpdropper or cilium's host firewall or https://github.com/boylegu/TyrShield exist or https://github.com/ebpf-security/xdp-firewall today and implement ebpf filter based firewalling.
Of these there is a sample integration for XDPDropper to fail2ban that never got merged https://github.com/fail2ban/fail2ban/pull/3555/files -- I don't think anyone else has really worked on that junction of functionality yet.
There's also wazuh which seems to package ebpf tooling up with a ton of detection and management components, but its not a simple to deploy as fail2ban.
-
Zero Trust, One Router: Hardening Your Home Lab Like a Cyber Fortress.
Fail2Ban: Stop brute-force attacks
-
Forget IPs: using cryptography to verify bot and agent traffic
Wasn't that the argument against https, namely, that it was too costly to run [1]? I also run fail2ban [2] in my servers and I rarely even notice it's there.
I'm not saying you should sit down with the iptables manual and start going through the logs, but I can see the idea taking off if all it takes is (say) one apt-get and two config lines.
[1] https://stackoverflow.com/questions/1035283/will-it-ever-be-...
[2] https://github.com/fail2ban/fail2ban
-
DigitalOcean blocks SMTP ports 465 and 587 since last month
Not a whole lot of a source to share, sorry.
Whenever registering/subscribing to some provider, I always use a new,unique email address. If/when that provider gets their user database leaked, after some time, spam starts rushing in. At that point, I change my email address in provider's records, and old one is moved to "spamtrap" alias on my server. Over the years, quite a few has accumulated - linkedin, yahoo, you name it...
Fail2ban [0] parses mail server logs, and I have a rule there, where source IP address of anything incoming to spamtrap, is looked up in whois and logged. Then, manual awk/grep/sort contraption is run periodically.
DO's AS14061 used to be consistently in top-3 spam sources, occasionally taking #1 spot.
[0] http://www.fail2ban.org/
-
One-Click Setup for SSH Login, Password Policy, IP Ban Configuration, and Custom Admin User Creation
IP Ban: Fail2ban
-
How to install and configure Fail2ban for protecting SSH and Nginx
First you need to install Fail2ban. Before installation please see official installation guide on GitHub. Maybe something has been changed after this article published.
-
The Ultimate NixOS Homelab Guide - Flakes, Modules and Fail2Ban w/ Cloudflare
Throughout this I'll be referring to these pages: https://nixos.wiki/wiki/Fail2ban https://github.com/dani-garcia/vaultwarden/wiki/Fail2Ban-Setup https://github.com/fail2ban/fail2ban/blob/master/config/action.d/cloudflare.conf
-
OpenSSH introduces options to penalize undesirable behavior
Impatient of what exactly? fail2ban is battle tested for well over a decade. It is also an active project with regular updates: https://github.com/fail2ban/fail2ban/commits/master/
-
Looking for a way to remote in to K's of raspberry pi's...
now some things you need to think about: - cloud init - this will need to be secure so lock it down hard anything not needed an alternative OS to look at if you have the ability's is https://www.alpinelinux.org/ also as these devices are not that powerfull every extra agent / abstaction layer you add impacts performance need to look at low over head security https://www.crowdsec.net/ and https://github.com/fail2ban/fail2ban (if you call fail2ban security) - using certificates to authenticate ssh login
- Fail2Ban
Nginx Proxy Manager
-
Zero Trust, One Router: Hardening Your Home Lab Like a Cyber Fortress.
Nginx Proxy Manager β self-hosted reverse proxy with SSL built-in
-
Self-hosting like a final boss: what I actually run on my home lab (and why)
Nginx Proxy Manager: if you want that dashboard life with SSL and subdomain routing.
-
Down the Rabbit Hole of creating a Home Lab
NGINX Proxy Manager - GUI for NGINX proxy management
-
The Good Karma Kit
I've been running a tor relay relay on my static IP at my home for over a year now and haven't seen any trouble from it.
On the other hand, Nginx Proxy Manager got me blocked by brightcloud for the dumbest reason imaginable - the word "proxy" on the default "it works" page - https://github.com/NginxProxyManager/nginx-proxy-manager/dis...
-
Adventures in Homelabbing: From Cloud Obsession to Self-Hosted Shenanigans
I began to self-host a Minecraft server using Crafty Controller, an Excalidraw instance, Docmost to replace Notion, Plane to replace Jira, and Penpot to replace Figma. To be able to access them from the internet, I used Nginx Proxy Manager to set up reverse proxies with SSL. You can use Traefik or Caddy instead, but I enjoyed the ease-of-use of NPM. For a dashboard solution, I started with Homarr, but later switched to Homepage because I'm apparently incapable of making a decision and sticking with it.
-
Blocking bots in Nginx
In our case, since we use proxymanager to manage the different domains, the entry of this configuration is done in the advanced section
- Nginx Proxy Manager
-
A story on home server security
If anyone is looking for one, https://nginxproxymanager.com/
Been using it for years and itβs been solid.
-
Blackcandy: Self hosted music streaming server
Most people will use nginx-proxy [0] or Traefik [1] for front ending home labs with LetsEncrypt certs... Beyond that people will protect them with things like Tailscale [2], Cloudflare Tunnels [3] or even just mTLS [4] for protected access.
Home labbing today has a lot of amazing software and it's hard to keep up!
And as for dashboarding [5] on top of all this there are a lot of options.
[0] https://nginxproxymanager.com/
-
Zoraxy: Open-Source, All in one homelab network routing solution
https://github.com/NginxProxyManager/nginx-proxy-manager/iss...
What are some alternatives?
Suricata - Suricata is a network Intrusion Detection System, Intrusion Prevention System and Network Security Monitoring engine developed by the OISF and the Suricata community.
traefik - The Cloud Native Application Proxy
crowdsec - CrowdSec - the open-source and participative security solution offering crowdsourced protection against malicious IPs and access to the most advanced real-world CTI.
acme-dns - Limited DNS server with RESTful HTTP API to handle ACME DNS challenges easily and securely.
Snort - Snort++
uptime-kuma - A fancy self-hosted monitoring tool