Lars

We're an MSP running Devolutions Server with RDM and Devolutions Gateway 2026.3.0, evaluating Agent Tunnel for customer-site access. The feature works well — enrolment and transparent routing via advertised domains are in place. We want to raise a gap that becomes structural at our scale.

Context:

Two properties of that environment break advertisement-based routing:

1. Overlapping RFC1918 space. Most sites use 10.0.0.0/24, 192.168.1.0/24, etc. Subnet advertisement cannot disambiguate two agents advertising the same prefix, so we don't advertise subnets at all.

2. Shared DNS suffixes. A significant share of customers use .local, corp.local, ad.local and similar. Domain-suffix advertisement (*.corp.local) collides in the same way. Only customers with a unique AD suffix can be routed reliably today.

Request

The Gateway routing pipeline already evaluates an explicit jet_agent_id claim in the session token before subnet/domain matching (PR #1741). What's missing is a way for Devolutions Server to set it.

Concretely

Add an optional "Route via Agent" selector to Gateway Ruleset (and ideally an override at entry/folder level), listing agents enrolled on the ruleset's Gateway. When set, DVLS emits jet_agent_id in the session token so the Gateway routes through that agent regardless of advertisements.

Ideally a way to choose what agent to connect to at the entry level in RDM:

Secondary, lower priority: a way to map a synthetic per-tenant suffix (e.g. *.tenant42.tun.example) to the customer's real internal name at the agent, so entries can use unambiguous names without touching customer DNS. Optional if (1) exists.

With (1), we can keep IP-based entries per customer folder, bind the folder to a ruleset that pins the agent, and overlapping address space stops being a concern. It also gives a deterministic, auditable path per customer rather than one inferred from advertisements — useful for compliance.

Thanks, we'll keep our eyes peeled!

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?

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.

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.

Sorry to keep bumping this post, but we have discovered that the same bug still exists if you try to right click an active connection and press 'select in navigation pane'

This only applies cross-vaults as the act of right clicking the connection automatically marks the connection in the vault.

Ok, any ETA on 2025.1.28?

Hello!

We just updated to 2025.1.26.0 today, but search is still not working.

I see no meantion of it in the patch notes either, and update on this?

Any update on this?

Yes we use version management.

There is no button to Analyza Cache available:

But, looking at Private Vault today, the duplicate connections seems to have disappeared. No idea what happened, but it seems to be working as intended now.

Data Source is a locally installed DVSL & Data source is on version 2025.1.3.0.

As stated the Clients are on version 2025.1.24.0, this issue started after this upgrade.

I can also add that this is a multi-vault search. The seach brings you to the correct Vault, but does not bring you to the entry itself (Ref error message).

After upgrading Devolutions RDM Client to latest version: 2025.1.24.0 (Windows). Some of our users are reporting duplicate entries in Personal Vault. Every entry (Excluding folders) gets listed twice in the Personal Vault.

This also affects entries where you have linked to personal Vault based on a keyword, making you chose witch of the two entries you want to use.

Deleting one of the entries affects both entries, and both entries are removed when one if deleted.

Error is only in the local client, web client is not affected.

Personal Vault:

When opening entry connected to Personal Vault with keyword:

Hello.

After upgrading Devolutions RDM Client to latest version: 2025.1.24.0 (Windows). Our users are reporting errors woth Search functionality in RDM.

The object you are searching for shows up in the search results, but when we try and go to that entry we get an "Entry not found error".

Restarting RDM seems to resolve the issue for a short time before it suddenly stops working again.