SSH VPN CLI

Use Free VPN CLI over SSH.

Free VPN CLI can fit SSH workflows when the remote machine allows VPN tunnel and route changes. Keep the flow explicit: check status, connect carefully, verify, and run doctor diagnostics when something looks blocked.

SSH Headless JSON output Careful routing
#1 Free VPN
100M+
Installs worldwide
10+ yrs
Battle-tested VPN core
1,000+
Servers · global exits
SSH setup

Preflight before touching VPN state over SSH.

SSH sessions need careful handling. Verify the binary and current state before connecting, and be mindful of routing on remote hosts.

SSH-safe preflight

Check install and state first. Connect only on hosts where VPN tunnel permissions are allowed.

Paste in Terminal
$command -v freevpn >/dev/null 2>&1 && freevpn version --json
$freevpn status --json
$freevpn doctor --json
Support notes
  • Use only on hosts where VPN tunnels and route changes are allowed.
  • Be careful not to disrupt your SSH path.
  • Verify with freevpn status --json after connecting.
  • Use freevpn down when the workflow requires cleanup.
Runs where your work already lives

VPN control inside SSH and server workflows.

Use terminal commands for remote development, server checks, and diagnostics.

SSH shell

Operate the VPN from the remote terminal.

Servers and VMs

Use where tunnel permissions are available.

JSON output

Log status and doctor output in a parseable format.

Route awareness

Check state before and after connection changes.

Two lines and you're connected

Preflight, then connect carefully.

Do not start with a blind connect on a remote host. Check state first.

Paste in Terminal
$freevpn status --json
$freevpn up --json

If behavior changes unexpectedly, use freevpn doctor --json and disconnect with freevpn down if needed.

How it works

up. status. down.

Three verbs cover most day-to-day VPN work. set-region and doctor cover region selection and troubleshooting.

1 Check where you are · connect
2 Switch region · verify · disconnect
SSH workflow

Check, connect, verify, clean up.

A careful SSH workflow keeps VPN actions visible and reversible.

Paste in Terminal
$freevpn status --json
$freevpn up --json
$freevpn status --json
$freevpn doctor --json
$freevpn down
CommandWhy it matters
freevpn status --jsonCheck current state before changing network behavior.
freevpn up --jsonConnect and keep output structured.
freevpn doctor --jsonDiagnose DNS, route, controller, license, or egress problems.
freevpn downRestore VPN state when cleanup is required.
Features

SSH-relevant CLI features.

Remote terminal workflows need visible status, structured output, and diagnostics.

Terminal-only control

No desktop window is required over SSH.

JSON output

Use parseable status and doctor output.

Doctor diagnostics

Collect structured evidence before guessing.

Route visibility

Verify current state before relying on the tunnel.

Ad Block

Use DNS-level blocking while connected.

Agent-readable docs

Use SKILL.md for command guidance.

Ad Block

Use Ad Block in SSH-driven workflows.

When the VPN is connected, Ad Block can apply to command-line tools and services that use the host network path.

  • Blocks known ad, analytics, and tracker domains across the device.
  • Works at the VPN layer, so it helps outside the browser too.
  • Use stats to inspect what was blocked during the current VPN session.
Optional desktop app

The CLI stays primary; the desktop app is optional.

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.

Paste in Terminal
$freevpn gui install
$freevpn gui open
$freevpn gui uninstall
Agent Skill

Give VPN commands to coding agents.

SKILL.md documents Free VPN CLI commands, JSON output, exit handling, and troubleshooting flows so agents can use terminal commands without guessing from screenshots.

Works with Claude Cursor Codex OpenClaw Hermes+ any MCP tool
Built for

Remote workflows that need VPN control.

Use Free VPN CLI carefully when SSH, server, or headless tasks need VPN state.

Remote machines

Use only where tunnel permissions are allowed.

SSH users

Keep commands visible and reversible.

Scripts

Parse JSON output instead of terminal text.

Troubleshooting

Run doctor for evidence.

Pricing

Free forever. Upgrade only if you want it.

Free VPN CLI is genuinely free to use: no signup, no email, no credit card. Use it for SSH and headless workflows on machines you control. The paid option removes the continuous connection limit for people who want the VPN running all day. Cancel any time. Prices in USD.

Always free

Free plan — $0 forever

No signup. No card. No expiry. Use it as much as you want.

  • 30-min sessions with a 3-min break in between, on repeat, forever.
  • Same servers, regions and Ad Block as the paid plan.
Install free

Need the VPN running non-stop?

The paid plans below remove the 30-min session limit. Nothing else changes.

Weekly
$7.99/wk

Unlimited time, billed weekly. Cancel in one click from the billing portal.

Get unlimited
Monthly
$21.99/mo

Unlimited time, billed monthly. Swap plans any time from freevpn manage.

Get unlimited
Payments handled by Stripe Cancel anytime No email required for billing
Practical notes

SSH safety notes.

VPN changes can affect remote networking, so keep the flow explicit.

  • Verify SSH access assumptions before connecting.
  • Use freevpn status --json before and after freevpn up --json.
  • Use freevpn down when cleanup is required.
  • Use freevpn doctor --json instead of guessing at route or DNS failures.
FAQ

VPN CLI over SSH FAQ.

Can I use Free VPN CLI over SSH?
Yes, on machines where VPN tunnel and route changes are allowed. Be careful to avoid disrupting your SSH path.
What should I run first over SSH?
Run freevpn status --json before changing VPN state.
Does SSH require the desktop app?
No. SSH workflows should stay terminal-first.
How do I troubleshoot a remote VPN issue?
Run freevpn doctor --json and inspect the structured diagnostics.
Can I disconnect from SSH?
Yes. Use freevpn down when your workflow requires cleanup.

Use Free VPN CLI carefully over SSH.

Check status, connect only where allowed, verify, and diagnose from the terminal.