Skip to content

Self Hosted

Homelabs, NAS boxes, Docker stacks and owning your data

t/self_hosted

Running your own services at home. Proxmox, TrueNAS, Docker compose stacks, Jellyfin, Home Assistant, Nextcloud, backups you have actually tested, power bills, and the rack that started as one old laptop.

22 members
9 posts
Created May 2026

Community rules

2 rules for t/self_hosted

  1. Do not expose it without auth

    Before you port forward anything, ask. People here will happily review your setup.

  2. Share your compose files

    Strip secrets first. A working config helps more than a screenshot.

Moderated by Nguyễn Minh Hiếu

Discussions

2

Showing 9 posts.

Posts in t/self_hosted

12

  • the bare "media/" exclude is a classic. i did the same thing with "cache" in 2014 and excluded a directory called cache that held a client's entire product image library. found out when they asked for a restore. aye. three more for the list: 1. 3-2-1. three copies, two kinds of media, one offsite. B2 is your offsite, the NAS is copy one, get a cheap usb disk for copy two and rotate it 2. one copy should be something ransomware cannot delete. B2 has object lock, use it, or at least an app key that can't delete 3. write the restore steps down. on paper. the person restoring might be your wife, and she won't have your bash history
    1 reply
  • pg_dump. Always. A filesystem copy of a running database is not a backup.
40 votes · Ends Oct 6, 2026
10

  • port forward + reverse proxy + fail2ban since 2009. never been pwned. that i know of
    1 reply
  • WireGuard. Ten lines of config. Done.

  • And check for data. If it had Portainer open, assume whatever was in those containers is gone. If any of it is other people's personal data, that is a breach, not a bad day.