The $50 Laptop That Replaced My “Real” NAS (And Why Nextcloud Had to Go)

#

Reading time: ~7 minutes | Word count: ~1,100

I spent three weeks trying to make Nextcloud work. Three weeks of PHP dependencies, database tuning, Redis caching configs, and a mobile app I only needed to browse files. Then I deleted everything and installed Samba. Best decision I made all year.

If you’ve been shopping for a NAS setup, you’ve seen the price tags. Synology’s 8-bay units creep past $800. QNAP’s 32GB RAM workstations cost more than some desks. Server racks with enough drive redundancy to survive a fire sell for thousands. The homelab community makes it look like you need enterprise iron before you even start.

You don’t. You need a computer, some storage, and a network cable.

What a NAS Actually Is (Hint: It’s Not a Brand)

#

NAS stands for Network Attached Storage. That’s it. Storage accessible over a network. No specific hardware. No required brand. No minimum RAM spec. No “NAS-grade” drives that cost 30% more for the same platters in a different box.

A NAS is just a machine sharing files on your LAN. Your old laptop running Debian is a NAS. Your Raspberry Pi with a USB drive is a NAS. The definition is the function, not the form factor.

I learned this the hard way after burning through three “proper” self-hosted platforms before circling back to the simplest possible setup.

The Bloated Trio: Nextcloud, Seafile, Owncloud

#

Here’s what I tried, in order:

Nextcloud — The darling of the self-hosted world. Calendar, contacts, talk, deck, forms, office suite, app store. I needed file sharing. I got an operating system for an operating system. The Android app was mandatory for basic file browsing. The web UI lagged on my hardware. 90% of features I never touched.

Seafile — Lighter than Nextcloud, focused on sync. Better. But still required a web interface, user management overhead, and a dedicated service stack. For sharing files with three family members, it was overkill.

Owncloud — Similar to Nextcloud (it’s the predecessor, actually). Same bloat, smaller community, more friction.

All three wanted to be Dropbox replacements. All three wanted to manage my calendar, my contacts, my collaborative documents. I didn’t need a cloud platform. I needed a folder I could open from any device on my network.

The Stack That Actually Won

#

Two tools. Zero bloat. Total power draw: 15 watts idle.

Samba — LAN File Sharing That Just Works

#

Samba speaks SMB/CIFS. Every operating system understands it natively. Windows File Explorer. macOS Finder. Linux file managers. Android file apps. iOS Files app. No client software. No accounts to create. No web dashboards.

# Install on Debian/Ubuntu
sudo apt install samba

# Basic share config in /etc/samba/smb.conf
[family]
   path = /srv/nas/family
   browseable = yes
   read only = no
   valid users = @family

That’s it. The share appears in every device’s file browser. Drag, drop, done.

Syncthing — P2P Sync Without the Cloud Bill

#

Samba handles LAN access. But what about photos from your phone? What about syncing documents between devices when you’re not home?

Syncthing. Peer-to-peer. Encrypted. No monthly fees. No middleman server. Your devices talk directly to each other.

Install Syncthing on your phone, your laptop, your server. Create a folder, share the device ID, done. Photos from your phone land on your NAS automatically. Documents sync between machines without touching someone else’s infrastructure.

# Install on Debian
sudo apt install syncthing
sudo systemctl enable --now syncthing@youruser

The web UI is local-only by default. No exposed ports. No attack surface.

Remote Access Without the Headaches

#

My ISP uses CGNAT. No public IP. Tailscale refused to relay properly. WireGuard needed a port I couldn’t forward.

The fix: Cloudflared Tunnel + Netbird.

Cloudflared exposes your Samba share (or Syncthing web UI) through Cloudflare’s edge. No port forwarding. Netbird (open-source, WireGuard-based) creates a mesh network that punches through CGNAT via DERP relays.

Both free. Both work behind carrier-grade NAT. Both took under 30 minutes to configure.

The Honest Limitations

#

This isn’t perfect. I won’t pretend it is.

• No RAID. If my single HDD dies, data dies with it. I keep critical files backed up to an external drive weekly. RAID is not backup anyway.
• No web GUI for Samba. You manage shares via config files or CLI. If you need a dashboard, install Cockpit or Webmin alongside it.
• No built-in photo gallery. Syncthing syncs photos; it doesn’t display them beautifully. I use Immich on a separate machine for that.
• No collaboration features. No document editing, no shared calendars, no kanban boards. That’s not what this stack does.

The Hardware: Potato Specs, Real Results

#

Current build:

Previous build was a Celeron N4000 laptop with 4GB RAM and a 500GB HDD. Idled at 5 watts. Worked fine for months.

Potato hardware is not a barrier. Old laptops are perfect NAS machines — they have built-in batteries (UPS!), built-in displays (debugging!), and they cost nothing on the used market.

Why This Works: Workflow First, Crowd Second

#

The self-hosting community has a gravitational pull toward complexity. Kubernetes clusters for three users. Reverse proxies for local services. Monitoring stacks for a single container.

I followed that crowd for years. It made me miserable.

The principle that changed everything: choose tools that match your workflow, not tools that match someone else’s blog post.

I need file sharing → Samba. I need sync → Syncthing. That’s the whole stack. Two config files. Two services. Done in an afternoon.

FAQ

#

Q: Can I use this setup for media streaming (Plex/Jellyfin)? A: Yes, but it’s a separate service. Samba + Syncthing handle storage and sync. Add Jellyfin for streaming. The i3-6100T handles 1080p transcodes fine.

Q: What happens if my HDD fails with no RAID? A: You restore from backup. I run weekly rsync to an external USB drive. For critical data, I also push encrypted restores to Backblaze B2 ($0.005/GB/month).

Q: Is Samba secure enough for sensitive files? A: On your LAN, yes. Samba supports encryption and user authentication. Don’t expose SMB ports to the internet — use Cloudflared or a VPN for remote access.

Q: Why not just use Tailscale instead of Netbird? A: Tailscale requires port forwarding or a public IP for optimal performance. My CGNAT setup blocks that. Netbird’s DERP relay system works without any ISP cooperation.

Q: How many users can this handle? A: Samba handles dozens of concurrent users on gigabit LAN without breaking a sweat. Syncthing scales to hundreds of devices. The bottleneck is your disk I/O, not the software.