Repository navigation
Releases
VPN Admin v2.0.3
What's Changed
- fix(db): omit empty peer DNS from v2 resource specs migration by @ks-tool in #35
- fix(ssh): reset stale passphrases on credential changes by @ks-tool in #36
- fix(awg): include interface MTU in client configs by @ks-tool in #37
- fix(deploy): remove legacy provider listener configuration by @ks-tool in #39
- fix(peers): reserve gateway address for exit peers by @ks-tool in #42
- fix(sync): preserve provider-only peers during resync by @ks-tool in #43
Full Changelog: v2.0.2...v2.0.3
VPN Admin v2.0.2
What's Changed
Full Changelog: v2.0.1...v2.0.2
VPN Admin v2.0.1
VPN Admin v2.0.0
VPN Admin v2.0.0 is the first stable release of the redesigned provider-based architecture. The project evolves from an AmneziaWG-specific panel into a visual control plane for VPN infrastructure.
Highlights
Visual infrastructure management
- Geographic server map with locations, health statuses, clusters, and tunnels.
- Tunnel visualization with p95 latency over a sliding 15-minute window.
- Interactive Network Graph for connecting interfaces and listeners with directed links.
- Multi-server routes and visual rerouting of existing connections.
Multiple VPN providers
- AmneziaWG / WireGuard, Xray, and Hysteria 2 support.
- Mixed-protocol chains using local route connections between providers on the same host.
- Unified user management across servers and protocols.
- AWG client configurations and Xray/Hysteria 2 connection URIs.
Provider-driven configuration
- Providers expose resource manifests and JSON Schemas.
- Configuration forms are generated dynamically with React JSON Schema Form.
- Cached schemas remain available when a server is temporarily unreachable.
- New providers can be added without protocol-specific forms or deployment logic in the admin core.
Independent deployment
- Pack-based agent and provider deployment.
- Providers install and configure their own cores, dependencies, registrations, and firewall rules.
- Public and private OCI registries, local binaries, and local directories are supported.
- Agents and providers can be installed, updated, and removed independently.
- The agent supervises provider processes and persists desired resource state.
Migration and reliability
- Existing AWG configurations can be imported with preview.
- Improved cleanup for users, peers, interfaces, links, servers, and remote provider resources.
- Protocol-neutral health checks and detailed resource status reporting.
- Desktop and standalone web server modes share the same model and functionality.
Breaking changes
V2 replaces AWG-specific resource and deployment workflows with provider-managed resources. Some APIs and configuration formats differ from v1.
The v2 database is stored separately at ~/.vpn-admin/db. Migration from v1 is manual and leaves the source database unchanged.
Before upgrading, back up your existing installation and stop both applications. Then run:
awg-migrate v2By default, this migrates ~/.awg-admin to ~/.vpn-admin/db. After migration, review the imported resources and install the v2 agent and required providers through Manage panel → Agent.
AWG Admin v1.5.0
What's Changed
Full Changelog: v1.4.1...v1.5.0
AWG Agent v1.3.0
What's Changed
Full Changelog: v1.4.1...agent/v1.3.0
AWG Admin v1.4.1
What's Changed
Full Changelog: v1.4.0...v1.4.1
AWG Agent v1.2.1
What's Changed
Full Changelog: v1.4.0...agent/v1.2.1
AWG Admin v1.4.0
v1.4.0
New
- Import existing wg-quick / awg-quick interfaces (#8, #15). Interfaces brought up on a server before the agent was installed are now discovered and shown on the server page with a Not managed badge (read-only), and can be taken over with a one-off import:
- the agent reads the interface's conf from the server (
/etc/amnezia/amneziawg/<name>.conf, then/etc/wireguard/<name>.conf); the file is the source of truth; - a peer map (
user:/ indentedprivate-key: peer name) assigns the conf's peers to users — matched by exact name, created when missing; peers left out are imported without a user and keep working; - Preview dry-runs the import: interface, users (new / existing) and peers, the conf's hook commands, the hook commands the import generates (the routes wg-quick added implicitly, as idempotent
ip route replace/del … || truehooks, incl.Table = N), and warnings (non-idempotent hooks,DNSchanging meaning,SaveConfigignored, peers without keepalive, link-type mismatch, …); - the interface, users and peers are written in one transaction, then pushed to the agent like any other change; a live interface is adopted in place, a downed one is created.
- Creating or renaming an interface to the name of an unmanaged one is refused, since the push would overwrite the wg-quick link.
- Available from the agent dialog (Import interface) and from the unmanaged interface's card; hidden for a containerized agent. See the guide section "Importing a wg-quick / awg-quick interface" for the seamless vs. clean migration paths and the wg-quick unit clean-up.
- the agent reads the interface's conf from the server (
- Save client config to a file from the peer QR-code modal (#14): the same config the QR encodes can be saved as a ready-to-import
.conf(native save dialog on desktop, written0600; browser download on the web).
Requirements
- The import feature needs agent/v1.2.0 or newer on the server (new
/interfaces/unmanagedand/interfaces/{name}/import-sourceendpoints; agent/v1.2.0 also fixes device enumeration on amneziawg-dkms v3.0 hosts, #11). With an older agent the unmanaged list is simply empty and the import reports that the conf can't be read. - The admin now depends on the published
agent v1.2.0module.
AWG Agent v1.2.0
Companion release for the admin's wg-quick import (#8). Both awg-agent (kernel) and awg-agent-userspace are affected.
New
GET /interfaces/unmanaged— lists live WireGuard/AmneziaWG devices on the host that the agent has no stored config for (interfaces brought up bywg-quick/awg-quickor by hand), with the link kind (amneziawg/wireguard). Scanned on every request, so an interface raised after the agent started shows up without a restart. The admin uses it to show "Not managed" interfaces and to refuse creating a new interface under such a name.GET /interfaces/{name}/import-source— returns the host's wg-quick conf for the interface (/etc/amnezia/amneziawg/<name>.conf, then/etc/wireguard/<name>.conf) as{path, content};404when neither exists,400for a name that isn't a valid interface name. Read-only; the admin parses it and pushes the resulting config back through the usualPUT /interfaces, which adopts a live link in place.
Fixed
- amneziawg-dkms v3.0 hosts (#11):
wgctrlnow speaks the v3 netlink wire format (u32 keepalive, u64H1–H4), so device enumeration no longer fails on the first v3 device — this had broken per-peer metrics and orphan detection. The fix ships via theks-tool/wgctrl-gofork (pinned inagent/go.modandagent/e2e/go.mod). Note: dkms v3 does not acceptH1–H4ranges; pushing a config with ranges to a v3 host now fails with a clear error instead of a parse panic.
Compatibility
- Purely additive API; no config or storage format changes. An older admin keeps working against this agent, but the import feature in the admin requires this version or newer (it treats the
404from an older agent as "unknown"). - The literal path
/interfaces/unmanagedtakes precedence overGET /interfaces/{name}, so an interface literally namedunmanagedcan't be fetched by name.