SEC.01

The playbook

The run starts read-only: the recon probes decide what happens next. The steps that follow are adapted to the distribution and state found — a real machine is rarely clean.

1. 01reconfrpc already present? version
2. 02reconexisting service and config (do not overwrite frpc.toml)
3. 03reconthe local port to expose is actually listening
4. 04reconarchitecture (amd64 or arm64)
5. 05actThe frp server is reachableverify
6. 06actInstall frpcverify
7. 07actCreate the frp system userverify
8. 08actWrite /etc/frp/frpc.tomlverify
9. 09actCreate the systemd serviceverify
10. 10actEnableverify

SEC.02

What it verifies

Each step ships its own check. The run only moves on when the check passes, so what the recipe reports as done is what is actually on the server.

1. 01verifyThe frp server is reachableVerified bytimeout 5 bash -c '</dev/tcp/${server_addr}/${server_port}' && echo ok
2. 02verifyInstall frpcVerified byfrpc --version
3. 03verifyCreate the frp system userVerified byid -u frp
4. 04verifyWrite /etc/frp/frpc.tomlVerified byfrpc verify -c /etc/frp/frpc.toml && stat -c %a /etc/frp/frpc.toml
5. 05verifyCreate the systemd serviceVerified bysystemd-analyze verify /etc/systemd/system/frpc.service && echo ok
6. 06verifyEnableVerified bysystemctl is-active frpc && journalctl -u frpc -n 30 --no-pager | grep -c 'start proxy success'

SEC.03

Guardrails

Non-negotiable instructions the run must respect, whatever it finds on the server.

SEC.04

Variables

What you choose before launching — the recipe fills in the rest.

SEC.05

How a recipe runs in Servor

Servor is zero-knowledge: the platform cannot execute anything on its own. When you launch this recipe, a run reads the reconnaissance, plans the steps and asks for your approval. Each approved command is signed by your browser — with a key the server never sees — then relayed verbatim to the agent, which verifies the signature locally before executing.

SEC.06

Deploy on Servor button

Maintain frp tunnel or a project that needs it? Put this button in your README or on your site: one click and your users install it on their own server.

SEC.07

More networking recipes

1. 01TailscaleTailscale mesh VPN: auth key or login link, without touching the server DNS.
2. 02WireGuardWireGuard VPN server + a first client, without touching routing. Destructive: network interface.
3. 03Pi-holePi-hole v6 (DNS + ad blocking) in a container, on the chosen IP. Destructive when listening on 0.0.0.0 (port 53).
4. 04AdGuard HomeAdGuard Home filtering DNS, local UI. Destructive: may free port 53.
5. 05OpenVPNOpenVPN server via the road-warrior script (angristan), first client created. Destructive: network.