Support

Hi, I wanted to post this on the forum in case someone runs into this in the future. Without revealing them, thank you to the customer who found this. The issue we had was related to Kerberos not working when using Devolutions Gateway as a KDC proxy in an environment where the client sits in Domain A but is trying to reach into Domain B. The Gateway is in Domain B. Despite the configuration on the AD side being properly configured, we only got generic NTLM downgrades from the Remote Desktop Manager client and a generic "Account restriction" message. Here’s what they figured out: The issue was caused by having two users with the same "User logon name". Even though the users were in different domains (and forests), the duplicate UPN caused ambiguity during cross-forest Kerberos principal resolution. This interfered with Kerberos realm discovery, leading to Kerberos failing silently and falling back to NTLM, which ultimately resulted in the misleading: “A user account restriction (for example, a time-of-day restriction) is preventing you from logging on.” Once the duplicate user logon name was made unique across the environment, Kerberos authentication started working as expected through the Gateway. Before figuring this out, the workaround was to use FreeRDP with the SSPI module in portable version. This seemed to bypass the fallback lookup of the Kerberos realm that Microsoft RDP performs by default. Like so: [image] [image] Hopefully this saves someone a few hours of troubleshooting. Best regards,

Yesterday we updates Devolutions Server and Gateway to the latest version. When I try to open an asset through the gateway I get this error: [image] Also when I try to edit the settings in Devolutions Server Console I get an error: [image] Attached the details of the error. Is this a known issue and what can I do to fix this?

Hello Devolutions, we evaluate implementing Devolutions Gateway. We recognized, that we need connectivity on Port 7171 to the Devolutions Gateway for it to work from the Clients Web-Browser, which is different than what is shown on your architecture sketch. [image] 1.) Is this some kind of misconfiguration on our side or is 7171 from the Clients Web-Browser to the Devolutions Gateway really needed to do RDP from Devolutions Server using the Gateway in Web-Browser. 2.) By security policy, we are not allowed to have direct Internet access to the Devolutions gateway. How shall we secure the 7171/8181 Ports (e.g. is there Reverse Proxy support) - especially in case of 8181 which is TCP and not HTTPs. Can this be tunneled using HTTPs ? I am thinking about 2 scenarios A) Using Azure Frontdoor + WAF with Azure Private Link to Devolutions Gateway, forwarding connections from 443/HTTPS to 7171/HTTPS and tunnel Connections on 443/HTTPS to 8181 TCP B) Using Azure Application Gateway V2 +WAF with 443 forwarding to 7171 and TLS proxy for 8181 Thank you for your support ! Greetings Jean Pascal

Hi, at the beginning of this year we switched to RDM with selfhosted Devolutions Server as the Backend together with the PAM module. We appreciate RDm and it´s many integration options and protocols, so we don´t have to leave the "RDM universe" for daily tasks. We managed to get most of the things properly but struggling to archieve the following: We´ve set up a gateway farm at our headquarter in germany but now want to set up gateways at our branch office locations worldwide. How do we configure that the "nearest" gateway is used instead of always connecting to the headquarter for managing machines that are located in the branch offices? Best regards Florian

After upgrade of dvls from 2025.1.x to 2025.3.18 our gateways started to have issues with certificate verification. Gateways are marked as down and when we do the Ping Certificate warning pops up. Workaround is to click Continue and Save but we are curios why, both sides should have access to CRLs, certs are valid and created by trusted CA. [image]

After spending the better part of today trying to get my gateway to work... I will now ask for help... Devolutions Gateway is running on Linux Ubuntu 26.04. TLS Cert from Let's Encrypt. He says he is happy... See attachments. [image] [image] [image] Devolutions Cloud... says "Unreachable Gateway". I have confirmed 7171/8181 are indeed reachable from the internet and local LAN. Each time I get "Unreachable Gateway" error, this is the log entry on the gateway: [image] (My network is a /23... .255 is okay in this case) I hope someone has gone through this before and can just give me a magic solution ;) Or... just point me in the right direction... this works too

Hello, we've recently setup a Devolutions Gateway on a remote site and we've got a few questions about how the Devolutions Server actually communicates with the gateway. In the gateway documentation found here: https://docs.devolutions.net/gateway/overview/system-requirements/system-requirements-dvls/ It says: " The default port for HTTP(s) communication with the gateway is 7171, while the default port for TCP communication is 8181. These ports should be open and not blocked by firewalls to allow proper communication. " Question 1: The graph above that line shows that the Devolutions Server only communicates on port 7171 outgoing to the gateway. So I would assume that my firewall rule for Devolutions Server and Gateway communication doesn't need port 8181 outgoing allowed right? Question 2: I know that when using the Remote Desktop Manager and connecting to, for example an RDP session via a gateway its the client running RDM that opens the connection. However when I use the WebUI of the Devolutions Server to connect to a RDP Session via a gateway does my client running the Browser/WebUI initiate the connection or is it the Devolutions Server that connects to the remote gateway? Best regards, Lennart

Hello Everyone! I wonder if someone could help, or has come across this issue before. We are currently evaluating the Devolutions Team Starter Pack and trying to get Gateway to work with Devolutions Server via an Azure/Entra Reverse Proxy/ Application Proxy. Current Setup: We have a Windows 2025 server installed on prem running Devolutions Server with a side-by-side installation of Gateway server. We have existing Azure connectors on the LAN for other applications, so we have created a Enterprise Application in Azure to access the Devolutions Server via web and RDM with MFA SSO Enabled. This is all working fine and we can access our estate on RDM and Devolutions server using this setup. Issue: When trying to configure the Gateway server using the same reverse Proxy address within Devolutions server, it fails on the ping test and therfore marks it as "down". If we specify the internal address for the Gateway server it finds it and works without issue, however when connecting to sessions via the Gateway server, this only works when on the internal network, externally it fails (even though if we go into a RDP entry within the vault and test the Gateway connection, it passes) Reading the forum post here ( Best practices for Devolutions Server & Gateway deployment ) it sounds like the Gateway server should be accessible via the same URL as the Devolutions server because the IIS handles the redirects. Has anyone got this to work using the same entra reverse proxy address? Thanks! Dave

Hello, we have a problem using and debugging Devolutions Gateway running under Linux (Oracle Linux Server release 9.7) I have an external IP and doing NAT on our firewall and ACL rules allowing 7474 and 8181 are in place. The Devolution Gateway ist running as a service on a VM and listening on Port 7474 and 8181. We deployed a actual lets-encrypt certifiacate. Now we tried the following two use-cases: using RDM from within the company office. RDM is configured to use the Devolutions Gateway to reach the destinations. All destinations are also reachable directly via LAN. -> Connections works using RDM from outside the company office. RDM is configured to use the Devolutions Gateway to reach the destinations. All destinations are not reachable directly via LAN. -> Connections do no work [image] All destinations we try to reach from are in a private network (192.168.0.0/16) and have an URI *.internal.lan witch is only resolvable by an internal DNS-Server reachable form the devolutions gateway. We also tried public dns names and internal IP Adresses. So in conclution we are not able to access internal ressources via devolutions gateway without an VPN. We try to debug the problem by tracing traffic on the firewall, but did not capture traffic incoming to the devolutions gateway via the external IP from my non-office IP. On the other hand, I am able to create traffice via telnet 7474 and 8181 from my client. So it looks like Remote Desktop Manager does not try to connect via Devolutions Gateway

In the rease notes of version 2026.1 there is a entry of proxy bassed credential injection. But I can't find the place where I can configure it. Where can I find this option? Inject credentials securely with RDP proxy-based injection Devolutions Gateway can now inject RDP credentials from the Gateway rather than sending them to the client, significantly reducing credential exposure by keeping secrets closer to the private network. It also supports RDP reconnections by retaining the password only as long as needed, and is enabled by default for new Gateways (disabled for existing Gateways to avoid upgrade impact), and controlled via a ruleset toggle with logs indicating when it’s active.

[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]

Hello everyone, I'm using the free version of Remote Desktop Manager (some version from 2026). I need to access a single server that I can't reach directly via zscaler. We normally have a Microsoft Terminal Server that we access via RDP, and from there we establish an SSH session. I've installed the Devolutions Gateway on this server, and I can access my target via the web interface. However, I'd like to connect from the RDM to the target through the Gateway. Unfortunately, I have no idea how to do this. I've connected the RDM to Devolutions Hub Personal. Is this even possible? If so, is it free? I would be very grateful for any instructions. Kind regards - H-BLOGX

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?

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

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

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?

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.

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

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.

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]

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?

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://*" } ] }

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.

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 ?

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