> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/rdm/knowledge-base/knowledge-base-articles/entry-settings/proxy-tunnel-vpn.md).

# Proxy tunnel (HTTP, SOCKS4, SOCKS4A, SOCKS5) (VPN)

Configure Proxy tunnel VPN entries in Remote Desktop Manager, including usage, proxy host and type, credentials, dynamic port, local and remote hosts.

This article details the many settings and options available for ***Proxy tunnel (HTTP, SOCKS4, SOCKS4A, SOCKS5)*** VPN entries in Remote Desktop Manager.

<table data-header-hidden><thead><tr><th width="200"></th><th></th></tr></thead><tbody><tr><td><strong>SETTINGS</strong></td><td><strong>DESCRIPTION</strong></td></tr><tr><td><strong>Name</strong></td><td>The name of the entry.</td></tr><tr><td><strong>Folder</strong></td><td>The folder where the entry is located.</td></tr><tr><td><strong>Display</strong></td><td>How the entry opens. VPN entries open as <em><strong>External</strong></em>, and the list cannot be changed.</td></tr><tr><td><strong>Host</strong></td><td>Where the host of the entry comes from. Select a host mode from the list. When the host does not come from the entry itself, the <em><strong>Host</strong></em> field of the <em><strong>Connection</strong></em> tab is unavailable.</td></tr><tr><td><strong>Credentials</strong></td><td>How the credentials of the entry are provided. Select a credential mode from the list. When the credentials do not come from the entry itself, the <em><strong>Username</strong></em> and <em><strong>Password</strong></em> fields of the <em><strong>Connection</strong></em> tab are unavailable.</td></tr><tr><td><strong>VPN type</strong></td><td>The type of VPN of the entry. <em><strong>Proxy tunnel (HTTP, SOCKS4, SOCKS4A, SOCKS5)</strong></em> is selected for this entry. Selecting another type replaces the settings of the <em><strong>Connection</strong></em> tab.</td></tr></tbody></table>

### Connection

<table><thead><tr><th width="220">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>Usage</strong></td><td><p>How the tunnel is used:</p><ul><li><strong>Default (Port forward)</strong></li><li><strong>Port forward</strong></li><li><strong>SSH shell</strong></li><li><strong>Website</strong></li></ul></td></tr><tr><td><strong>Host</strong></td><td>The host name or IP address of the proxy server, with its <em><strong>Port</strong></em>. The default port is 80 when <em><strong>Proxy type</strong></em> is set to <em><strong>HTTP</strong></em>, and 1080 for the other types. The host is required when the host comes from the entry itself, and the field is unavailable otherwise.</td></tr><tr><td><strong>Proxy type</strong></td><td><p>The protocol of the proxy server:</p><ul><li><strong>HTTP</strong></li><li><strong>HTTPS</strong></li><li><strong>Socks4</strong></li><li><strong>Socks4a</strong></li><li><strong>Socks5</strong></li></ul></td></tr><tr><td><strong>Username</strong></td><td>The username used to authenticate on the proxy server.</td></tr><tr><td><strong>Password</strong></td><td>The password used to authenticate on the proxy server. Unavailable when a policy disables password saving in vaults.</td></tr><tr><td><strong>Use dynamic port</strong></td><td>Use a dynamic local port for the tunnel. Visible only when <em><strong>Usage</strong></em> is set to <em><strong>Default (Port forward)</strong></em> or <em><strong>Port forward</strong></em>.</td></tr><tr><td><strong>Force "localhost"</strong></td><td><p>Whether the tunnel uses <code>localhost</code> with the dynamic port:</p><ul><li><strong>Default</strong></li><li><strong>Yes</strong></li><li><strong>No</strong></li></ul><p>Visible only when <em><strong>Usage</strong></em> is set to <em><strong>Default (Port forward)</strong></em> or <em><strong>Port forward</strong></em>, and available only when <em><strong>Use dynamic port</strong></em> is checked.</p></td></tr><tr><td><strong>Local host</strong></td><td>The local host name or address of the tunnel, with its <em><strong>Port</strong></em> (default port 80). Visible only when <em><strong>Usage</strong></em> is set to <em><strong>Default (Port forward)</strong></em> or <em><strong>Port forward</strong></em>. The host and the port are both required in that case.</td></tr><tr><td><strong>Remote host</strong></td><td>The destination host name or address reached through the proxy, with its <em><strong>Port</strong></em> (default port 1080). Visible only when <em><strong>Usage</strong></em> is set to <em><strong>Default (Port forward)</strong></em> or <em><strong>Port forward</strong></em>. The host and the port are both required in that case.</td></tr></tbody></table>

### Advanced

<table><thead><tr><th width="220">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>Go offline on connection</strong></td><td>Switch Remote Desktop Manager to offline mode when the VPN connects.</td></tr><tr><td><strong>Close connection after (min)</strong></td><td>Close the VPN automatically after the set number of minutes, from 0 to 4320. Check the option to enable the number field.</td></tr><tr><td><strong>Detect reachable host in wait</strong></td><td>While waiting for the VPN, detect whether the host can already be reached.</td></tr><tr><td><strong>VPN reconnect mode</strong></td><td><p>Select the reconnect behavior of the VPN:</p><ul><li><strong>Default</strong></li><li><strong>Reconnect VPN</strong></li><li><strong>Leave VPN open</strong></li></ul></td></tr><tr><td><strong>Go online on disconnect after (sec)</strong></td><td>Switch Remote Desktop Manager back to online mode the set number of seconds after the VPN disconnects, from 0 to 180.</td></tr><tr><td><strong>Use adapter to detect connection</strong></td><td>Use the network adapter to detect whether the VPN is connected.</td></tr></tbody></table>

**After execution, wait**

<table><thead><tr><th width="220">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>After execution, wait</strong></td><td><p>Select what Remote Desktop Manager waits for after the VPN is started:</p><ul><li><strong>Delay</strong> — wait the set number of seconds, from -1 to 180.</li><li><strong>For IP on adapter</strong> — wait for the network adapter to receive an IP address. Enter the adapter name or the device name, or leave the field blank. Click the browse button to select an adapter.</li></ul></td></tr><tr><td><strong>Wait a maximum of (sec)</strong></td><td>The maximum time to wait for the IP address, from -1 to 180 seconds. Visible when <em><strong>For IP on adapter</strong></em> is selected.</td></tr><tr><td><strong>Then delay (ms)</strong></td><td>An additional delay once the IP address is received, from -1 to 180000 milliseconds. Visible when <em><strong>For IP on adapter</strong></em> is selected.</td></tr></tbody></table>

**Commands**

<table><thead><tr><th width="220">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>Commands</strong></td><td>The list of VPN commands, with their <em><strong>Name</strong></em>, <em><strong>After connection command</strong></em>, and <em><strong>Before disconnecting command</strong></em>. Use the <em><strong>Add</strong></em>, <em><strong>Edit</strong></em>, <em><strong>Delete</strong></em>, <em><strong>Move up</strong></em>, and <em><strong>Move down</strong></em> buttons to manage the list. The commands are available only when <em><strong>After execution, wait</strong></em> is set to <em><strong>For IP on adapter</strong></em>, and are not supported on macOS.</td></tr><tr><td><strong>After connecting, VPN command enabled</strong></td><td>Run the after connection commands once the VPN is connected.</td></tr><tr><td><strong>Before disconnecting, VPN command enabled</strong></td><td>Run the before disconnecting commands before the VPN is disconnected.</td></tr><tr><td><strong>Run routes in batch (forces elevated privileges)</strong></td><td>Run the route commands together in a batch. This requires elevated privileges.</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.devolutions.net/rdm/knowledge-base/knowledge-base-articles/entry-settings/proxy-tunnel-vpn.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
