Selfhosted

57329 readers

1413 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.
No low-effort posts. This is subjective and will largely be determined by the community member reports.

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 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Am I doing this (networking) safely? (lemy.lol)

submitted 4 weeks ago by flork@lemy.lol to c/selfhosted@lemmy.world

26 comments fedilink hide all child comments

Here is my setup:

I have multiple DuckDNS domains (and subdomains) pointing to my home IP. My home router has port 80 and port 443 forwarded to Nginx Proxy Manager on my home server. Nginx Proxy Manager points to the appropriate docker container and each one is encrypted with Let's Encrypt.

Am I missing anything here or is this how I'm supposed to be doing it? Every app that has a DuckDNS url has a password in some shape or form.

you are viewing a single comment's thread
view the rest of the comments

[–] flork@lemy.lol 4 points 4 weeks ago (1 children)

Thanks I'll look into these. Quick question: how does fail2ban use port 80 if that's already used by nginx?

[–] redlemace@lemmy.world 10 points 4 weeks ago (1 children)

It does not. It does not uses ports at all. Fail2ban monitors your logfiles and activates the firewall to block IP's that matched your rules.

t.ex. You can block an IP that tried to access https:///admin. You can block an IP that used wrong credentials x times to login on an ssh port. Or block one that tried to relay via your mailserver. The duration is configurable and alternative duration can be configured for recidivists.

And yes, you can whitelist IP's to avoid locking yourself out. The possibilities are endless.

[–] flork@lemy.lol 1 points 2 weeks ago (1 children)

I see, the default docker installer for fail2ban gave me an error because "Port 80 was already in use" (by NGINX Manager).

[–] redlemace@lemmy.world 2 points 2 weeks ago* (last edited 2 weeks ago)

Fail2ban does not listen on any port for it has no user interface. No interface at all actually. It's just a process that monitors your logfiles and changes firewall rules and writes to syslog if you tell it to.

I run it on internet facing servers so I use a 'regular' install and never docker. I see no advantage for docker in this case, but one huge disadvantage: Docker changes a lot on the network side. It creates bridges, and picks IP's all by itself. I hate that. (I know you can put in a lot of effort to manage it, but no thanks keep your 'hands' of my network config thank you)