Reverse Proxy - Multiple Instances (#620)

This commit is contained in:
shuuri-labs
2026-02-19 13:14:43 +01:00
committed by GitHub
parent 5c059fa7b8
commit d49f899db1
4 changed files with 314 additions and 15 deletions

View File

@@ -152,7 +152,7 @@ Static certificates support hot-reload through file watching. When the certifica
### High availability
Multiple proxy instances configured with the same `NB_PROXY_DOMAIN` value form a single proxy cluster. This provides high availability - if one instance goes down, the remaining instances in the cluster continue serving traffic. Each instance independently connects to the management server via gRPC and registers under the shared cluster address.
For self-hosted deployments, multiple proxy instances configured with the same `NB_PROXY_DOMAIN` value form a single proxy cluster, providing automatic failover. See [Running Multiple Proxy Instances](/selfhosted/maintenance/scaling/multiple-proxy-instances) for setup instructions covering token management, TLS certificates, and monitoring across instances.
### Traefik requirement
@@ -275,6 +275,7 @@ The Networks page also displays a badge on each resource indicating how many rev
## Related pages
- [Multiple Proxy Instances](/selfhosted/maintenance/scaling/multiple-proxy-instances) - deploy multiple proxy instances for high availability and redundancy
- [Custom Domains](/manage/reverse-proxy/custom-domains) - configure your own domain names for reverse proxy services
- [Authentication](/manage/reverse-proxy/authentication) - detailed guide on SSO, password, and PIN authentication options
- [Access Logs](/manage/reverse-proxy/access-logs) - monitor and audit traffic to your reverse proxy services