VPN Admin Evolves from AmneziaWG Panel to Visual VPN Infrastructure Management Tool
VPN Admin has evolved from a narrow-purpose panel built for AmneziaWG into a full-featured visual platform for managing complex VPN infrastructures across multiple protocols.
The original awg-admin tool was created to test application deployment and remote server management using AmneziaWG as a realistic scenario. Over time the project outgrew its single-protocol design. The updated vpn-admin introduces generalized abstractions: servers, network interfaces or logical listeners, provider resources, users with their connections, directed links between interfaces, and VPN services as configurable applications.
The core no longer needs to understand the internal details of Xray, Hysteria 2, or future providers. It stores inventory and desired state, renders topology, coordinates installation, and delegates protocol-specific work to providers.
New Deployment Mechanism
Installation now uses a standardized entry point: vpn-provider-<name> deploy --config <file>. Each provider installs its own core and dependencies, registers with the agent, and manages its resources independently. The persistent component on managed servers is vpn-agent, which runs providers as child processes and exposes an API to the admin interface. Systemd manages only the agent; individual VPN services do not require separate unit files.
Dynamic Configuration Forms
Providers supply manifests containing JSON Schema definitions for their resources. The admin interface uses React JSON Schema Form to render protocol-specific forms on demand. Cached schemas allow the interface to remain functional even when a server is temporarily unreachable.
Supported Providers
- AmneziaWG / WireGuard – kernel and userspace modes, Amnezia obfuscation, import of existing wg-quick configurations, traffic metrics, and tunnel links.
- Xray – VLESS over TCP or WebSocket with TLS, per-user UUIDs, and VLESS URI generation with QR codes.
- Hysteria 2 – QUIC/UDP listeners with username-password authentication and hysteria2:// URI creation.
Both proxy listeners and traditional network interfaces appear as nodes in the visual editor, allowing mixed-protocol chains.
Visualization and Routing
The geographic map displays server locations using city names resolved against a local Data Center Atlas cache or manual coordinates. Color-coded markers indicate agent reachability and resource health. Tunnels are shown with arrows whose color reflects p95 latency over a sliding 15-minute window.
The Network Graph supports directed multi-hop routes of arbitrary length. Links are established through a prepare-commit handshake coordinated by the admin interface. Mixed chains such as Xray → AWG → Hysteria 2 are possible because each node can act as a protocol connector using SOCKS5 or policy routing.
Extensive end-to-end tests cover five-server Xray chains, five-server Hysteria 2 chains, and an eight-server mixed chain containing fourteen endpoints and thirteen links, all verified with real HTTP traffic.
The project is available on GitHub under the Apache 2.0 license with desktop builds, a Docker image, and installation instructions.
Related articles
Windows and MacBook Pro Setup Combines Local Network Access with Dual VPNs and Kill Switch Protection
A user detailed how they integrated an older MacBook Pro into an existing Windows workstation environment while preserving separate user accounts, file sharing, and independent VPN connections. The setup required careful routing configuration to keep the Kill Switch active on both Amnezia VLESS and AmneziaWG without breaking local SMB connectivity. After initial failures caused by the Windows Kill Switch blocking the 192.168.1.0/24 subnet, split tunneling was implemented to route local traffic directly. Separate macOS accounts were created for daily use and a dedicated “Serverok” account for remote scripting and compute tasks. SSH and SFTP ultimately replaced problematic SMB shares for the secondary account, enabling reliable file transfers at over 50 MB/s. The configuration allows simultaneous or sequential use of both machines while maintaining strong VPN protection on each.
RuCenter Prepares DNS Guard Launch for Early Cyber Threat Detection
RuCenter is developing DNS Guard, a new system designed to detect cyber threats at the DNS level before they cause disruptions to websites and corporate services. The tool will combine DNS traffic analysis, monitoring of domain record changes, and validation of DNS zone configurations. According to RuCenter’s 2026 research, 53.4% of companies experienced domain-related incidents, while only 31.5% maintain formalized domain management policies. DNS Guard will track suspicious changes to records affecting websites and email, identify forgotten subdomains vulnerable to takeover, detect anomalous queries, audit zone settings, and send alerts on critical events. The system leverages RuCenter’s own DNS infrastructure to spot recurring anomalies across multiple zones and targets medium and large enterprises managing numerous domains, with planned API integration for corporate security platforms.
Rostelecom Suffers Mass Outage Disrupting Website, Mobile App and Personal Account
Rostelecom experienced a significant service disruption that left its official website, mobile application, and customer personal account either unavailable or functioning with errors. The first reports of problems began arriving around 12:40 Moscow time. Over a 24-hour period, the monitoring service Detector404 recorded approximately 2,500 user complaints. The largest share, 59 percent, originated from the Nizhny Novgorod region, followed by 4 percent from Kursk region and 2 percent each from Ryazan and Ivanovo regions. Rostelecom has not issued any official statement regarding the incident, and the root cause along with the timeline for full restoration remain unknown. The outage occurred in the same week that hosting provider ESTT suffered a similar infrastructure failure.
Russian State Duma Rejects Bill Proposing Fines for Covering Face in Public
On November 11 the State Duma rejected bill No. 1159193-8 that sought to introduce a new article in the Code of Administrative Offenses punishing appearance in public places with a face covered in a way that prevents identification. The draft included exceptions for medical reasons, official duties, weather conditions, and sports or cultural events. Two committees of the Federation Council on defense and security as well as constitutional legislation opposed the measure. The Duma committee on criminal and administrative legislation found the wording too vague and lacking legal certainty. It also noted that new offenses require prior federal-law prohibitions. On the same day lawmakers rejected another bill introducing criminal liability for crimes committed with deepfakes.