Skip to main content
  1. Posts/

What Did You Stop Self-Hosting? Real Reddit r/selfhosted Experiences & Tech Guide

·4 mins

The Community Spark: The “Un-Self-Hosting” Trend #

A fascinating trend recently took over the r/selfhosted community: “What did you stop running on your home server?” As home labs mature, enthusiasts are realizing that self-hosting everything is a fast track to burnout. The discussion highlighted a crucial paradigm shift—knowing what not to host is as important as knowing how to deploy services. Users shared their lived experiences of moving critical, high-maintenance workloads off their local hardware to third-party providers or managed VPS environments.

Synthesized Community Perspectives #

Analyzing the top-voted comments reveals a strong consensus around three main pain points: maintenance overhead, data gravity, and network reliability.

Community members overwhelmingly agreed that Email servers are the first to be abandoned. Maintaining IP reputations, managing DKIM/SPF records, and fighting to escape spam blacklists is exhausting. Similarly, users abandoned heavy Database servers and Cloud Storage (like Nextcloud) due to the sheer stress of managing backups and syncing conflicts.

There weredebates, however. Some purists argued for hosting Nextcloud locally using cheap secondary drives, while pragmatists preferred paying $5/month for managed storage to avoid catastrophic data loss. The overall consensus? Keep your media servers and IoT controllers local, but offload your public-facing, high-availability, and data-critical stacks.

Deep-Dive: Critical Workload Offloading Guide #

If you’re re-evaluating your home lab, here is a technical guide on how to securely offload your remaining critical services to a cheap VPS using WireGuard.

Step 1: Provision a VPS and Install WireGuard #

Instead of exposing local services via complex ingress tunnels, establish a simple, secure WireGuard tunnel between your VPS and your home server.

Run this on your VPS (Public Node):

sudo apt install wireguard
umask 077; wg genkey | tee privatekey | wg pubkey > publickey

Step 2: Configure the Tunnel #

Edit your VPS /etc/wireguard/wg0.conf:

[Interface]
Address = 10.8.0.1/24
PrivateKey = <VPS_PRIVATE_KEY>
ListenPort = 51820

[Peer]
PublicKey = <HOME_SERVER_PUBLIC_KEY>
AllowedIPs = 10.8.0.2/32

Bring the interface up: sudo wg-quick up wg0. Now, your VPS reverse proxy (Nginx Proxy Manager or Caddy) can route traffic safely to your home server via the 10.8.0.x subnet without opening home ports to the internet.

Self-Hosted vs. Managed: The Pros & Cons #

WorkloadSelf-Hosted (Local) ProsManaged / Third-Party ProsCommunity Verdict
EmailFull data privacy, no monthly feesGuaranteed deliverability, no spam managementOffload (Mailcow on a VPS at best)
Cloud StorageUnlimited space (cheap HDDs), full controlZero sync conflicts, handled backupsOffload for sensitive docs; Local for media
DatabasesLow latency to local appsManaged automated backups, failoverHybrid (Offload Prod, keep Dev local)
Media ServingTotal control, no bandwidth capsN/A (Home hardware is king here)Keep Local (Plex/Jellyfin)

The Verdict / Expert Advice #

Self-hosting should empower you, not enslave you.

  • For Solo Enthusiasts: Keep media streaming (Jellyfin), smart home hubs (Home Assistant), and ad-blockers (Pi-hole) on local hardware. Offload email to Google or Fastmail.
  • For Homelab Builders: Keep an inexpensive VPS for a WireGuard exit node and reverse proxy. Host your databases locally but automate nightly encrypted dumps to an S3-compatible provider like Backblaze B2.
  • _for Families: Use managed cloud storage to prevent catastrophic data loss of personal photos. Local hardware fails; redundancies matter.

Frequently Asked Questions (FAQ) #

1. Why do people stop self-hosting email? Self-hosting email requires constant management of DNS records (DKIM, SPF, DMARC) and IP reputation. Major providers like Gmail and Outlook often block residential or dynamic VPS IPs, making reliable email delivery nearly impossible without dedicated infrastructure.

2. What is the alternative to self-hosting Nextcloud? Many users migrate to managed cloud sync services like Google Drive, Dropbox, or dedicated managed Nextcloud providers like Hetzner Storage Share. This eliminates the headache of database maintenance and sync conflict resolution.

3. What should I keep self-hosting on my home server? The community highly recommends keeping media servers (Plex, Jellyfin), smart home automation (Home Assistant), and network ad-blockers (Pi-hole, AdGuard Home) local. These benefit from local network speeds and don’t require public IP reputation.

4. How do I securely access self-hosted apps remotely? Instead of port forwarding, use a VPN like WireGuard to tunnel into your home network, or set up a reverse proxy on a cheap VPS that forwards traffic to your home network via a secure tunnel (like Cloudflare Tunnels or a direct WireGuard connection).