Currently, PasarGuard operates as a single-instance deployment — if the host machine goes down, the entire system (panel + subscription endpoints) becomes unavailable. There's no built-in mechanism to run a standby panel instance that can take over automatically.
What I'm requesting:
- Support for running PasarGuard in an active-passive or active-active HA setup across multiple hosts
- At minimum: a documented way to replicate panel state (PostgreSQL data, config) to a standby instance with automatic or semi-automatic failover
- Ideally: a shared/external DB configuration option so multiple panel instances can point to the same database, with a load balancer or floating IP handling traffic routing
The xray-core nodes themselves are stateless and survive panel downtime fine — the critical point of failure is the panel host. For a production VPN service, panel downtime directly affects subscription validation and user access.
Is this on the roadmap? If there's already a supported workaround or recommended architecture for HA deployments, I'd appreciate the details.
Currently, PasarGuard operates as a single-instance deployment — if the host machine goes down, the entire system (panel + subscription endpoints) becomes unavailable. There's no built-in mechanism to run a standby panel instance that can take over automatically.
What I'm requesting:
The xray-core nodes themselves are stateless and survive panel downtime fine — the critical point of failure is the panel host. For a production VPN service, panel downtime directly affects subscription validation and user access.
Is this on the roadmap? If there's already a supported workaround or recommended architecture for HA deployments, I'd appreciate the details.