Back to ChangelogDownload
v1.34.1July 22, 2026
Auto Deploy Through Existing Proxies
Auto Deploy now works through a reverse proxy you already run, and the deployment service can be upgraded from the server side.
Download v1.34.1
Get this version from GitHub Releases
What's Changed
Improvements
7- Choose where your proxy runs — tell Server Compass whether your existing reverse proxy or tunnel runs directly on the VPS or inside Docker
- Keep the safe local-only option for Nginx, Caddy, or tunnels running directly on the server
- Choose Docker access for Nginx Proxy Manager, Traefik, Caddy, or tunnel containers on a separate Docker network
- See the exact gateway address before activation — the readiness check now shows the address and port your proxy should use
- Review gateway access at a glance — the deployment service card shows the active gateway address and port alongside route and health details
- Get safer Docker setup guidance — a clear warning reminds you to restrict the gateway port to trusted proxy or Docker networks
- Keep existing services working during the update — Auto Deploy and monitoring setups move automatically to their consistent server location without losing their current configuration
Bug Fixes
1- Fixed Auto Deploy webhooks being unreachable from Docker-based reverse proxies — bridge-networked proxies such as Nginx Proxy Manager can now connect after you select “Proxy runs in Docker”
Screenshots
Related Resources
Templates
Video Tutorials
Technology Stacks
Related Topics
auto deployexisting proxydeployment service upgrade




