> 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/gateway/getting-started/devolutions-server/devolutions-gateway-configuration-with-devolutions-server.md).

# Devolutions Gateway configuration with Devolutions Server

This topic describes how to configure Devolutions Server to connect with Devolutions Gateway. There are three ways to install a Devolutions Gateway: the ***Side-by-side installation***, the ***Standard (managed) installation***, and the ***MSI installation***.

{% hint style="warning" %}
If your clients fail to connect with Devolutions Gateway, ensure the certificate contains the entire chain. This certificate chain includes any intermediate certificates. For example: Root Certificate Authority – Secure Certificate Authority – Purchased XYZ Certificate

Additionally, to [Launch an RDP session](https://docs.devolutions.net/gateway/kb/how-to-articles/launch-rdp-session-web-client/) with Devolutions Gateway only browsers that meet these minimal version requirements are compatible:

* Chrome: 102
* Firefox: 102
* Safari: 16.4
  {% endhint %}

## Installation types

The ***Side-by-side installation*** will be used if you need to install Devolutions Gateway on the same machine where Devolutions Server is hosted. It is a simplified installation process that will automatically configure the new Devolutions Gateway with information from the Devolutions Server instance (access URI and public key).

To install Devolutions Gateway on another machine than the one where Devolutions Server is hosted, you need to follow the ***Standard (managed) installation*** process. The procedure is similar, but you will need to provide more information about your Devolutions Server instance to complete it.

### Side-by-side installation

This installation process is the easier of the two and is the recommended method for simpler network layouts.

1. From the Devolutions Server Console, click on the ***Companions*** tab.

   ![](https://cdnweb.devolutions.net/docs/docs_en_server_ServerOp2083.png)
2. In the Devolutions Gateway section, click on ***Install***.
3. Choose ***Side-by-side installation***.

   ![](https://cdnweb.devolutions.net/docs/DVLSCONSOLE4047_2025_3.png)

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>It is possible to download an <a href="https://devolutions.net/gateway/download/">.msi</a> file to install Devolutions Gateway on an offline Devolutions Server.</p></div>
4. If default values do not work for your environment, enter the desired settings.
   * ***HTTP Listener***: HTTP(s) port to reach the Gateway. (7171 is default)
   * ***TCP Listener***: port used for the RDP sessions. (8181 is default)
5. Click ***OK***.

   ![](https://cdnweb.devolutions.net/docs/DVLSCONSOLE0003_2025_1.png)
6. Go to the Devolutions Server web interface, connect with an administrator account.
7. Go to ***Administration*** – ***Devolutions Gateway***.
8. Click on the ***Ping*** button for the desired gateway in the list to see if a connection can successfully be made. If the page was already open, refresh it first.

   ![](https://cdnweb.devolutions.net/docs/DVLS0005_2025_1.png)

### Standard (managed) installation

The ***Standard (managed)*** method allows Devolutions Gateway to be installed on a separate server than Devolutions Server. It could be for performance purposes or access networks that Devolutions Server cannot access.

1. From the Devolutions Server Console, click on the ***Companions*** tab.
2. In the Devolutions Gateway section, click on ***Install***.
3. Choose ***Standard installation***.

   ![](https://cdnweb.devolutions.net/docs/DVLSCONSOLE4046_2025_3.png)
4. Choose between ***Download version*** and ***Install from .msi file***.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>It is possible to download an <a href="https://devolutions.net/gateway/download/"><em><strong>.msi</strong></em></a> file to install Devolutions Gateway on an offline Devolutions Server.</p></div>
5. Click ***Next***.

   ![](https://cdnweb.devolutions.net/docs/DVLSCONSOLE0004_2025_1.png)
6. Enter the ***Access URI*** information, for example <https://gateway.example.com>.

   ![](https://cdnweb.devolutions.net/docs/DVLSCONSOLE0005_2025_1.png)
7. Choose the Devolutions Gateway ***Listeners*** ports (by default they are 7171 and 8181). Devolutions Server will use the Access URI port (usually 443 or 7171) for health checks and initial configuration. Remote Desktop Manager will use ports 7171 and 8181 to connect to the Gateway. For instance, a web session using the Gateway will connect on port 7171, as will any registration via Devolutions Gateway. Port 8181 is used by sessions such as RDP.

   * If HTTPS is chosen instead of HTTP in the step above, the ***Certificate configuration*** will be needed.
   * ***Certificate file***: Needs to be a full chain certificate (.pfx, .p12, .pem, .crt).
   * ***Certificate password***: Only needed if a .pfx or .p12 certificate was used.
   * ***Private key file***: Only needed if a .pem or .crt was used as a certificate.

   <div data-gb-custom-block data-tag="hint" data-style="danger" class="hint hint-danger"><p>Do not share the private key with other users, as it can be used to decrypt the communication between a user and Devolutions Gateway. Only the public key should be shared.</p></div>
8. Click ***Next***.
9. Choose between:

   * ***Use public key from*** Devolutions Server ***instance '***&#x44;evolutions Serve&#x72;***'***: this option is used if the installed Devolutions Gateway is on the same server as the Devolutions Server;
   * ***From file***: If installing Devolutions Gateway on another computer, download the public key from the Devolutions Server you want to pair with that Devolutions Gateway. It is located under ***Administration –*** Devolutions Gateway.

   ![](https://cdnweb.devolutions.net/docs/DVLS0007_2025_1.png)
10. Click ***Next***.

    ![](https://cdnweb.devolutions.net/docs/docs_en_server_ServerOp0011.png)

    <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>If Devolutions Server is not installed locally, then check the <em><strong>From file</strong></em> option, and select Devolutions Gateway's <code>.json</code> configuration file .See <a href="https://docs.devolutions.net/gateway/kb/how-to-articles/use-windows-certificate-store/#configuring-windows-certificate-store-via-gatewayjson">Configuring Windows certificate store via gateway.json</a> for a typical configuration file.</p><p><a href="https://github.com/Devolutions/devolutions-gateway/?tab=readme-ov-file#configuration">Devolutions' GitHub repository</a> also contains a list of the typical paths for the file, as well as all the stable options available to customize it.</p></div>
11. Click ***Install***.

    ![](https://cdnweb.devolutions.net/docs/docs_en_server_ServerOp0012.png)
12. Click ***Close***.

    ![](https://cdnweb.devolutions.net/docs/docs_en_server_ServerOp0013.png)
13. On the Devolutions Server web interface, connect with an administrator account.
14. Go to ***Administration*** – ***Devolutions Gateway***.
15. Click on the ***Add*** button on the top right corner.

    ![](https://cdnweb.devolutions.net/docs/DVLS0006_2025_1.png)
16. Enter the following information.
    * ***Name***: Name of the gateway that will be displayed in Remote Desktop Manager.
    * ***Description***: Description of the gateway.
    * ***Set as default***: If enabled, this gateway will be selected by default when configuring Remote Desktop Manager.
    * Devolutions Gateway ***URL***: The Devolutions Gateway URL and Port that Devolutions Server will connect to, for example: **<https://gateway.example.com:7171>**.
    * ***TCP Listening Port***: Set the port with the same TCP port value configured in the Devolutions Server Console.
    * ***TCP hostname***: It should be resolvable by the machine initiating the connection (Remote Desktop Manager).
17. Click ***Save***.

![](https://cdnweb.devolutions.net/docs/DVLS0008_2025_1.png)

The gateway should now be visible in the list. It is possible to verify the status of the gateway with the ***Ping*** button.

![](https://cdnweb.devolutions.net/docs/DVLS0005_2025_1.png)

18. Publish the Devolutions Gateway ***configuration***.
19. Publish the ***Revocation list***.

<figure><img src="https://cdnweb.devolutions.net/docs/DVLS6066_2025_3.png" alt=""><figcaption></figcaption></figure>

### Enable Gateway recording

Click [here ](https://docs.devolutions.net/server/kb/how-to-articles/configure-recording-server/)to learn how to enable Devolutions Gateway recording in Devolutions Server.

#### MSI installation <a href="#msi-installation" id="msi-installation"></a>

It is possible to do an automated silent installation which will install a gateway with the default configuration. This is the recommended way to configure it through the [Devolutions.PowerShell module](https://docs.devolutions.net/powershell/gateway-powershell/). Use the following command:

```
msiexec.exe /i DevolutionsGateway-x86_64-VERSION.msi /quiet /norestart /log gateway_install.log
```

#### Update Devolutions Gateway <a href="#update-devolutions-gateway" id="update-devolutions-gateway"></a>

Devolutions Gateway can be updated in three different ways depending on your needs:

* Push updates via Devolutions Server web interface, in ***Administration*** – Devolutions Gateway. Using this method, instances can be updated singly or in bulk. The latter can be done quickly by toggling the ***Bulk update*** option, selecting the gateways, and clicking on ***Update***. Note that [Devolutions Agent](https://devolutions.net/agent/) is required to update from the Devolutions Server web interface.
* Update manually through the Devolutions Server Console. To do so, head over the ***Companions*** tab, select the Devolutions Gateway to update, click the ***Update*** button, and follow the instructions then provided.
* Run the [auto-updater PowerShell script](https://docs.devolutions.net/powershell/gateway-powershell/powershell-updater/). This can be registered as a scheduled task to periodically check for updates.

### See also

* [Devolutions Academy - Overview of Devolutions Gateway](https://academy.devolutions.net/student/path/2007290/activity/3070847)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.devolutions.net/gateway/getting-started/devolutions-server/devolutions-gateway-configuration-with-devolutions-server.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.