vpn

Orchestrate VPN fleet deployment and client management across Ubuntu hosts.

16|1|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/seb0ch/vpn --skill vpn-seb0ch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vpn
Source: https://github.com/seb0ch/vpn/tree/main/.claude/skills/vpn
Command: npx skills add https://github.com/seb0ch/vpn --skill vpn-seb0ch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Operates and maintains a multi-host VPN stack (AmneziaWG + Xray REALITY + dnscrypt-proxy) across remote servers, automating deployment, status checks, client management, and topology changes.

Core Features & Use Cases

  • Deploys and redeploys a VPN fleet on multiple Ubuntu hosts.
  • Adds/removes VPN clients and configures cross-server routing for clients.
  • Verifies health, status, and integrity after each operation; supports tear-down and kernel module rebuilds.

Quick Start

Deploy a VPN fleet to a new Ubuntu host and add a client.

Frequently Asked Questions about vpn

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy a self-hosted VPN fleet across multiple Ubuntu servers?

Deploy a self-hosted VPN fleet by orchestrating AmneziaWG, Xray REALITY, and dnscrypt-proxy across Ubuntu hosts using script-driven actions with post-operation verification. You need to resolve inventory from ~/.config/vpn/hosts.yml before deployment.

Can I add and remove VPN clients or route them between servers in a fleet?

Yes, you can add and remove VPN clients and configure cross-server routing within your VPN fleet. The orchestration process uses script-driven actions to manage client configurations and verifies health status after each operation.

Does VPN fleet orchestration require a specific inventory file format?

Yes, VPN fleet orchestration requires an inventory file at ~/.config/vpn/hosts.yml. This YAML file resolves target Ubuntu hosts so the script-driven actions can execute deployments and client management across servers.

What is included in VPN fleet maintenance besides initial deployment?

VPN fleet maintenance includes re-deployments, adding or removing logins, cross-server client routing, health and integrity status checks, tear-downs, and kernel module rebuilds for AmneziaWG, Xray, and dnscrypt-proxy components.

Why does my VPN orchestration fail to verify status after a deployment?

VPN orchestration status verification fails if the script-driven actions cannot resolve the target hosts from ~/.config/vpn/hosts.yml or if the Ubuntu servers lack the required environment for AmneziaWG, Xray, and dnscrypt-proxy components.

What's the best way to tear down and rebuild VPN components across remote hosts?

The best way to tear down and rebuild VPN components is through fleet orchestration that applies script-driven actions across remote Ubuntu hosts, followed by post-operation verification to ensure stack integrity for AmneziaWG, Xray, and dnscrypt-proxy.