Selfhosted

39980 readers

598 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

[email protected]

Nginx in LXC/Proxmox...how to Fail2ban? (lemm.ee)

submitted 2 months ago* (last edited 2 months ago) by [email protected] to c/[email protected]

6 comments fedilink hide all child comments

Hi guys!

Back in the day I used to have a VM holding nginx and all the crap exposed...and I did set it up with fail2ban. I moved away from it, as the OS upgrade was turning messy, and rebuilt onto an LXC container. How should I use fail2ban/iptables in order to protect/harden my LXC container/server? Do the same conditions apply, or will I have any limitations/issues due to the container itself?

Thanks!

top 6 comments

sorted by: hot top controversial new old

[–] [email protected] 8 points 2 months ago (1 children)

Fail2ban and containers can be tricky, because under the hood, you'll often have container policies automatically inserting themselves above host policies in iptables. The docker documentation has a good write-up on how to solve it for their implementation

https://docs.docker.com/engine/network/packet-filtering-firewalls/

For your usecase specifically: If you're using VMs only, you could run it within any VM that is exposing traffic, but for containers you'll have to run fail2ban on the host itself. I'm not sure how LXC handles this, but I assume it's probably similar to docker.

The simplest solution would be to just put something between your hypervisor and the Internet physically (a raspberry-pi-based firewall, etc)

[–] [email protected] 5 points 1 month ago* (last edited 1 month ago) (1 children)

No, it is not like Docker. You can treat an LXC container pretty much like a VM in most instances, including firewall rules. To answer the question, you can use fail2ban just like you had done in your VM, meaning you can run it inside the LXC container, where fail2ban can change the firewall rules of that container as it sees fit.

[–] [email protected] 1 points 1 month ago (2 children)

Thanks I appreciate your reply... I have a bit of concern about an unprivileged container having firewall limitations (as I might have read in the past this was...finicky), but I'm going to give it a shot.

[–] [email protected] 3 points 1 month ago

I'm exclusively running unprivileged LXC containers and haven't had any issues regarding the firewall, neither with iptables nor nftables.

[–] [email protected] 3 points 1 month ago

I've also been running nginx in an unprivileged LXC container. I haven't used fail2ban, specifically, but crowdsec has been working without issue.

You can mostly just treat an LXC like a normal VM.

[–] [email protected] 1 points 1 month ago

Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:

Fewer Letters	More Letters
HTTP	Hypertext Transfer Protocol, the Web
LXC	Linux Containers
nginx	Popular HTTP server

[Thread #964 for this sub, first seen 10th Sep 2024, 23:45] [FAQ] [Full list] [Contact] [Source code]