I Threw My Server in the Garbage, and My Network Got Better

An Open Source Outlaw Story

There comes a time in every man’s life when he has to admit that a relationship just isn’t working anymore. You’ve tried everything. You’ve invested time, money, patience, and more than a few colorful conversations. You’ve stayed up late trying to make things right. You’ve given second chances, third chances, and chances you didn’t even bother counting. And eventually, you realize something. It’s not getting better.

In my case, the relationship was with an Ubuntu server. And this week, I threw it in the garbage. Literally. And I couldn’t be happier.

It Started With a Good Idea

Like most homelab adventures, mine started innocently enough. I wanted to host my own services. I wanted control over my data. I wanted to stop paying monthly subscriptions for things I could reasonably do myself. So, I built a server. Then I added something. And something else. Before long, that machine was running Nextcloud, Navidrome, Immich, Tube Archivist, and an assortment of Docker containers that seemed to multiply every time I turned my back. It was impressive. At least on paper.

I had my own cloud storage, music streaming, photo management, and video archiving. All without handing my digital life over to another company. I was living the open source dream! Except for one little problem. The dream was becoming a nightmare. When Everything Depends on Everything

Here’s something nobody tells you when you start self-hosting. Just because a machine CAN run fifteen services doesn’t necessarily mean it SHOULD. Every time I wanted to fix something, I had to worry about breaking something else.

A Docker change here. A permission problem there. A storage mount that didn’t behave. A service that worked perfectly yesterday but suddenly decided today was a good day to develop a personality. And rebooting? Oh, goodness.

Rebooting that server became an event. I didn’t reboot it casually. I approached the task like a man preparing to defuse a bomb. Would everything come back? Would Docker cooperate? Would the storage mount correctly? Would I spend the next three hours trying to figure out why something that worked before the reboot had suddenly stopped?

There were days when I genuinely wondered whether I was running the server or the server was running me. Meanwhile, somewhere in the background, Steve was smiling.

You know Steve.

He’s our fictional corporate IT guy. Clipboard, tie, company polo shirt, and an unshakable belief that every problem can be solved with another subscription.

“Have you considered moving everything to the cloud?” Put the clipboard down, Steve.

Then I Had an Idea

What if I stopped trying to make one computer do everything? What if I took those services and gave them their own machines? Nothing extravagant. Nothing expensive. Just some perfectly capable computers that were sitting around waiting for something useful to do. A dedicated machine for music. Another for photos. One for Nextcloud. A separate system handling video and media. And suddenly, something wonderful started happening.

Things just worked.

Navidrome got its own server and dedicated 8TB music drive. Jellyfin continued doing what Jellyfin does best. Tube Archivist could download videos without making me nervous about everything else running on the network. Nextcloud was getting a storage upgrade. And Immich was moving to a different room entirely, taking some of the heat and electrical load away from my main server area. I wasn’t just reorganizing software. I was reorganizing the entire philosophy of my homelab.

The Greatest Discovery Wasn’t Speed

Don’t misunderstand me. Performance matters. But the biggest improvement wasn’t faster processing or more memory. It was independence. I could work on one thing without affecting everything else. Read that again. I could reboot the music server without interrupting Nextcloud. I could troubleshoot Immich without wondering what it might do to Jellyfin. I could replace a drive without turning the entire household into an involuntary technology experiment.

Sure, these systems still share a network and electrical infrastructure. But a problem with one application no longer had to become everybody’s problem. And troubleshooting? Good grief, what a difference.

If Navidrome has a problem, I troubleshoot Navidrome. Not fifteen containers, six mount points, three databases, and a mysterious Docker network that apparently developed its own opinions sometime last Tuesday.

The best homelab isn’t the one that can do everything. It’s the one where fixing one thing doesn’t break everything else.

That’s a lesson I wish I’d learned a long time ago.

The Final Goodbye

Eventually, it was time to retire the old Ubuntu server. I had moved the important services. The new machines were working. The data was being preserved. The old server had served its purpose. So I issued the shutdown command. And wouldn’t you know it?

THE THING WOULDN’T EVEN SHUT DOWN PROPERLY!

Error after error involving UFW firewall rules. One after another. I stood there watching a machine that had caused me months of headaches apparently determined to cause one final headache on its way out. I don’t even know whether it ever completed the shutdown.

And at that point? I didn’t particularly care. The machine was finished. Its career was over. Its services had been replaced. And the old server went into the garbage. Not metaphorically, THE ACTUAL GARBAGE.

I can almost hear Steve now – “Have you opened a support ticket?”

Yes, Steve. It’s in the garbage can.

Smaller Machines, Bigger Freedom

Here’s what surprised me most about this whole experience. I didn’t solve my problems by purchasing a massive new server. I didn’t sign up for an expensive cloud platform. I didn’t hire a consultant or buy some enterprise management package. I took equipment I already had, gave each machine a clear purpose, and simplified the entire operation.

There are tradeoffs, of course. More machines mean more operating systems to maintain, more devices to monitor, and more opportunities for hardware failure. Distributed systems don’t magically eliminate problems. But they do allow me to contain them.

And with smaller, more efficient machines, I can spread the workload and heat instead of concentrating everything in one troublesome box.

The result? A homelab that’s easier to understand, easier to maintain, and considerably more enjoyable. And maybe that’s the real point. Technology is supposed to serve us.We’re not supposed to spend every waking moment serving it.

The Outlaw’s Take

I started this journey because I wanted to own my data. My music. My photographs. My documents. My videos. I didn’t want somebody else’s subscription price, advertising strategy, or corporate decision determining what I could do with things I already owned.

But somewhere along the way, I had created a different kind of dependency. Instead of depending on a giant technology company, I had made everything depend on one increasingly troublesome server.

That’s not freedom either.

So I changed it. And now, when I sit down at my desk and open my music library, something remarkable happens. The music plays. No drama. No troubleshooting session. No frantic checking to see what else broke. Just music.

And somewhere in the distance, I can almost hear a tractor crank. Steve lowers his clipboard. The Outlaw smiles.

Because sometimes the best upgrade isn’t adding something new.

Sometimes it’s finally getting rid of what wasn’t working.

Open Source Outlaw — Breaking the Rules of Big Tech.

Your hardware. Your data. Your rules.

And Steve? Stay away from my garbage can.