Yes that does seem to describe modern computing, indeed, consumer electronics in general.
It's no longer about solving actual problems, it IS the problem.
this post was submitted on 13 Mar 2026
1330 points (99.0% liked)
Selfhosted
56958 readers
1244 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: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
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.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
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 2 years ago
MODERATORS
No upstream bugs to fix?
Off topic, warning: this comment section is making me want to learn things
It's been 2 days off reddit and my brain has opinions other than "aaaargh" or "meh".
Proceed with caution
Don't worry, you're one Docker pull away from having to look up how to manually migrate Postgres databases within running containers!
(Looks at my PaperlessNGX container still down. Still irritated.)
I feel your pain. Had to fix my immich, NC and Joplin postgresdb. Turned out, DB via NFS is a risky life. ;D
Backups. You're forgetting them.
I should do some breaking network changes... While tunneled in.
“Yes, while connected to my wireguard server through port 123 here from my Chinese office, I should probably try to upgrade the wireguard server. That’s a great idea!”
Ask me how I know.
The rare moment when everything actually works. 😄
Time to start documenting it!
At 71, I have to document. I started a long time ago. I worked for a mec. contractor long ago, and the rule was: 'If you didn't write it down, it didn't happen.' That just carried over to everything I do.
load more comments
(2 replies)
Let's tinker around and accidentally break something.
and debug it until you have to reinstall your entire stack from scarch
GET OUT OF MY HOUSE!
load more comments
(3 replies)
My ~~man~~ person!
load more comments
(1 replies)
Have you tried introducing unnecessary complexity?
If you know how your setup works, then that's a great time for another project that breaks everything.
Saturday morning: "Incus and podman seem interesting. I bet I could swap everything over while the family is out this afternoon"
Sunday evening: "Dad, when will the lights work again?"
“Dad, when will the lights work again?
As soon as selinux decides I have permission.
load more comments
(2 replies)
load more comments
(7 replies)
Actually, one thing I want to do is switch from services being on a subdomain to services being on a path.
immich.myserver.com -> myserver.com/immich
jellyfin.myserver.com -> myserver.com/jellyfin
I'm getting tired of having to update DNS records every time I want to add a new service.
I guess the tricky part will be making sure the services support this kind of routing...
Why are you having to update your DNS records when you add a new service? Just set up a wildcard A record to send *.myserver.com to the reverse proxy and you never have to touch it again. If your DNS doesn't let you set wildcard A records, then switch to a better DNS.
Not OP but a lot of people probably use pi-hole which doesn't support wildcards for some inane reason
It does support it, you just have to add it to dnsmasq.
I have it Setup under misc.dnsmasq_lines like so:
address=/proxy.example.com/192.0.0.100
local=/proxy.example.com/
Then I have my proxied service reachable under service.proxy.example.com
That's my case. I send every new subdomain to my nginx IP on pi-hole and then use nginx as a reverse proxy
load more comments
(3 replies)
load more comments
(1 replies)
Wildcard CNAME pointing to your reverse proxy who then figures out where to route the request to? That's what I've been doing - this way there's no need to ever update DNS at all :)
I find the path a bit clunky because the apps themselves will oftentimes get confused (especially front-ends). So keeping everything "bare" wrt path, and just on "separate" subdomains is usually my preferred approach.
load more comments
(4 replies)
Have you already tried implementing an identity provider like Authentik, so you can add OIDC and ldap for all your services, while you are the only one that’s using them? 🤔
load more comments
(6 replies)
When's the last time you checked if your backup solution works?
But if my backups actually work then I miss out on the joy of rebuilding everything from scratch and explaining to my wife why non of the lights in the house work anymore.
load more comments
(1 replies)
load more comments
(6 replies)
How is the kubernetes (k3s/rke2) migration coming along?
One word: chaos engineering!
Can't believe nobody here mentioned nixOS so far? How about moving all of your configs in a flake and manage all of your systems with it?
load more comments
(5 replies)
logging is probably down
You do, of course have a dedicated rsyslogd server? An isolated system to which logs are sent, so that if someone compromises another one of your systems, they can't wipe traces of that compromise from those systems?
Oh. You don't. Well, that's okay. Not every lab can be complete. That Raspberry Pi over there in the corner isn't actually doing anything, but it's probably happy where it is. You know, being off, not doing anything.
load more comments
(2 replies)
You have remote power management set up for the systems in your homelab, right? A server set up that you can reach to power-cycle other servers, so that if they wedge in some unusable state and you can't be physically there, you can still reboot them? A managed/smart PDU or something like that? Something like one of these guys?
Oh. You don't. Well, that's probably okay. I mean, nothing will probably go wrong and render a device in need of being forcibly rebooted when you're physically away from home.
load more comments
(9 replies)
The comments in this thread have collectively created thousands of person-hours worth of work for us all...
view more: next ›