this post was submitted on 14 Nov 2025
-44 points (10.7% liked)

Selfhosted

52938 readers
697 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
 

alright folks, let's get real. we all have our sprawling digital fortresses, carefully constructed brick by brick. but there's always that one piece of software, that one perfectly tuned instance, where if it so much as hiccuped, you'd be ready to throw the entire homelab out the window and start fresh in a cave. what is it for you? what's your absolute, non-negotiable, 'i will personally visit the datacenter if this fails' self-hosted application? for me, it's my media server stack. my wife would disown me. don't let me down, arr suite.

you are viewing a single comment's thread
view the rest of the comments
[–] curbstickle@anarchist.nexus 5 points 19 hours ago (1 children)

Well the only way my media server goes down is if the power is out for more than a few hours or my internet connection is down.

So I'd have to say that.

[–] fhoekstra@feddit.nl 1 points 15 hours ago (1 children)

I don't believe you, but I'd like to be proven wrong.

I expect you have a UPS that feeds your hosts and networking equipment and something like ZFS for disk redundancy. This protects against the most common failures and is usually enough, but there are still single points of failure in such a setup, that are not as common, not as hard to deal with through manual intervention, and quite difficult to protect with redundancy.

I would be surprised if you are protected against the following single points of failure without manual intervention:

  • NAS machine (not just disk) failure. You would need to have a multi-node distributed storage, like Ceph, to protect against this.
  • Networking equipment failure. I think you can do some magic with BGP to do this, but I'm not a network engineer and I've never set up a redundant network.
[–] curbstickle@anarchist.nexus 2 points 11 hours ago

Ceph for the proxmox cluster, 2x48 port switch + 16 port 10gbit as the core, 2xNAS (technically one is the backup, and there would be a few moments of downtime as the containers restart - a different container with the same config pointed to the backup NAS instead).

UPS and internet are the SPoF.