Skip to content

Connectivity

Private Locations Availability & Connectivity

Does the Private Location Restart Automatically if It Disconnects?

The agent retries its SSH connection when it disconnects. Docker Compose's restart: always restarts a container only after its process exits. It doesn't restart a running container just because the location is disconnected.

The Helm chart combines a scheduled 24h restart with a liveness probe. For Docker Compose and other custom deployments, set HEALTH_CHECK_PORT, monitor /health, and restart the container if it reports 503. See Environment Variables.

Does the Private Location Turn Off After a Period of Inactivity?

No, the Private Location remains active indefinitely as long as it maintains connectivity to the Escape platform. The service continuously sends heartbeat signals to the Escape platform at regular intervals (every 5 seconds) to maintain its connection status and ensure availability for incoming scan requests.

The Private Location doesn't stop when it loses network connectivity. It keeps retrying until it reconnects. It stops only if it's explicitly terminated or reaches its configured restart interval. Helm configures a 24h restart interval by default.

What type of traffic goes through port 80?

The current escape-cli Private Location agent connects to the Escape platform exclusively over the SSH tunnel on port 2222 (see Firewall Configuration). It does not use port 80.

A port 80 fallback existed only in the legacy Repeater deployments and is no longer part of the modern CLI agent, so there is nothing to disable. All Private Location traffic routes through the secure SSH channel on port 2222.

Troubleshooting

If connectivity issues are experienced or troubleshooting is needed for a Private Location, the following steps should be followed:

  1. Verify deployment configuration: The deployment configuration should be checked to ensure the API key is correctly set and has not expired
  2. Review firewall settings: Firewall settings should be verified to allow the necessary outbound connections to the Escape platform
  3. Check SSL/TLS configuration: The SSL/TLS configuration should be reviewed to ensure certificates are valid and properly configured for secure connections
  4. Analyze logs: Logs should be monitored and analyzed using the logging and monitoring tools to identify specific error patterns or connection issues
  5. Contact support: If issues persist after following the above steps, the support team should be contacted with relevant log excerpts and configuration details for further assistance