Homelab Journal
Homelab Journal #9: Remote access without opening the front door
Week nine of the SmallGrid homelab: setting up private remote access and avoiding the temptation to expose services too early.
This week’s goal
Reach the server when away from home without making it public to the whole internet.
The beginner temptation is to forward a port and declare victory. I chose not to do that, mostly because I like sleeping.
What I actually did
I set up private remote access using a mesh-style approach.
The useful parts were:
- server accessible from my own devices
- no public Jellyfin login page
- no router port forwarding
- no dynamic DNS rabbit hole
- fewer moving parts to explain later
I tested it from a phone away from Wi-Fi and confirmed the server was reachable.
What broke, or nearly did
I briefly forgot that remote playback still depends on home upload speed.
Remote access is not a magic bandwidth generator, which feels unfair but is apparently how networks work.
What I’m keeping
- Private access by default
- No public port forwarding for now
- A short note of the private address
- A proper test from outside the house
SmallGrid takeaway
Remote access should start private. If there is no clear reason to expose a service publicly, do not promote your home server to internet-facing main character.