Man I’m lame.

Used to be {env}-function##

Now it’s {env}-{vlanlocation}-function##

VLAN location such as DMZ, Infra, Jump for jump boxes, IOTSec or IOTInsec, Etc

I wouldn’t say you’re doing it wrong, but a reverse proxy allows you to not only have a specific domain to use and multiple backends, etc… but it also can translate to not needing to have a port open for every single service you run on the backend.

RP’s can certianly be a load balancer, but usually for home lab / selfhosted purposes, we don’t need a load balancer.

I use both WireGuard and OpenVPN to vpn into my home network.

However, it doesn’t matter whether you use a domain or just up… if you get blocked from accessing either / both … you’re screwed. 🤷🏼‍♂️

You are looking for a disaster recovery plan. I believe you are going down the right path, but it’s something that will take time.

I backup important files to my local NAS or directly store them on the local NAS.

This NAS then backs up to an off site cloud backup provider BackBlaze B2 storage.

Finally, I have a virtual machine that has all the same directories mounted and backs up to a different cloud provider.

It’s not quite 3-2-1… but it works.

I only backup important files. I do not do full system backups for my windows clients. I do technically backup full Linux vms from within Proxmox to my NAS…but that’s because I’m lazy and didn’t write a backup script to back up specific files and such. The idea of being able to pull a full system image quickly from a cloud provider will bite you in the ass.

In theory, when backing up containers, you want to backup the configurations, data, and the databases… but you shouldn’t worry about backing up the container image. That can usually be pulled when necessary. I don’t store any of my docker container data in volumes… I use the folder mapping from host to directory in docker container… so I can just backup directories on the host instead of trying to figure out the best way to backup a randomly named docker volume. This way I know what I’m backing up for sure.

Any questions, just ask!

Somehow, I have never seen this list… and easily over half of those projects I’ve never heard of but could add some great functionality to my home. Thanks for posting it!

I’ll pitch in here… so website dns (porkbun) is configured to point to your home in, great!

2 things need to happen.

1. Your router needs to expose ports 80 and/or 443 for HTTP and HTTPS access. If you are only doing HTTPS then 80 isn’t really necessary. These ports need forwarded to a reverse proxy, such as NGINX or Apache.
2. You need to have a reverse proxy setup that can translate the domain name that is being sent to a local IP address:port. You should be able to find some relatively simple/easy reverse proxy configuration generators online to help you get that setup. You’ll want to setup SSL certificates while you’re at this too. Look up “nginx certbot lets encrypt” and that should get you pointed in the right direction.

Once those are done, in theory, you should be able to access your website outside of your home network using your domain name.

I’ve just started to delve into Wazuh… but I’m super new to vulnerability management on a home lab level. I don’t do it for work so 🤷🏼‍♂️

Anyways, best suggestion is to keep all your containers, vms, and hosts updated best you can to remediate vulnerabilities that are discovered by others.

Otherwise, Wazuh is a good place to start, but there’s a learning curve for sure.

So you definitely still need a local DNS running. AdGuard Home, PiHole, Technitium, Hell your router probably has a local dns server you can enable and add some entries to it.

But once you setup a dns server, you’ll need to point all network clients to the dns server address so it can start resolving the web address to the ip in question.

I cover most of what services I’m running in my own post looking for assistance recently.

https://geekroom.tech/post/242

I’m not sure if you ever made your way to following through with this… But the three node system isn’t a bad starting point. However, here’s how I would approach it (similar to how I actually got my start in homelabs and how I do things now)

1 system for your router (looks like you picked a Qotom unit, those are decent), 8-16 gb ram

1 system for proxmox virtualization… run all your services in LXC’s or Virtual machines, as much ram as you can get a get for your system

And 1 system dedicated to storage (truenas or unraid), 32gb ECC ram (personal preference but not necessarily needed even with zfs for home use)

I’d start at https://reddit.com/r/homelab … but since we’re on Lemmy, I’d rather suggest posting on [email protected] (new, but looking to gain traction)

Can confirm, genuinely good service and support at reasonable prices.

Also use Cloudflare as new domain registrar because I use them as DNS as well. I can’t say that I’ve had any problems with them at all.