Support

Get help and support for Devolutions Gateway

avatar

jonasnijs

Configuration not in sync

[image] My gateway configuration is not in sync, and when i try to publish gateway configuration, i get a failed error. When i try to use this gateway to connect thru ssh to my server in the browser i also get an error: [image]

39

2

avatar

Tommy Sanders

avatar

pvansluisveld

Automatically Publish Gateway Configuration for DVLS Gateway in DVLS Server within Docker architecture

I'm running my Devolutions architecture in Docker. When I re-create my DVLS gateway docker container, for example when I'm updating the image version, I need to login to my DVLS server and manually browse to the specific DVLS gateway and click on the option "Publish Gateway Configuration". After this option my DVLS gateway is working again. My question: Is it possible to automatically run "Publish Gateway Configuration" for my DVLS gateway when I re-create the Docker container?

55

4

avatar

Benoit Cortier

avatar

juergengrabert

Gateway Revocation list is not in sync

Hello, we had to create new certificates for the gateway. These were signed by our CA. The Devolution servers are not in the domain, so we also had to store the root certificate locally. However, there is now a problem with the gateway. The gateway is not accessible via Administration > Dev Gateway > Diagnostics. It is running, though. The website (https) is also working. The gateway log on the gateway server shows the following message: "unauthorized at devolutions-gateway\src\middleware\auth.rs:189:28 [source: failed to verify token signature using main provisioner key, because signature error: invalid signature, because invalid signature]" Do the Provisioner.PEM and KEY files also need to be recreated? Regards, Jürgen

41

4

avatar

Richard Markiewicz

avatar

mlaffoon

DVLS Gateway - Failed to start error

Came in this morning to find both of our gateways offline, with the following message in the logs: 2026-02-03T12:59:25.114904Z ERROR devolutions_gateway: Failed to start error="failed to bind listener: tcp://REDACTED:8181 -> tcp://0.0.0.0:8181: failed to bind TCP socket: Address already in use (os error 98)" Any hints on where to look for the root cause? Thanks! Gateway Version ------------------------- devolutions-gateway_2025.3.3-1_amd64.deb System Info ------------------------- OS: Ubuntu 24.04.3 LTS x86_64 Host: VMware Virtual Platform None Kernel: 6.14.0-37-generic Uptime: 21 days, 16 hours, 18 mins Packages: 838 (dpkg), 5 (snap) Shell: bash 5.2.21 Resolution: 1280x768 Terminal: /dev/pts/0 CPU: Intel Xeon Gold 5220R (4) @ 2.194GHz GPU: 00:0f.0 VMware SVGA II Adapter Memory: 376MiB / 7941MiB

69

6

avatar

Benoit Cortier

avatar

pvansluisveld

Getting randomly GATEWAY_OFFLINE messages

Last week I implemented a new DVLS gateway farm with 2 DVLS gateways on Debian 13. My config: { "Id": "d174211d-2e50-4d30-93cb-bc0dfec5a595", "Hostname": "off-dvls-gw02.linux.interconnect.services", "ProvisionerPublicKeyFile": "provisioner.pem", "ProvisionerPrivateKeyFile": null, "TlsCertificateFile": "server.crt", "TlsPrivateKeyFile": "server.key", "Listeners": [ { "InternalUrl": "tcp://*:8181", "ExternalUrl": "tcp://*:8181" }, { "InternalUrl": "https://*:7171", "ExternalUrl": "https://*" } ] } 2 DVLS gateways are running without any issues and it its possible to connect with RDP and SSH. [image] For some reason I'm getting random GATEWAY_OFFLINE errors logs in my Devolutions Server. [image] In de attachment I added my gateway logs. I cannot find the issue, is there something I can do?

55

3

avatar

Richard Markiewicz

avatar

naratatianaaa

Multi Monitor Session Recording

Hello, Users want to be able to connect via RDP with dual screens. Looking at the documentation, it says the display mode should be set to external. When trying to connect, I get the error "The session requires session recording; it cannot be opened externally". I want to be able to connect with dual screens and also record the screen. Is such a feature available or is it included in your roadmap? Thank you.

98

4

avatar

Richard Markiewicz

avatar

markusburkhardt

Resolved Implemented

RDP-sessions are beeing terminated after a few seconds when opening them over DVLS in webbrowser

Hello members of the Devolution community, One of my DVLS-users reported to me that RDP-sesstions, which are opend in the Browser over our Gateway-Farm, are beeing terminated after a few seconds. I was able to reproduce this issue under my user as well. We also tried different RDP-sessions as well with the same result. Then i tried the same session under my DVLS-admin-user and the issue didn`t occur. I also tried it the other way around. I gave the reporting user also administrativ Permissions in DVLS an the issue didn`t occur. I also looked into the logs on the DVLS or the Gateways and unfortunally i wasn´t able to find any hints on what was going on. I am only getting this error on the Gateways, when the Session is terminated: 2025-12-03T06:26:14.049288Z ERROR listener{port=7171}:https{client=<ip DVLS>:56863}: devolutions_gateway::listener: handle_https_peer failed error="HTTP server: error shutting down connection: an existing connection has been closed by the remotehost. (os error 10054)" The reporting user also has access to the RDP-Manager (Version 2025.3.25.0) and there he can use the Gateway, with the same session, without any issues. Here are our current system-information. #DVLS-Server 4x vCPU-Cores 8GB RAM Windows Server 2025 with November CU DVLS 2025.3.10.0 .Net 9.0.11 - Windows Server Hosting Microsoft Windows Desktop Runtime - 9.0.11 (x64) #Gateway-Fram, consisting from two indentical server with the following specs: 4x vCPU-Cores 8GB RAM Windows Server 2025 with November CU Devolutions Gateway 2025.3.2.0 Microsoft Windows Desktop Runtime - 9.0.11 (x64) Please take a look at this issue and if you need further information let me know. Thanks in advance for the help! Greetings from Germany, Markus

127

4

avatar

William Alphonso

avatar

victorpop

Resolved Implemented

Gateway Error - SqlException - The INSERT permission was denied on the object 'RemoteSession'

Hi everyone, Today I upgraded our Devolutions infrastructure to newer versions (see end of post). Since then, we encounter a weird issue with the Gateway. Whenever you launch a new connection, the following error is generated: Error: SqlException - The INSERT permission was denied on the object 'RemoteSession', database 'MY_REDACTED_DATABASE_HERE', schema 'dbo'. at Microsoft.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction) at Microsoft.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception... This happens when I use the credentials for the Runner account on the DVLS server. Which has been the case for the last ...forever. I switch to the Owner account only when I need to update the system. After that, I jump back to using the Runner account. And this worked like that for the last year or so, with no errors. What am I missing? Current versions: Devolutions Server Console: 2025.3.5.0 Devolutions Server Instance: 2025.3.5.0 Devolutions Gateway: 2025.3.2 Remote Desktop Manager: 2025.3.20.0 64-bit Database running on a dedicated SQL cluster with SQL Server authentication.

Recommended Answer

4 months ago

Hello, Thank you for your feedback. The permissions script is missing the INSERT permission on the RemoteSession table for the Scheduler account. You can use the following query to grant the missing permission. Replace the Scheduler username in the UserName variable below. DECLARE @UserName varchar(150) SET @UserName = 'SchedulerUsernameHere' 'GRANT INSERT ON dbo.RemoteSession TO [' + @UserName + ']' Let us know if that helps. Best regards,

206

5

avatar

Marc-Andre Bouchard

avatar

ibhozza

Resolved

I can SSH but cannot Telnet through Devolutions Gateway (DGW)

I have test environment with following: Outside network - 192.168.20.0/24 (router 192.168.20.99) Inside Network - 192.168.20.0/24 (router 10.20.20.99) DVLS - 10.20.20.240 Local DNS Server - 10.20.20.240 Devolutions GW - 10.20.20.100 (internal), 192.168.20.99 (external) SSH/Telnet Server - 10.20.20.15 RDM Client - 192.168.20.190 Port Forwarding enabled on router : TCP 192.168.20.99:443 to 10.20.20.240:443 TCP 192.168.20.99:7171 to 10.20.20.100:7171 TCP 192.168.20.99:8181 to 10.20.20.100:8181 Basically, I would like to simulate RDM client from outside to a protected network. To gain access to a protected network RDM client must go through Devolutions Gateway (DGW). This is a standalone gateway installed on Ubuntu 24.04 with a single NIC and IP of 10.20.20.100 Routing between the two subnets is configured and working fine. From DGW, I can telnet and SSH to a Cisco device 10.20.20.15 since they are connected to the same switch. This proves that SSH and Telnet are configured well on Cisco device perspective. I did swap Cisco with a MikroTik device and both SSH and Telnet worked fine. Now here comes the challenge. From the outside subnet, I can SSH from RDM Client (192.168.20.190) to 10.20.20.15 through the gateway. From a Cisco/MikroTik device perspective, SSH connection originated from DGW 10.20.20.100 and life is good. But I cannot Telnet from RDM client 192.168.20.190 to 10.20.20.15 Both SSH and Telnet entries belong to a folder names "Linux-Servers" whose Gateway/VPN settings are set to "always connect" DGW settings: { "Id": "01e9f434-c0ac-4ebb-ae05-1adb0463abb6", "ProvisionerPublicKeyFile": "provisioner.pem", "ProvisionerPrivateKeyFile": "provisioner.key", "TlsCertificateFile": "server.crt", "TlsPrivateKeyFile": "server.key", "Listeners": [ { "InternalUrl": "tcp://10.20.20.100:8181", "ExternalUrl": "tcp://192.168.20.99:8181" }, { "InternalUrl": "https://10.20.20.100:7171", "ExternalUrl": "https://192.168.20.99:7171" } ] } See screenshots of entry properties and errors. The Telnet error indicates a gateway IP of 127.0.0.1 on while SSH shows the correct gateway of 192.168.20.99. The 127.0.0.1 does not look right and I think it is the root cause of failure. Honestly, I don't know where the 127.0.0.1 is coming from. I have deleted and recreated SSH/Telnet entries. Either way, SSH works, but Telnet keeps failing. I think the 127.0.0.1 in the error message is the smoking gun. [image] [image] [image] [image] [image] [image] [image] [image] [image] [image]

Recommended Answer

4 months ago

I got it working. The problem was DNS settings on RDM client. proxy.nbc.africa was resolving to 192.168.20.100 instead of 192.168.20.99 (using /etc/hosts file since rdm client has no access to private dns server) The rest of settings are still the same. Telnet is now working through the gateway

144

3

avatar

Erica Poirier

avatar

jamesmontgomery

Hub / Gateway / Recordings with RDM

Hi Folks, When using RDM with Hub + Gateways, and session recording is enabled, is there any combination of settings that results in the recording being stored on the Gateway side?

405

12

avatar

Samuel Dery

avatar

pvansluisveld

Multiple handle_https_peer failed errors

In our Devolutions Gateways logging we find a lot of errors, like HTTP server: error shutting down connection: Broken pipe (os error 32) HTTP server: peer closed connection without sending TLS close_notify TLS handshake failed: tls handshake eof Logs: 2025-11-04T17:33:52.985760Z ERROR listener{port=7171}:https{client=172.16.1.43:60994}: devolutions_gateway::listener: handle_https_peer failed error="HTTP server: error shutting down connection: Broken pipe (os error 32)" 2025-11-04T17:34:13.184212Z ERROR listener{port=7171}:https{client=172.16.1.142:50816}: devolutions_gateway::listener: handle_https_peer failed error="HTTP server: peer closed connection without sending TLS close_notify: https://docs.rs/rustls/latest/rustls/manual/_03_howto/index.html#unexpected-eof" 2025-11-04T17:34:33.094822Z ERROR listener{port=7171}:https{client=172.16.1.142:50951}: devolutions_gateway::listener: handle_https_peer failed error="TLS handshake failed: tls handshake eof" Is there something we can do to fix these errors? We have 2 Linux VMs with Devolutions Gateway version 2025.3.2, also 2 Windows Servers with Devolutions Server 2025.3.4.0 [image] Config off-dvls-gw03: root@off-dvls-gw03 devolutions-gateway # cat gateway.json { "Id": "3e95bdfe-99ba-41e4-96b6-1f755015935e", "Hostname": "off-dvls-gw03.linux.interconnect.services", "ProvisionerPublicKeyFile": "provisioner.pem", "ProvisionerPrivateKeyFile": null, "TlsCertificateFile": "server.crt", "TlsPrivateKeyFile": "server.key", "Listeners": [ { "InternalUrl": "tcp://*:8181", "ExternalUrl": "tcp://*:8181" }, { "InternalUrl": "https://*:7171", "ExternalUrl": "https://*" } ] } Config off-dvls-gw04: root@off-dvls-gw04 devolutions-gateway # cat gateway.json { "Id": "f2bf2b4c-9011-434b-9c96-e88c5059f9fa", "Hostname": "off-dvls-gw04.linux.interconnect.services", "ProvisionerPublicKeyFile": "provisioner.pem", "ProvisionerPrivateKeyFile": null, "TlsCertificateFile": "server.crt", "TlsPrivateKeyFile": "server.key", "Listeners": [ { "InternalUrl": "tcp://*:8181", "ExternalUrl": "tcp://*:8181" }, { "InternalUrl": "https://*:7171", "ExternalUrl": "https://*" } ] }

160

2

avatar

Benoit Cortier

avatar

jitsersevenant1

Linux Gateway Recording

Hi, Is there a way to configure the recording storage path on a linux gateway? I would like to attach/mount a seperate disk to the gateway for recording files. I've checked the KB's but the only mention there was that on windows based gateways you can only set the recording path through the dvls console.

120

2

avatar

Richard Markiewicz

avatar

jitsersevenant1

Resolved

DVLS-Gateway not connected

Hi, When trying to check my DVLS gateway logs I get the following error: Devolutions Gateway is unreachable. Please make sure it is up and running. DevolutionsGatewayUnreachable Pushing the revocation list gives met this: TypeError: Cannot read properties of null (reading 'length') at Object.next ( https://dvls.be.jit-c.eu/dvls/chunk-5UHK4QTL.js:1:179627) at bi.next ( https://dvls.be.jit-c.eu/dvls/chunk-56GO2EBD.js:3:3484) at we._next ( https://dvls.be.jit-c.eu/dvls/chunk-56GO2EBD.js:3:3208) at we.next (https://dvls.be.jit-c.eu/dvls/chunk-56GO2EBD.js:3:2935) at https://dvls.be.jit-c.eu/dvls/chunk-56GO2EBD.js:3:15822 at Pi._next (https://dvls.be.jit-c.eu/dvls/chunk-56GO2EBD.js:3:13436) at Pi.next (https://dvls.be.jit-c.eu/dvls/chunk-56GO2EBD.js:3:2935) at o.subscribe.a (https://dvls.be.jit-c.eu/dvls/chunk-56GO2EBD.js:3:23503) at Pi._next (https://dvls.be.jit-c.eu/dvls/chunk-56GO2EBD.js:3:13436) at Pi.next (https://dvls.be.jit-c.eu/dvls/chunk-56GO2EBD.js:3:2935) When pushing the test button I get this: Success Devolutions Gateway 'https://sbebrjump01.be.jit-c.eu:7171' is alive and healthy. SETUP: Devolutions server subnet A (servers) latest version Windows Server 2025 datacenter (evaluation) Devultuions gateway on subnet B (jump) Subnet B (jump) Linux ubuntu 22.04.5 LTS (jammy) dvls gateway 2025.3.2 powershell latest cerbot + acme dns plugin eurodns certificates for client - gateway are generated by certbot and adjusted into the correct formats Gateway status errors: Revision error / update: Certificate is now ok. I've linked the json file directly to the fullchain.pem and privkey files certbot generates. Nov 03 17:19:53 sbebrjump01 devolutions-gateway[28930]: 2025-11-03T16:19:53.590018Z INFO listener{port=7171}:https{client=10.100.0.2:59933}> Nov 03 17:19:53 sbebrjump01 devolutions-gateway[28930]: 2025-11-03T16:19:53.628529Z ERROR listener{port=7171}:https{client=10.100.0.2:59934}> Nov 03 17:20:41 sbebrjump01 devolutions-gateway[28930]: 2025-11-03T16:20:41.602349Z ERROR listener{port=7171}:https{client=10.100.0.2:59942}> Nov 03 17:20:41 sbebrjump01 devolutions-gateway[28930]: 2025-11-03T16:20:41.602366Z INFO listener{port=7171}:https{client=10.100.0.2:59942}> Nov 03 17:21:29 sbebrjump01 devolutions-gateway[28930]: 2025-11-03T16:21:29.833892Z ERROR listener{port=7171}:https{client=10.100.0.2:59944}> Nov 03 17:21:29 sbebrjump01 devolutions-gateway[28930]: 2025-11-03T16:21:29.833940Z INFO listener{port=7171}:https{client=10.100.0.2:59944}> Nov 03 17:21:38 sbebrjump01 devolutions-gateway[28930]: 2025-11-03T16:21:38.717003Z ERROR listener{port=7171}:https{client=10.100.0.2:59945}> Nov 03 17:21:38 sbebrjump01 devolutions-gateway[28930]: 2025-11-03T16:21:38.730433Z ERROR listener{port=7171}:https{client=10.100.0.2:59947}> Nov 03 17:21:38 sbebrjump01 devolutions-gateway[28930]: 2025-11-03T16:21:38.730487Z INFO listener{port=7171}:https{client=10.100.0.2:59947}> Nov 03 17:21:45 sbebrjump01 devolutions-gateway[28930]: 2025-11-03T16:21:45.611778Z ERROR listener{port=7171}:https{client=10.100.0.2:59948}> :request{method=PATCH path=/jet/config}: devolutions_gateway::middleware::log: duration=200.44µs status=401 Unauthorized :request{method=GET path=/jet/heartbeat}: devolutions_gateway::http: error=401 Unauthorized at devolutions-gateway/src/middleware/auth.rs:17> :request{method=POST path=/jet/jrl}: devolutions_gateway::http: error=401 Unauthorized at devolutions-gateway/src/middleware/auth.rs:178:28 > :request{method=POST path=/jet/jrl}: devolutions_gateway::middleware::log: duration=199.29µs status=401 Unauthorized :request{method=GET path=/jet/diagnostics/logs}: devolutions_gateway::http: error=401 Unauthorized at devolutions-gateway/src/middleware/aut> :request{method=GET path=/jet/diagnostics/logs}: devolutions_gateway::middleware::log: duration=198.13µs status=401 Unauthorized :request{method=GET path=/jet/heartbeat}: devolutions_gateway::http: error=401 Unauthorized at devolutions-gateway/src/middleware/auth.rs:17> :request{method=GET path=/jet/diagnostics/configuration}: devolutions_gateway::http: error=401 Unauthorized at devolutions-gateway/src/middl> :request{method=GET path=/jet/diagnostics/configuration}: devolutions_gateway::middleware::log: duration=203.12µs status=401 Unauthorized :request{method=GET path=/jet/heartbeat}: devolutions_gateway::http: error=401 Unauthorized at devolutions-gateway/src/middleware/auth.rs:17> Anyone any idea's ?

155

4

avatar

Michel Audi

avatar

sheinzelmann

Webaccess over Gateway

Hi I recently created some gateways to different customers. Some time later i noticed that i can only use RDP over gateways. If i want to access a Synology NAS over WebGUI i get the following error, same for Firewalls and others. [image] Did i configure something wrong? Thanks for your help Sean

211

11

avatar

Richard Markiewicz

avatar

hjbos

File upload through Gateway very slow

Hi, We use Devolutions Gateway between all our components including access to vCenter. When we need to upload an ova or iso to vCenter the upload process is very, very slow. Uploading a few gb takes several hours. When we connect without gateway it's much, much faster. Is this a known issue and is there something we can do to speed this up?

131

8

avatar

Richard Markiewicz

avatar

csudderth

Resolved

Issues with Gateway over Cloudflare

I'm not sure if this would be a Gateway issue or a Cloudflare issue, but thought I'd ask here as well. I do have a support case open with Cloudflare as well. I have a Devolutions Server with gateways and I am currently unable to access any web sessions while proxied over Cloudflare. This happens with both using a tunnel and without using a tunnel. When not using a tunnel, as soon as I set the DNS record to a gray cloud, it works great. I have tried this with two different gateway servers so far with the same results. Here is a sample of the logs when connecting: 2025-10-16T20:29:56.725672Z INFO listener{port=7171}:https{client=172.18.0.1:37338}:request{method=GET path=/jet/rdp}: devolutions_gateway::middleware::log: duration=33.316µs status=101 Switching Protocols 2025-10-16T20:29:56.755589Z ERROR listener{port=7171}:https{client=172.18.0.1:37338}:request{method=GET path=/jet/rdp}: devolutions_gateway::api::rdp: RDP failure client=172.18.0.1:37338 error="couldn’t read clean cleanpath PDU: WebSocket protocol error: Connection reset without closing handshake: WebSocket protocol error: Connection reset without closing handshake: Connection reset without closing handshake" On the Cloudflare logs, I am just seeing a 500 status on the edge servers, but no status code at all for the origin. Internally, everything works as expected. While inspecting tunnel logs, I do not see any X509/SSL errors (at first I was getting these until I specified the hostname in the TLS settings on Cloudflare Tunnel) and get no errors at all. Unfortunately, I don't have much else to go on and while I believe this is an issue on the Cloudflare side, has anyone seen this and dealt with this before?

171

3

avatar

csudderth

avatar

tiagoda-silva

SSH sessions fail via Devolutions Gateway, error 10054

Hello, I’m encountering an issue with all SSH connections through Devolutions Gateway. RDP, HTTPS and other sessions work perfectly, but SSH sessions fail with the following error in the Gateway logs: INFO tcp{client=x.x.x.x:15917}:generic_client{session_id="6b6bf8cc-660e-4210-aa2a-edeafef5edde" protocol="Ssh" target="tcp://x.x.x.x:22"}: devolutions_gateway::proxy: Forwarding ended abruptly reason="Une connexion existante a dû être fermée par l’hôte distant. (os error 10054)" Details: Gateway version: 2025.3.0 and 2025.3.2 (Windows Server) RDM version: 2025.3.16 Target host: VMware ESXi host (SSH enabled and reachable) From the Gateway itself, SSH to the ESXi works fine using PowerShell or PuTTY Only SSH via RDM + Gateway fails immediately Already tested: Restarted Devolutions Gateway service (no change) Update Devolutions Gateway (no change) Thanks for your help, Tiago

145

4

avatar

Michel Audi

avatar

tiagoda-silva

Resolved

Devolutions Server cannot update Gateway: “No updateable gateways were found”

Hello, I’m having an issue with the Gateway update process from the Devolutions Server web interface. When I go to Administration > Gateways, click Bulk update, select my Gateway and then click on update I get the following message: Update version No updateable gateways were found. The Gateway is reachable and operational. Details: Devolutions Server version: 2025.3.2 Devolutions Gateway version: 2024.3.3 (Windows Server) Thanks for your help,

Recommended Answer

5 months ago

Hi, Did you install Devolutions Agent on the same machine as Devolutions Gateway? https://devolutions.net/agent/ https://docs.devolutions.net/rdm/devolutions-ecosystem/devolutions-agent/#updating-remote-devolutions-gateways-via-devolutions-agent Let me know if you need further assistance. Best regards,

110

3

avatar

tiagoda-silva

avatar

TN

Cannot connect RDP with RD gateway via Devolutions GW

Hi Just set up a Devolutions Gateway for session recording and it works fine connecting to "normal" rdp connections. But when connecting to a server that is behind a Microsoft RD Gateway it does not work via Devolutions GW. Error message in RDM: [image] Error in the MS RDGW: The user "domain\username", on client computer "[public ip of client]", did not meet resource authorization policy requirements and was therefore not authorized to resource "[devolution gateway address]". The following error occurred: "23002". Using Devolutions server 2025.2.12.0 Devolutions Gateway 2025.3.0 on a separate server RDM 2025.2.29.0 If I connect to the computer running Devolutions Gateway I can reach other RDP servers behind MS RDGW just fine as well so network wise there is nothing blocking the connection.

334

6

avatar

Michel Audi

avatar

thomasprovin

Resolved

Unable to connect wit Devolutions Gateway - user must have a valid license for Devolutions Gateway

Hi, I am currently trying to expand our Devolutions server with a Devolutions gateway. The installation of the gateway was successful and the health checks are also successful. The Gateway is allowed for all vaults and showes up in Remote Desktop Manager. When I configure a session to use this new gateway in Remote Desktop Manager, I receive the following error message when starting the session: [image] I have not been able to find a way to assign a gateway license to a user. I was also under the impression that no additional licenses were required to use a Devolutions gateway. Do we need additional licenses or why do we receive the error message?

Recommended Answer

6 months ago

Hello, I have received the message that there are no longer 5 free licenses available since version 2024.2. [image] But as I wrote, I fundamentally misunderstood the licensing model and we will use a different solution. Thanks for all the informations.

201

9

avatar

thomasprovin

avatar

adillinger1

Persistent localStorage not working when accessing web applications through Devolutions Gateway

Hello, we are running into an issue when accessing web applications through the Devolutions Gateway. When connecting directly (without the Gateway), user-specific settings of the web application are stored in the browser’s localStorage and persist across sessions as expected. However, when connecting through the Gateway, these settings are lost every time the session is closed and reopened. After some analysis, the reason seems clear: The browser only persists localStorage per origin (scheme + host + port). When using the Gateway, the session is usually exposed as https://127.0.0.1:<randomPort> or via a dynamic relay path. Because the port/path changes on every connection, the origin is never the same . As a result, the browser creates a new, empty localStorage container each time, and the previously saved settings are not visible anymore. This is not an issue with cookies (those might be handled differently), but specifically with localStorage, since it is strictly tied to the origin. Question: Is there any way to configure the Gateway / RDM so that a stable origin is used (e.g., a fixed URL or fixed port), so that localStorage can persist across sessions? If not, would it be possible to consider this as a feature request for the Gateway? Having a stable origin would solve the problem and allow web applications to properly persist user settings. Thanks!

124

2

avatar

Michel Audi

avatar

fgerritsenmulkes

Best practices for Devolutions Server & Gateway deployment

Hi, We are currently using Devolutions Server together with the Devolutions Gateway, and I’m looking for advice on the best practices for configuring this setup. From what we understand, the Devolutions Gateway needs to be installed at the customer’s location, and the RDM client connects to it directly. This seems to require opening the gateway’s port to the entire internet, which in our view defeats the purpose of adding an extra security layer. How are other users handling this scenario? Are there recommended approaches or alternative configurations that avoid exposing the gateway directly to the public internet while still allowing remote RDM client connections? Thanks in advance for your insights!

351

6

avatar

Benoit Cortier

avatar

hello

Unrecognized Guid format when connecting through Gateway

I have set up Devolutions Server and several Gateways for my company but no matter what I do, I keep getting "Unrecognized Guid format" when trying to establish an SSH connection through a gateway on RDM. I have installed everything on Linux according to the guide and got it up and running. The gateway was running on a different Linux server. I can connect just fine when I am not using the gateway, when using it i get the Error. So I figured I would spin up Win Server 22 as it might be a bug with the Linux version. Unrecognized Guid format. So I tried a Gateway on a different Windows server. Unrecognized Guid format. I then tried the Linux gateway on the Windows server and the Windows gateway on the Linux server. Unrecognized Guid format. I have checked several times that the ID in the gateway.json matches the server. It does. I have tried with different versions of the GW. Unrecognized Guid format. After spending about 40 hours in total on it I give up. I created a Github issue as last resort and was kindly referred here. Any help appreciated. I am unsure if the Gateway topic is the right place for this as I am starting to assume that it might be a bug in RDM as it is so independent of which gateway version i used but as the error message specifically mentions the gateway I am posting it here for now. Please move if not adequate. To summarize the versions used: Server: Linux (Ubuntu Server 22.04): 2025.2.4.0 & 2025.2.3.0 Windows (Server 22): 2025.2.5.0 Gateway: Linux (Ubuntu Server 22.04): 2025.2.3.0 & 2025.2.1.0 Windows (Server 22): 2025.2.3 (tried standalone and side-by-side install) RDM: Linux (Ubuntu Desktop 24.04): TRIAL 2025.2.0.8 & TRIAL 2025.2.1.3 All gateways showed "Active and healthy" and in the Diagnostics section everything was green except an error at " TCP listening hostname configuration:" that I could never resolve. We are only using it internally, no access from outside, Certs are done with Let's Encrypt via Caddy doing DNS ACME challenges with the cloudflare plugin. However, Gateway to Server connections were done with the IP address. As I have spun up several servers and gateways and flattened some already again, I do not have logs for all machines but if you need some please let me know.

282

13

avatar

Richard Markiewicz

avatar

jeffreyzammit

Backlog

Cannot connect to session from my RDM mobile app which make use of the Devolutions Gateway

When using my RDM mobile app, I cannot connect to sessions that are configured to make use of the Devolutions Gateway. Is this a lacking feature in the mobile app, or is it some misconfiguration from my end?

268

21

avatar

jeffreyzammit

avatar

pvansluisveld

Automatically terminate sessions

I was wondering if it is possible to automatically terminate sessions if there idle for x minutes/hours? We would like to have it on for all kind of sessions, so RDP, SSH and HTTPS. We are using a gateway farm with 2 gateways. Devolutions Gateway version: 2025.2.3 OS: Linux / Debian 12 Bookworm

176

2

avatar

Marc-Antoine Dubois

1 - 25 of 53 items