Back to all features
Remote connectivity

Proxies and Jump Servers

Reach a target Host through a proxy or SSH jump server

Overview

Edit a Host and configure a proxy or jump server under Advanced Settings to connect through an intermediate network entry point.

Use a proxy

  • HTTP CONNECT and SOCKS5 proxies are supported.
  • A proxy can require no authentication or use its own username and password.
  • When both a proxy and jump server are configured, the proxy carries the connection from the phone to the jump server, which then connects to the target Host.

Use a jump server

  • SSH tunnel: Redock signs in to the jump server, opens a tunnel to the target, and authenticates the target Host in the app. Prefer this mode to retain full terminal, SFTP, Agent Chat, and Web Preview capabilities.
  • Jump server SSH config: after Redock signs in to the jump server, its SSH client connects to the target. Use this for Host aliases, keys, or special login settings stored on the jump server. Runs, Git Changes, and port forwarding are limited in this mode.
  • The jump server can reuse the target Host credentials or have its own username, password, or SSH key.

Keep in mind

  • Proxies and jump servers work with SSH only. They cannot be combined with Mosh or embedded Tailscale.
  • SSH tunnel mode requires the jump server to allow TCP forwarding to the target Host.
  • For jump server SSH config mode, first ensure the jump server can connect to the target non-interactively and complete host-key verification.

Put this feature into your mobile workflow

Steer terminal coding agents on your own host, right from your phone.