Devolutions Gateway

Ctrl + k

Devolutions Gateway

Devolutions Gateway

Announcement

Official announcements for Devolutions Gateway.

Feature Request

Request new features for Devolutions Gateway.

Support

Get help with Devolutions Gateway.

Kerberos failure via Devolutions Gateway (KDC proxy) caused by duplicate UPN across forests

Support (French)

Get help with Devolutions Gateway in French.

Support (German)

Get help with Devolutions Gateway in German.

Bug Report

Report bugs in Devolutions Gateway.

Recent Posts

Published 4 hours ago

Option to change Windows Service-Account of Gateway Service

Hi! We recognize the need for a better supported workflow here. As per internal discussions, we are looking into: Updating the installer to ensure it does not overwrite a custom service account on updates. Providing documentation about the required permissions for a custom Windows service account running the gateway. We’ll keep you posted on any progress for official support and documentation. Best regards,

Feature Request

stefannitsch-fitz

Published 12 hours ago

Option to change Windows Service-Account of Gateway Service

Hi! Regarding Installation on a Windows Server it would be good to have a supported option to define another gateway service account than NETWORK SERVICE. For example - session recording to SMB-Share requires authentication. It is actually possible to access a share and use it for session recording when changing the gateway service account to one that has access to that share. But there are caveats: you need to manually adept NTFS permissions for the gateway folder within "Program Data" for the new service user triggering gateway update from devolutions server/RDM fails (ERROR listener{port=7171}:https{client=xx.xx.x.xxx:61728}:request{method=POST path=/jet/update}: devolutions_gateway::http: error=500 Internal Server Error at devolutions-gateway\src\api\update.rs:68:9: failed to write the new `update.json` manifest on disk [source: Access is denied. (os error 5)])) everytime you modify the gateway-configuration from the server console (companion tab), the service-account automatically changes back to NETWORK SERVICE BR

Feature Request

Published 3 days ago

Reverse Proxy for Gateway Agents

Thanks, we'll keep our eyes peeled!

Feature Request

Published 5 days ago

Reverse Proxy for Gateway Agents

Perfect. The 2026.2 iteration will also ship self updates and scheduled updates for Devolutions Agents. The feature is already part of Devolutions Agent and Gateway v2026.1.2 released yesterday: [image] However, we still need to make this easy to manage centrally via Devolutions Server. As for the timeframe, YYYY.2.0 versions are typically released in June, so I would say in 1 or 2 months from now. Best regards,

Feature Request

Published 5 days ago

Reverse Proxy for Gateway Agents

Correct, that is what we are looking for in functionallity. Of course with central mangement of these Gateway agents, so we can bulk update them from the Gateway server. Glad to hear that, do you have a timeframe for when v2026.2 will be available?

Feature Request

Published 6 days ago

How to run Devolutions Gateway under Linux

Hello Konrad, Awesome! Well, I assume the automatic detection work as expected, but in your gateway.json the Hostname parameter is not set, so it will use the (internal) hostname of your GW machine. To avoid this, you can simply add the Hostname parameter to your configuration file, like "Hostname": "gw.yourexternal.domain", After a Gateway restart, the Auto detect should work as expected. https://github.com/Devolutions/devolutions-gateway#configuration Regards, Min

konradbauckmeier1

Published 6 days ago

How to run Devolutions Gateway under Linux

Oh that simple, yes ist works now as expected. THANK YOU! I thought we had tested that as well. In any case, the “automatic detection” button doesn't make sense in the GUI. It would also be nice if the documentation here were more detailed.

Published 6 days ago

How to run Devolutions Gateway under Linux

Hello Konrad, For security purposes, I would recommend removing the screenshot. I have seen all the required information, thank you! For the TCP Hostname please also use the name of your Gateway: qey.....net Regards, Min

Published 6 days ago

Reverse Proxy for Gateway Agents

Thanks, that helps. I want to make sure I’m really understanding your request correctly. You are asking for a native site connector / outbound tunnel capability in Devolutions Gateway, where a component deployed inside the customer network would: establish an outbound connection to Gateway, simplifying network configuration at the customer site, allow Gateway to securely relay RDP / SSH / HTTPS connections to internal systems behind it, and do this without requiring a separate third-party reverse proxy or VPN solution such as Cloudflare tunnel or Ngrok. If that is what you mean, then I believe I understand the use case correctly. I’m also glad to let you know that we are currently experimenting with such a feature and have already made good progress. It is currently planned for v2026.2 on our roadmap. I’ll attach the ticket to this thread. Best regards,

Feature Request

konradbauckmeier1

Published 6 days ago

How to run Devolutions Gateway under Linux

the gateway url is resolvable externally the tcp hostname is not. I also used the FQDN for the telnet tests.

Published 6 days ago

Reverse Proxy for Gateway Agents

Hello Benoit Cortier As we understood the Gateway is a way to connect to servers and services on edge networks without VPN. But we do requiere those connections to be on-demand and the protection a reverse proxy offers. I see you support 3- party Reverse Proxy Solutions, but this another layer of complexity to the solution. the addition of a native Reverse Proxy in the Gateway solution would make it a viable option for us to make use of. A typical example of a use case for us would be to connect to a server (RDP) or a service (SSH/HTTPS) at a customer location. Today we use VPN for this. But we're looking into a way to do this simpler and more secure. What we want would be the option to deploying one Reverse Proxy Agent that would handle incoming network connections to the different servers in that given network. (RDP, SSH, HTTPS etc). Allowing only connections coming from our Public IP.

Feature Request

Published 7 days ago

How to run Devolutions Gateway under Linux

Hello Konrad, Is your Devolutions Gateway access URI resolvable externally? If your Devolutions Gateway is configured with a URL like gateway.internal.lan it will not work as the Gateway cannot be reached. This would explain why the logs are empty and why no external connections can be established. https://docs.devolutions.net/gateway/overview/system-requirements/system-requirements-dvls/#basic-infrastructure Did you use the FQDN or the IP address of the Gateway for your telnet tests? Regards, Min

Published 7 days ago

Reverse Proxy for Gateway Agents

Hello Lars Just to clarify the use case: is the goal to install an Agent at a customer or remote site, have it establish an outbound connection to Gateway, and then let Gateway route sessions through that Agent to private resources behind it? In other words, are you referring to something like a remote-site outbound connector or tunnel? Something that would allow you to use a central Devolutions Gateway to manage access to many internal networks behind Devolutions Agents? Best regards,

Feature Request

Published 7 days ago

Reverse Proxy for Gateway Agents

Is there any plans to include a native Reverse Proxy functionallity into the Gateway agent installations? The inclution of Reverse Proxy functionallity would make the Gateway product a very viable option to handle customers/remote sites access at scale.

Feature Request

konradbauckmeier1

Published 10 days ago

How to run Devolutions Gateway under Linux

Of course I can share the logs, but as I explained earlier, they are empty, because there are no connection attempts form RDM to the public gateway IP (no packet in the firewall at all) if I am outside the VPN and try to reach internal systems without VPN. Thats why I am assuming, that I have not unterstood the usage of the gateway in the first place or I have configured RDM not correctly. However, from the offce there is already a network-based VPN connection to the datacenter (some entries in the logs) and from outside I am able to do a telnet to the gateway ports (visible via firewall traceroute) Thank you for your support! regards Konrad (sorry there was a planned change of my email adress, thats why I have a new username)

Published 13 days ago

How to run Devolutions Gateway under Linux

Hello, Thank you for the detailed description of the issue. To help us investigate further, could you please share the Devolutions Gateway logs? You can find information on how to locate them here: https://docs.devolutions.net/gateway/kb/troubleshooting-articles/gateway-troubleshooting/#devolutions-gateway-logs-and-diagnostics Once we have the logs, we will be able to take a closer look at what happens when a connection attempt is made from outside your office network. Best regards,

konradbauckmeier

Published 14 days ago

How to run Devolutions Gateway under Linux

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

Published 19 days ago

2026.1 Proxy based credential injection

Thanks! It was for me not clear that I had to create a ruleset. We wil test it.

Published 19 days ago

Configuration not in sync

Hello, Thank you for your response. I have created a case and sent you a request for a remote session to allow further investigation. Best regards,

Published 19 days ago

2026.1 Proxy based credential injection

Hello freddy1 The option is available when using a Gateway Ruleset. First, create a Gateway Ruleset: [image] Go under the Security section: [image] As written in the announcement, it’s enabled by default for new rulesets, so most likely you would just save, and select the Gateway Ruleset for the connections you wish to apply proxy-based credentials injection. Gateway Rulesets are assigned the same way as normal Devolutions Gateways. Best regards,

External resources

Devolutions Documentation

Technical SupportEmail : service@devolutions.netPhone : + 1 844 463.0419