Skip to content

v1.34.1 - Auto Deploy Through Existing Proxies

Choose a tag to compare

View all tags
@stoicsoft stoicsoft released this 22 Jul 09:10
v1.34.1
e53f3d0
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Improvements

servercompass-1 34 1-docker-proxy-gateway-access servercompass-1 34 1-docker-proxy-readiness-check

Auto Deploy Through Existing Proxies

  • 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

Server-Side Service Upgrades

  • 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

  • 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”
Assets 18
Loading