Simple Bridge Panel Offers Self-Hosted Management for Xray and AmneziaWG Connections
A developer tired of unreliable mass-market VPN services and the growing administrative burden of managing multiple personal VPS instances has created Simple Bridge Panel (SBP), a self-hosted web interface for controlling Xray and AmneziaWG connections.
After years of renting individual servers to avoid shared-IP fraud scoring by systems such as Scamalytics, the author found that manual configuration files multiplied quickly once family members and friends requested access. The resulting tool, also playfully called Suspiciously Big Pizza, installs on a fresh Ubuntu 24.04 amd64 server and centralizes deployment, user management, and traffic accounting behind a single interface.
Supported connection types
SBP currently offers three primary protocols. Xray TCP uses VLESS over TCP with REALITY and XTLS Vision on port 443. Xray XHTTP runs in a separate container and has demonstrated higher throughput in the author’s tests. AmneziaWG provides a stable UDP-based WireGuard-compatible tunnel using amneziawg-go inside Docker. Additional whitelist-bypass routes based on work by kulikov0 are also supported for networks that filter UDP.
The interface displays groups, devices, server status, component health, and traffic statistics on a single screen. Each group can be assigned an expiration date; when the date passes, the panel automatically adjusts the corresponding container configurations and routing rules.
Architecture and security considerations
The application is split into an unprivileged web frontend and a local agent that executes only pre-approved operations over a Unix socket. State is stored in SQLite, and runtime changes to Xray are applied via its API rather than container restarts. Update verification includes SHA-256 checks and automatic rollback if the new version fails health checks. Historical logs and traffic archives are deliberately minimized; only the current calendar month’s data is retained.
The project is limited to clean Ubuntu 24.04 installations to reduce the chance of conflicting with existing Docker setups, sysctl rules, or third-party containers. Source code is available under the Apache 2.0 license at the official GitHub repository.
Related articles
Corporate Boomerang: WordPress Founder Matt Mullenweg Survives Board Coup at Automattic
Automattic experienced a rapid corporate power struggle when its board placed founder and CEO Matt Mullenweg on forced paid leave. Within two days Mullenweg regained control by leveraging his shareholder voting rights and removed opposing administrators from the company Slack. The original board members who supported his ouster are now departing the company. The brief conflict highlighted how corporate governance rules allowed shareholders to ultimately determine board composition. Mullenweg described his restored position as that of a pirate before announcing renewed alignment with the board. Public support from WordPress leadership helped solidify his return to leadership.
Russian Transport Ministry Ready to Provide Regulatory Framework for Poplar Fluff Vacuum Robots
The Russian Ministry of Transport has signaled readiness to develop necessary regulations if municipal services express interest in specialized robots designed to collect poplar fluff from city streets. The statement from Minister Andrey Nikitin follows a viral meme that originated from a two-year-old video created by the agency Out Digital. Although no real machines called пухосос exist and no serial production has been launched, the fictional concept gained widespread attention after being presented as an actual Moscow development. The Department of Housing and Utilities in Moscow playfully expanded the joke by introducing additional fictional devices named Zasosyor, Musorozhor, and Gazonyukh. Linguistic experts at Gramota.ru later analyzed the newly coined term, further amplifying the meme's reach across Russian media and social networks. The minister emphasized that any future regulatory support would depend entirely on demand from communal services rather than proactive development by the ministry itself.
Context is Everything: How to Avoid Drowning in Security Incidents and Distinguish Employees from Attackers
The article explains that false positives in security systems often stem from missing business context rather than technical flaws. It outlines three levels of filtering that combine process rules, access logs, and job-specific behavior to rank risk accurately. Behavioral analysis tools like UEBA can help but require proper training and human oversight to avoid generating more noise. Key metrics focus on reducing false alerts, improving MTTD and MTTR, and minimizing daily administration time. For smaller companies without dedicated SOC teams, the guidance emphasizes starting with log collection, identifying existential risks, and aligning policies with real business processes. The piece stresses that technology alone cannot replace analysts who deeply understand company operations.
redb 4.0 Released: XML Routes, Lazy References, Unique Keys and WS-Trust Across the Ecosystem
The redb ecosystem has delivered a major simultaneous release across all core components, bringing redb.Core, redb.Route, redb.Tsak and redb.Identity to version 4.0.0. The update introduces declarative XML routing, lazy object references, unique key constraints, and a full WS-Trust SOAP facade while closing multiple security issues reported through external audits and community feedback. Seventy-six NuGet packages, seven container images and platform archives for Windows and Linux are now available, with the Pro edition remaining free and license-free throughout the 4.x line. Significant internal changes include a unified expression language, support for modern data formats such as Protobuf and Avro, and improved handling of distributed caches and OpenTelemetry metrics. Security hardening covers header sanitization in all identity facades, consent-page protections, dashboard access controls and a switch to bcrypt password hashing. Existing clusters must be stopped before upgrade because mixed versions are not supported, and large databases require a maintenance window for schema changes and partial index creation.