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

Selfhosted

53057 readers
472 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
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
12
public Apache VirtualHost pointing to e.g. NextCloud/Immich VMs inside LAN (lemmy.blahaj.zone)
submitted 1 day ago by BonkTheAnnoyed@lemmy.blahaj.zone to c/selfhosted@lemmy.world
8 comments fedilink hide all child comments
 

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?

you are viewing a single comment's thread
view the rest of the comments
[–] BonkTheAnnoyed@lemmy.blahaj.zone 2 points 21 hours ago

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