Selfhosted

59999 readers

454 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.
Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.
Don't duplicate the full text of your blog or git here. Just post the link for folks to click.
Submission headline should match the article title.
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 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

130

Tutorial series for self hosting beginners? (lemmy.world)

submitted 6 months ago* (last edited 6 months ago) by anticonnor@lemmy.world to c/selfhosted@lemmy.world

31 comments fedilink hide all child comments

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 6 months ago* (last edited 6 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.