VPN Coordinator — First Run Setup

The coordinator is not fully configured yet. Copy the generated values below into your .env file, then restart the container.

Generated values

These are generated fresh on every page load. Use them once — regenerate if needed.

Used for JWT signing and private-key encryption. Set once — never change it after first run.

Also set in .env
ADMIN_PASSWORD=your-chosen-password
WG_SERVER_PUBLIC_IP=your-vps-public-ip
Remote Nodes
▸ How to deploy an agent on a remote node
1. Prepare the host (Ubuntu / Debian)

Install WireGuard and enable IP forwarding — required before starting the agent container:

sudo apt install wireguard
sudo modprobe wireguard
echo wireguard | sudo tee /etc/modules-load.d/wireguard.conf

sudo sysctl -w net.ipv4.ip_forward=1
echo "net.ipv4.ip_forward=1" | sudo tee /etc/sysctl.d/99-vpn-agent.conf
2. Start the agent

For mass deployment with a shared enroll token — use the Deploy button on each node row for per-node commands.

docker run -d \
  --name vpn-agent \
  --restart unless-stopped \
  --network host \
  --pid host \
  --privileged \
  -v /lib/modules:/lib/modules:ro \
  -e COORDINATOR_URL=https://vpnhub.c2iapp.link \
  -e ENROLL_TOKEN=loading… \
  569234188113.dkr.ecr.us-east-2.amazonaws.com/vpncoordinator:agent-lts

Loading…

VPN Operator Devices
▸ How to use the downloaded config file
Windows
  1. Download and install WireGuard for Windows.
  2. Open the WireGuard app.
  3. Click Import tunnel(s) from file and select the downloaded .conf file.
  4. Click Activate to connect.
Ubuntu / Debian
  1. Install WireGuard:
    sudo apt install wireguard
  2. Copy the config:
    sudo cp username.conf /etc/wireguard/wg0.conf
  3. Connect:
    sudo wg-quick up wg0
  4. Auto-start on boot:
    sudo systemctl enable wg-quick@wg0

Loading…

Live VPN Status

Loading…

Operations
Backup

Export all nodes and users to a JSON file. Includes decrypted WireGuard private keys — keep the backup file secure. Use to migrate to a new VPS without re-deploying agents.

Restore

Restore from a backup file. The database must be empty (no existing nodes or users) — delete all records first if needed. This operation cannot be undone.

Audit Log

Record of all management actions (most recent first).

Click Refresh to load.

Current Focus
Change Focus

While focused on a node, traffic to that site's real LAN IPs routes directly instead of through the translated subnet.

No active nodes are available yet.

Clearing focus switches you back to translated subnet access for all sites.