this post was submitted on 19 Nov 2025
12 points (100.0% liked)

Selfhosted

53057 readers
606 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.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

How realistic is this architecture? It's been a while since I've set something like this up for work.

The thought behind this layout is that having only one machine hanging out there with just Apache and ssh (from lan only, non-standard port), and forwarding via Mod_Proxy any services I might want to share with non-LAN friends/family (photos, docs), is a smaller exposure than hosting all my VMs in a DMZ and hoping that the one server doesn't get nuked.

Something like: DNS -> public-zone{ www-serv } <-> firewall-1 <-> lan{ vm-host <-> firewall-2 <-> (printers, laptops, etc) }

firewall-1 is actually a router running Tomato, with custom iptables rules. That way if www-serv is compromised the attacker can't just drop some rules.

firewall-2 is just iptables rules on vm-host

all LAN computers' iptables are a little more permissive, with holes for SAMBA, CUPS, and ssh on non-standard port.

What do you think? Is this sufficient? What would you do differently?

all 9 comments
sorted by: hot top controversial new old
[–] frongt@lemmy.zip 3 points 22 hours ago* (last edited 22 hours ago) (2 children)

I think Apache is overkill. Just use caddy or traefik if it's containers. nginx if not.

The real answer is, ngnx is a great fit. I already know most quirks of Apache, though, and I don't necessarily want to pull in another manual to my brain.

I might switch in the future, though. It'd be handy to have that in my pocket.

I'm not using containers, per se, at least not in the docker sense, virtualization is done with is KVM

[–] RheumatoidArthritis@mander.xyz 4 points 1 day ago (1 children)

Yup, it worked for me, no incidents. Add mod_security if you're worried, and of course keep Apache up to date.

I now moved Apache to a separate VLAN on the private side, and have strict firewall rules on traffic from that VLAN only to services it's supposed to be proxying.

[–] BonkTheAnnoyed@lemmy.blahaj.zone 2 points 1 day ago (3 children)

thanks! It's hard not to feel out of my depth, it's been so long. And, it being my own info, not a corp's protected by insurance, indemnity, mandatory arbitration, and (as a last resort) backups, the stakes feel a little higher.

Yeah, I felt a little uneasy putting my data on something which could be broken into. Still do, having seen my share of hacked websites at work.

If it helps you, I host everything in subdirectories with non obvious names, so bots only hit 404 pages.

Nextcloud.bonk.xyz -> nope Bonk.xyz/nextcloud -> nope Bonk.xyz/bonkcirrostratus -> good luck guessing that

[–] cecilkorik@lemmy.ca 2 points 1 day ago

Sounds like you're doing fine to me. The stakes are indeed higher, but that is because what you're doing is important.

As the Bene Gesserit teaches: I must not fear. Fear is the mind-killer. Fear is the little-death that brings total obliteration. I will face my fear.

Make your best effort at security and backups, use your fears to inform a sober assessment of the risks and pitfalls, and ask for help when you need to, but don't let it stop you from accomplishing what you want to. The self-hosting must flow.

[–] RheumatoidArthritis@mander.xyz 1 points 1 day ago (1 children)

Yeah, I felt a little uneasy putting my data on something which could be broken into. Still do, having seen my share of hacked websites at work.

If it helps you, I host everything in subdirectories with non obvious names, so bots only hit 404 pages.

Nextcloud.bonk.xyz -> nope Bonk.xyz/nextcloud -> nope Bonk.xyz/bonkcirrostratus -> good luck guessing that

That's a really good strategy , thanks!