U
/u/zn-ku
Guest
I run a small Minecraft (Fabric) server plus a companion website out of my home network, and I'd like a second set of eyes on whether the setup makes sense, is over-engineered somewhere, or is missing something obvious. Rough shape of it (details generalized, no real IPs/hostnames):
Home side: Residential cable connection (~1Gbps down / 50Mbps up). The ISP router is set as an exposed host, forwarding everything to a pfSense box that handles the actual firewalling, default-deny inbound, with all port-forwarding rules living on pfSense rather than the ISP router. Behind that is a flat LAN hosting the Minecraft server, a Discord bot, and the website's backend.
Public side: A small VPS acts as the public-facing edge and reaches back into the home LAN over a WireGuard tunnel. nginx on the VPS does double duty: reverse-proxying HTTP(S) for the website/Discord bot, and stream-proxying Minecraft's TCP/UDP port straight through to the LAN server. The VPS also runs its own local firewall on top of whatever pfSense allows outbound from home.
The server itself: I know this part will get some heat, but I'm on a budget and this is a passion project, so everything runs on one PC. Windows 10 LTSC (supported until 2032, so still on security updates, but I know a single-box setup isn't ideal). Specs: Ryzen 9 3900X, 32GB DDR4, 1Gbps fiber. Holds a steady 20 TPS. Plan is to move to a dedicated server with Proxmox once I can afford it, so services can be properly separated.
Backups (this is where I really want input): Currently using git to version the Minecraft world folder, which I already know is a bad idea. I have a few spare 250GB SSDs I could put toward something better, maybe a TrueNAS VM eventually, but I'd love advice on a reasonable interim setup that doesn't require new hardware.
App layer: A Vite/React frontend with a small Express backend, sitting behind the same reverse proxy as everything else.
Happy to go into more detail on specifics. Didn't want to post exact configs/IPs publicly, so drop a comment or DM if you want to dig in.
submitted by /u/zn-ku
[link] [comments]
Continue reading...
Home side: Residential cable connection (~1Gbps down / 50Mbps up). The ISP router is set as an exposed host, forwarding everything to a pfSense box that handles the actual firewalling, default-deny inbound, with all port-forwarding rules living on pfSense rather than the ISP router. Behind that is a flat LAN hosting the Minecraft server, a Discord bot, and the website's backend.
Public side: A small VPS acts as the public-facing edge and reaches back into the home LAN over a WireGuard tunnel. nginx on the VPS does double duty: reverse-proxying HTTP(S) for the website/Discord bot, and stream-proxying Minecraft's TCP/UDP port straight through to the LAN server. The VPS also runs its own local firewall on top of whatever pfSense allows outbound from home.
The server itself: I know this part will get some heat, but I'm on a budget and this is a passion project, so everything runs on one PC. Windows 10 LTSC (supported until 2032, so still on security updates, but I know a single-box setup isn't ideal). Specs: Ryzen 9 3900X, 32GB DDR4, 1Gbps fiber. Holds a steady 20 TPS. Plan is to move to a dedicated server with Proxmox once I can afford it, so services can be properly separated.
Backups (this is where I really want input): Currently using git to version the Minecraft world folder, which I already know is a bad idea. I have a few spare 250GB SSDs I could put toward something better, maybe a TrueNAS VM eventually, but I'd love advice on a reasonable interim setup that doesn't require new hardware.
App layer: A Vite/React frontend with a small Express backend, sitting behind the same reverse proxy as everything else.
Happy to go into more detail on specifics. Didn't want to post exact configs/IPs publicly, so drop a comment or DM if you want to dig in.
submitted by /u/zn-ku
[link] [comments]
Continue reading...