this post was submitted on 01 May 2026
319 points (96.8% liked)
Selfhosted
60409 readers
204 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:
-
Be civil.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Not OP. But i do the same.
I have multiple proxmox hosts, running multiple VMs, each running containers.
I do it so I can minimise disruption. Fixing a fault in immich doesn’t mean the house is without plex for a week.
Running multiple Proxmox hosts in a cluster makes sense so you can swap VMs from one the other and have extra hardware reliability. I'd also get grouping your containers on different Docker VMs the apply the same security rules to containers in a group (internally vs. externally available for example). But how does a faulty Immich container take down a Plex container?
Could be anything.
Something decides it’s going to fill your disk up with noise and plex enters a crash loop as it can’t write to disk any more.
Your reverse proxy decides it’s not going to issue valid SSL certificates so all your plex clients refuse to connect.
One day an OS update decides your network configuration wasn’t important, and your OS throws a shit fit because there’s no route to 192.168.1.100 any more