this post was submitted on 24 Nov 2025
130 points (97.1% liked)

Selfhosted

61409 readers
332 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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

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

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

I've been dabbling with selfhosting for a bit now (home assistant and nextcloud), but it's clear that I lack a fundamental understanding of networking. For example:

  • I've got OpenWRT on my router, but no idea what I'm doing when it comes to firewall settings, DNS, DHCP, etc.
  • I've got a domain thru Porkbun, but no idea how to properly setup my DNS settings there to route to my local machine.
  • I've got NGINX running in a docker container in a VM and can get to the UI on my local network, but no idea what I'm doing wrong with my attempts at a reverse proxy.

Does anyone here have links to a good in-depth tutorial series for learning about securely selfhosting?

you are viewing a single comment's thread
view the rest of the comments
[–] phi@slrpnk.net 2 points 8 months ago* (last edited 8 months ago)

Maybe try to isolate the problems a bit and tackle one at a time. DDNS is only needed yo get to your router from the world wide web. Once you can resolve a name to your router's changing public ip address you can continue to think about port forwarding in openWRT. Once you can forward incoming traffic to a host behind your router, let's say port 80 to your nginx instance, then you can think about configuring nginx, let's say mapping to different running docker containers depending on the name in the url .... etc.