this post was submitted on 07 Feb 2026
14 points (88.9% liked)

Selfhosted

56085 readers
954 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

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
[–] redlemace@lemmy.world 11 points 9 hours ago (2 children)

My usual additions:

  1. Have the router to block portscanners
  2. fail2ban on internet facing services.
[–] non_burglar@lemmy.world 1 points 5 hours ago* (last edited 5 hours ago)
  1. Have the router to block portscanners

What do you mean by this? Closing unused ports?

[–] flork@lemy.lol 4 points 8 hours 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 8 points 8 hours ago

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.