SSH terminals
Run status, up, down, doctor, and region commands without a GUI.
Free VPN CLI works from the command line, so server and SSH workflows can check status, connect, switch regions, and diagnose issues without a desktop window.
For headless work, start with an explicit binary check and status read. Install from the downloads page or documented shell installer when needed.
Confirm the CLI exists, read current state, then connect when the environment allows VPN tunnels.
freevpn doctor --json for route, DNS, controller, license, and egress evidence.Keep VPN work inside the shell where your server, scripts, and diagnostics already run.
Run status, up, down, doctor, and region commands without a GUI.
Use the CLI where the host allows VPN service and tunnel permissions.
Parse --json output for automation and monitoring.
Use doctor output when DNS, routes, or egress behavior is unclear.
Headless sessions should verify the CLI and current VPN state before bringing the tunnel up.
If the host blocks tunnel permissions, use freevpn doctor --json for evidence.
Three verbs cover most day-to-day VPN work. set-region and doctor cover region selection and troubleshooting.
Headless VPN work should be explicit. Check install, read status, connect, verify again, and use doctor output on failure.
| Command | Why it matters |
|---|---|
command -v freevpn >/dev/null 2>&1 && freevpn version --json | Verify the CLI exists before a script changes VPN state. |
freevpn status --json | Read current VPN state in a machine-friendly format. |
freevpn up --json | Connect and return structured output. |
freevpn down | Restore state when the workflow requires cleanup. |
freevpn doctor --json | Collect troubleshooting evidence on headless hosts. |
The CLI is useful where a desktop window is unavailable or inappropriate.
Every core workflow is available through terminal commands.
Use --json for scripts, logs, agents, and monitors.
The installer registers the daemon during setup on supported systems.
Set explicit exits for test or troubleshooting sessions.
Use VPN-layer blocking while the tunnel is connected.
Capture route, DNS, controller, license, and egress checks.
When the VPN is connected, Ad Block can help scripts, terminals, and server-side tools avoid known ad, analytics, and tracker domains.
These workflows are terminal-first. On a desktop machine, you can add the optional companion window for human status checks while keeping scripts and agents on CLI commands.
SKILL.md documents Free VPN CLI commands, JSON output, exit handling, and troubleshooting flows so agents can use terminal commands without guessing from screenshots.
Claude
Cursor
Codex
OpenClaw
Hermes+ any MCP toolUse Free VPN CLI when SSH sessions, scripts, or servers need command-line VPN control.
Use only where tunnel permissions are allowed.
Keep status and diagnostics in terminal output.
Use JSON output and explicit cleanup.
Give SKILL.md to coding agents for safer command usage.
Free VPN CLI is genuinely free to use: no signup, no email, no credit card. Use it for terminal, scripts, and developer workflows. The paid option removes the continuous connection limit for people who want the VPN running all day. Cancel any time. Prices in USD.
No signup. No card. No expiry. Use it as much as you want.
The paid plans below remove the 30-min session limit. Nothing else changes.
Unlimited time, billed weekly. Cancel in one click from the billing portal.
Unlimited time. Save ~58% vs. monthly: one charge a year, nothing else to think about.
Unlimited time, billed monthly. Swap plans any time from freevpn manage.
Avoid broad promises on hosts you do not control.
freevpn doctor --json instead of guessing when a tunnel fails.freevpn down when your workflow requires cleanup.command -v freevpn >/dev/null 2>&1 && freevpn version --json.freevpn doctor --json and inspect the structured diagnostics.Check state, connect, verify, and diagnose from the terminal.