홈서버

In Part 1, I set up a Beelink SER9 MAX with WSL2 and Docker, building the backbone of my home server. With a mini PC running a server environment, I was ready to host anything.

But there was one problem.

“If I can only access it at home… isn’t it just an external hard drive?”

The real value of a home server begins when you can access it from anywhere. During the day I work at the office, and when I get home, there’s never enough time to sit in front of the computer. Days are packed. Commute time, lunch breaks, quick moments between tasks — I needed to be able to check and manage my server from my smartphone during these gaps.

So Part 2 is all about making the home server accessible from outside. And once again, I didn’t type a single line of code. I just told Claude Code, “Make it so I can access my server remotely.”

Remote Access Options for a Home Server

There are roughly three ways to access a home server from outside.

The first is port forwarding. You go into your router settings and open ports. The moment questions like “TCP or UDP?” come up, someone like me — a complete non-coder — is already lost. Plus, there are security risks, and if your home IP changes, you lose access.

The second is setting up your own VPN server — installing something like WireGuard or OpenVPN. Great if you have networking knowledge, but the setup is complex and requires certificate management. Mountain after mountain for a non-coder.

The third is Tailscale. And naturally, that’s what I chose.

What is Tailscale? — The VPN That Just Works

Tailscale, in one sentence: “Install it, log in, and you’re done.”

Traditional VPNs require setting up servers, creating certificates, configuring firewalls, setting up clients… the list never ends. Tailscale eliminates all of that. Install the app, log in with your Google or Microsoft account, and your devices automatically connect to each other securely.

Technically, it’s a mesh network built on top of WireGuard, a modern VPN protocol. But honestly, I don’t know exactly what that means. What matters is:

• Free for personal use — up to 100 devices
• 30-second install, almost nothing to configure — no networking knowledge needed
• Direct device-to-device connections — fast because there’s no middleman server
• Works on every platform — Windows, Linux, macOS, iOS, Android

The “nothing to configure” part is key. For non-developers like me, fewer settings means a better tool.

Installing Tailscale — Without Writing a Single Line of Code

My home server runs Docker on WSL2 inside Windows 11. Tailscale gets installed on the Windows side.

Installing Tailscale on the PC

I told Claude Code, “Install Tailscale for me,” and followed its instructions:

1. Download the Windows version from the official Tailscale website
2. Run the installer — Next, Next, Done
3. A Tailscale icon appears in the system tray
4. Click the icon → Log in → Sign in with Google

That’s it. The moment you log in, your server gets a dedicated Tailscale IP address. This IP is permanent — it doesn’t change even if your home internet IP changes. With this IP, you can access your server from anywhere.

What About WSL2 and Docker?

I was worried about this, but the answer is simple: you don’t need to do anything extra. Docker containers running inside WSL2 share Windows’ network, so installing Tailscale on Windows automatically makes all WSL2 services accessible.

For example, my WordPress runs as a Docker container, and accessing it via the Tailscale IP just works. Same for Immich (photo backup), Open WebUI (AI chat), and everything else.

I asked Claude Code, “Does this work with WSL2?” It said, “Install on Windows and WSL2 works too.” And it did. I didn’t need to understand why.

Accessing from a Smartphone — The Magical Moment

This is where it gets real.

The biggest reason I installed Tailscale was smartphone access. Working at the office all day, then coming home to household responsibilities — there’s surprisingly little time to sit at a computer. During lunch breaks, on the subway home, lying on the couch for a few minutes — I wanted to check my server during these in-between moments.

The setup is remarkably simple:

1. Install the Tailscale app on your smartphone
2. Log in with the same account you used on your PC
3. Turn on the VPN connection
4. Type the Tailscale IP in your browser

That’s it. During lunch at work, I check photos on Immich, send commands to my AI assistant via Telegram, and review my blog on WordPress admin — all from my phone.

The speed is surprisingly good too. Since it’s WireGuard-based, there’s none of the sluggishness you’d expect from a typical VPN. It feels like you’re on the same WiFi network.

For a busy professional with no time to sit at a computer, this is a game changer. The home server transforms from “something I use only at home” to “my personal cloud, always in my pocket.”

Tailscale Funnel — Opening Your Server to the World

Everything so far has been about connecting “my own devices.” But what about services that anyone should be able to access, like a blog?

Tailscale has a feature called Funnel. It exposes a specific service on your server to the internet, complete with an automatically assigned domain and HTTPS certificate.

Setting Up Funnel — Claude Code Did This Too

I told Claude Code, “Make my WordPress blog visible to the outside world.” Claude Code ran the necessary commands, and the result:

• Tailscale automatically assigned a domain
• An HTTPS certificate was automatically issued (Let’s Encrypt)
• External traffic was routed to my WordPress server

No need to buy a domain. No need to manually renew certificates. Tailscale handles everything.

This is exactly how you’re reading this blog right now. This post is served from the WordPress instance on my mini PC at home, exposed to the internet through Tailscale Funnel. No separate cloud server. No hosting service. Directly from the mini PC on my desk.

Funnel’s Limitations

It’s not perfect, of course:

• The domain is fixed as *.ts.net — custom domains aren’t supported
• Speed depends on your home internet’s upload bandwidth — not suitable for heavy traffic
• Only certain ports are available

But for a personal blog or small project, it’s more than enough. Being able to run a blog directly from your own server without cloud hosting — that’s the beauty of a home server.

The Non-Coder’s Secret: I Just Said “Do It”

I keep emphasizing this throughout the article, but I didn’t type a single line of code during any of this.

Installing Tailscale? Claude Code told me to “download and install this,” and I just clicked with my mouse. Setting up Funnel? Claude Code ran the commands itself. Verifying WSL2 compatibility? Claude Code said “it just works,” and it did.

I did exactly two things:

1. Told Claude Code “do this for me”
2. Clicked “Next” on the installation screens

This is how a non-coder runs a home server. Not by learning technology, but by delegating to an AI that knows technology. “Install Tailscale,” “Make it accessible remotely,” “Expose my blog to the public” — say it in plain language, and the AI handles the rest.

You might think, “But shouldn’t I at least understand the basics?” Honestly — no, you don’t have to. I still don’t know the difference between TCP and UDP. I’m not entirely sure what port forwarding actually does. But my home server is accessible from my smartphone anywhere in the world, and my blog is live on the internet.

What matters isn’t technical knowledge. It’s the will to make it happen. And in 2026, if you have that will, AI takes care of everything else.

What My Home Server Can Do Now

With hardware and Docker from Part 1, and Tailscale remote access from Part 2, here’s what my mini PC home server currently handles:

• Access from anywhere — office, café, subway, anywhere via smartphone
• Blog hosting — WordPress exposed to the internet via Funnel
• Photo/video backup — Immich as a self-hosted Google Photos replacement
• AI assistant — commanding an AI agent via Telegram
• Local AI — running LLMs directly on my server with Ollama

All of this runs on a single mini PC, and thanks to Tailscale, it’s always within reach. And everything was set up not by me, but by Claude Code. I just pointed the direction.

Coming Up Next

In Part 3, I’ll cover installing WordPress with Docker and building a blog. Setting up a bilingual (Korean + English) blog, and building a system where AI writes and publishes posts automatically — the non-coder’s home server journey continues.

All technical work in this series was performed by Claude Code (AI). The author (a non-coder) said “do it” and reviewed the results.