Please enable JavaScript to view this site.

Devolutions Server Configuration


This topic describes how to configure Devolutions Server to connect on Devolutions Gateway.



1.From the Devolutions Server Console, click on the Companions tab and then Install the Devolutions Gateway.


2.You can either download the latest version, or retrieve the msi file from GitHub if you do not have Internet access.


3.You can then specify the configuration.


a.External URL: URL to reach the Devolutions Gateway from the RDM client. The port can be set as per your requirements, we will use 7171 since the Devolutions Gateway is installed on the same server as Devolutions Server.

b.HTTP Listener: HTTP(s) port to reach the Devolutions Gateway. If the Devolutions Gateway is placed behind a Load balancer, it can be set to use HTTP, if the Devolutions Gateway is directly accessible, you can (and should) specify an SSL certificate (see last section).

c.TCP Listener: port used for the RDP sessions, and eventually the SSH sessions.

d.Certificate configuration: required if the HTTP Listener is set to HTTPS.

4.If the Devolutions Gateway is installed on the same server as the instance of Devolutions Server, you can use the first option for the Key Pair.


If the Devolutions Gateway is installed on another server, you can download the Public Key from the web interface of Devolutions Server (Administration > Gateway).


5.Validate the information and click Install.


6.The Devolutions Gateway service will then be installed.


7.On the Devolutions Server web interface, connect with an administrative account.

8.Go in Administration - Gateway.



9.Click on the Add button on the top right corner.

Administration - Gateway

Administration - Gateway

10.Enter the following information.

a.Name : Name of the Devolutions Gateway that will be displayed in Remote Desktop Manager.

b.Description : Description of the gateway.

c.Set as default : If enabled, this gateway will be selected when configuring Remote Desktop Manager.

d.Devolutions Gateway URL : Use the same URL configured in the PowerShell script with Set-DGatewayHostname cmdlet (see above step 4).

e.TCP Listening Port: Set the port with the same TCP port value configured in the console

Gateway configuration dialog

Gateway configuration dialog

11.Click on Save.

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

Administration - Gateway

Administration - Gateway