If you've ever set up frp — the go-to open-source reverse proxy for NAT traversal — you know the drill: SSH into a VPS, install frps, write a frpc.toml on your local machine, wrestle with ports and tokens, run it as a background service, and hope nothing drifts.
It works. But for a lot of people — self-hosters, remote workers, small teams, anyone who isn't a sysadmin — the CLI workflow is friction they'd rather avoid. That's exactly why I built MoonProxy: an open-source desktop GUI for frp (macOS + Windows, MIT-licensed, built on Tauri v2).
Rather than pitch features, here are five concrete scenarios where reaching for a GUI client saves real time and headaches.
1. The "I Just Want to SSH Into My Home Server" User
You're at a coffee shop. You need to fix something on the mini-PC running under your desk at home. No public IP, carrier-grade NAT, no VPN.
CLI path: write a frpc.toml with a tcp proxy stanza, make sure the remote port on your VPS matches, start frpc, keep it alive, SSH to vps-ip:remote-port.
GUI path: open MoonProxy, type your frps server address + token, add one TCP proxy rule (local port 22 → remote port 6000), click Start. The public address is shown right on the home screen. Done.
The win isn't speed for an expert — it's that a non-Linux-savvy family member can do it after a one-time setup.
2. Debugging Webhooks and OAuth Callbacks Locally
Third-party services (Stripe, GitHub, Slack) need to POST to a publicly reachable URL. Your dev server runs on localhost:3000.
With MoonProxy you spin up an HTTP proxy rule pointing at localhost:3000, and you get a public domain on your frps server that forwards straight to your laptop. No ngrok account, no tunnel-as-a-service limits — just your own infra.
The bonus: MoonProxy's home tab shows a live traffic chart for the tunnel, so you can see the webhook hitting your machine in real time. That's surprisingly useful when debugging "did the callback actually fire?"
3. Sharing a Local Service With a Non-Technical Colleague
You've got a demo running locally and want a teammate to take a look — but they're on a different network and you don't want to deploy to a cloud VM just for a 10-minute review.
Start a tunnel in MoonProxy, hand them the public URL. When they're done, click Stop. The URL dies. No lingering exposure, no cloud bill, no kubectl.
4. Keeping a Tunnel Up 24/7 Without Babying It
Long-running tunnels (home NAS access, a personal blog hosted on a Raspberry Pi, a Minecraft server for friends) need to survive reboots, sleep/wake cycles, and network hiccups.
MoonProxy handles this with three built-in features:
- System tray resident — close the window and the tunnel keeps running.
- Launch at login + silent start — boots hidden to the tray.
- Scheduled connect — pick weekdays and start/stop times; the scheduler hot-reloads every minute.
So a tunnel can run Monday–Friday 9–18 and turn itself off otherwise — without a cron job or a systemd timer you'll forget about.
5. Knowing Immediately When a Tunnel Breaks
The silent failure mode of a backgrounded frpc process is brutal: everything looks fine until you try to connect and realize the tunnel died three hours ago.
MoonProxy polls local endpoint reachability at adaptive intervals (exponential backoff from 3s up to 24s) and surfaces the result as colored health dots on the home screen. A broken tunnel shows red within seconds, not after you've already left the house relying on it.
The Broader Point
frp the protocol is excellent. The workflow around it — hand-edited TOML, process supervision, port juggling — is where most non-experts give up. A GUI doesn't make frp more powerful; it makes it accessible to the people who need NAT traversal but don't want a side quest in systems administration.
If any of those five scenarios sound familiar, MoonProxy is free and open source:
- GitHub: MoonProxyHQ/moonproxy-desktop
- Website: moonproxy.app
- Platforms: macOS (Apple Silicon + Intel), Windows x64
- License: MIT
You bring your own frps server (self-hosted or any community endpoint you trust) — MoonProxy handles configuration, lifecycle, monitoring, and updates. The bundled frpc engine even self-updates from upstream releases, so you never have to wget a binary again.
Questions, feature ideas, or war stories? The Discussions tab is open. 🌙
Top comments (0)