Bug Report

I have had 2 gateways go down overnight during update installation. The servers are running Devolutions Gateway 2025.2.3-1 on Ubuntu 24.04. We have unattended upgrades enabled with needrestart, and needrestart deemed it necessary to restart the devolutions gateway service. The restart failed because the listening port was still in use. This morning I could immediately start the service again without having to kill any lingering process. It appears as if the gateway reported a stopped state too soon, so the start command was giving before it actually finished shutting down? Sep 24 06:04:09 devolutionsgw02 systemd[1]: Stopping devolutions-gateway.service... Sep 24 06:04:09 devolutionsgw02 devolutions-gateway[911]: 2025-09-24T04:04:09.008971Z INFO devolutions_gateway::service: Stopping gateway service Sep 24 06:04:19 devolutionsgw02 devolutions-gateway[911]: 2025-09-24T04:04:19.010468Z WARN devolutions_gateway::service: Termination of certain tasks is experiencing significant delays Sep 24 06:04:29 devolutionsgw02 devolutions-gateway[911]: 2025-09-24T04:04:29.011451Z WARN devolutions_gateway::service: Termination of certain tasks is experiencing significant delays Sep 24 06:04:39 devolutionsgw02 devolutions-gateway[911]: 2025-09-24T04:04:39.012837Z WARN devolutions_gateway::service: Terminate forcefully the lingering tasks Sep 24 06:04:39 devolutionsgw02 devolutions-gateway[911]: 2025-09-24T04:04:39.013276Z INFO devolutions_gateway: devolutions-gateway service stopping Sep 24 06:04:39 devolutionsgw02 systemd[1]: devolutions-gateway.service: Deactivated successfully. Sep 24 06:04:39 devolutionsgw02 systemd[1]: Stopped devolutions-gateway.service. Sep 24 06:04:39 devolutionsgw02 systemd[1]: devolutions-gateway.service: Consumed 58.644s CPU time, 79.4M memory peak, 0B memory swap peak. Sep 24 06:04:39 devolutionsgw02 systemd[1]: Started devolutions-gateway.service. Sep 24 06:04:39 devolutionsgw02 devolutions-gateway[48534]: 2025-09-24T04:04:39.046607Z INFO devolutions_gateway::service: version="2025.2.3" Sep 24 06:04:39 devolutionsgw02 devolutions-gateway[48534]: 2025-09-24T04:04:39.048196Z INFO devolutions_gateway::service: XMF native library loaded and installed path=/usr/lib/devolutions-gateway/libxmf.so Sep 24 06:04:39 devolutionsgw02 devolutions-gateway[48534]: 2025-09-24T04:04:39.048672Z INFO devolutions_gateway::service: Reading JRL file from disk (path: /etc/devolutions-gateway/jrl.json) Sep 24 06:04:39 devolutionsgw02 devolutions-gateway[48534]: 2025-09-24T04:04:39.049560Z INFO devolutions_gateway::listener: Initiating listener... url=tcp://0.0.0.0:8181 Sep 24 06:04:39 devolutionsgw02 devolutions-gateway[48534]: 2025-09-24T04:04:39.049611Z INFO devolutions_gateway::listener: Listener started successfully kind=Tcp addr=0.0.0.0:8181 Sep 24 06:04:39 devolutionsgw02 devolutions-gateway[48534]: 2025-09-24T04:04:39.049622Z INFO devolutions_gateway::listener: Initiating listener... url=https://0.0.0.0:7171/ Sep 24 06:04:39 devolutionsgw02 devolutions-gateway[48534]: 2025-09-24T04:04:39.050019Z ERROR devolutions_gateway: Failed to start error="failed to bind listener: failed to initialize https://0.0.0.0:7171/: failed to bind TCP socke> Sep 24 06:04:39 devolutionsgw02 systemd[1]: devolutions-gateway.service: Deactivated successfully.

I deployed a devolutions gateway as a POC for our high security environments. We have been long time users of RDM and DVLS and have a number of existing connections that are configured as "Host" connections that leverage assigned templates. [image] When the connection is reconfigured to use the Gateway, it immediately fails with the error message stating that the "Host" Connection type is unsupported. In reality, I'm not trying to launch a "Host" connection, I'm launching an SSH or a Web session using information from the Host entry. [image]

I have just upgraded DVLS to the latest and greatest, as I were a bit behind. I the also installed the GW alongside DVLS as I have some servers in a locked off VLAN, where GW would be the perfect solution. My folder structure is: Server1 (A folder of type Server) where I define the hostname of the server. -- RDP (More or less everything set to inherit. This results in the following connection in the DVLS Administration page: [image] And all my RDP connections battle over connecting to the DVLS/DVGW itself. If I type in the host directly in the RDP session it works as expected.

Hello, When attempting to connect to a Windows 11 (24H2) machine via Devolutions gateway (2025.1.4) installed on Windows server 2022, the connection fails. The gateway log file reports "An existing connection was forcibly closed by the remote host. (os error 10054)", and the event log on the Win11 computer reports "An TLS 1.3 connection request was received from a remote client application, but none of the cipher suites supported by the client application are supported by the server. The TLS connection request has failed. The SSPI client process is svchost[TermService] (PID: 1400)." Opening an RDP connection on the Gateway server and connecting to the same Win11 machine works fine. Wondering if there is a TLS 1.3 cipher suite required by Win11 RDP that is currently unsupported by the Gateway software? TLS Cipher Suites in Windows 11 v22H2 and later. - Win32 apps | Microsoft Learn System requirements for Devolutions Server - Devolutions Documentation Also noticed that there is a 'maximum TLS version' property on the RDP entry in RDM, but it is greyed out unless the FreeRDP protocol is selected. However when I tried changing to FreeRDP and setting max TLS version to 1.2, when launching the connection it says unable to connect to the gateway so not sure if FreeRDP is compatible with gateway connections. Please let me know if you would like any additional info. Thanks Joe