Unable to launch WebUI gateway sessions in a cross origin domain configuration

Unable to launch WebUI gateway sessions in a cross origin domain configuration

avatar

Hello,

Using DVLS 2025.3.15, which is accessed via Azure App proxy using url https://rdm.company.com

If gateway URL is in a different domain (i.e. https://gateway.company.app), the sessions will not launch via WebUI.

Conversely, accessing the same DVLS instance in the same browser session via an alternate url (i.e. https://rdm.company.app) results in successful launch of browser based session.

It is fairly common in a Hub Business deployment to have cross origin domains (i.e. https://customerhub.devolutions.app and https://gateway.company.com. Does DVLS support an equivalent setup? Customer would prefer to use primary domain (i.e. https://rdm.company.com) for branding purposes, but wants gateway traffic routing via a separate Cloudflare hosted domain.

Please let me know if you would like any additional info.

Thanks
Joe

All Comments (2)

avatar

To add, when there is direct line of sight between the browser and gateway (i.e. internal network), cross origin does seem to work. As far as I recall from another deployment, cross origin works fine over the internet with hub + cloudflare, so not sure if there is something different when using DVLS?

There is nothing logged in DVLS or gateway logs when the connection fails.

avatar

Hello,

Thank you for reaching out!

My name is William and I'm here to assist you.

Cross-origin domains are supported by Devolutions Server and Devolutions Gateway. One important requirement is that the TCP hostname configured on the Gateway must be resolvable and reachable by the client (browser or RDM). This hostname is used when establishing the connection to the Gateway.


To help narrow down the issue, could you please verify the following:

  1. Gateway health page
  2. Gateway connection test
    • From the Devolutions Server web interface, does the Test Connection for the Gateway succeed?
  3. Error messages
    • When attempting to launch the session from the Web UI, do you receive any specific error messages? If possible, please also check the browser developer console to see if any errors appear when the session launch fails.


These details should help determine whether the issue is related to Gateway connectivity, DNS resolution, or the proxy configuration.

Best regards,

d875f1d7-1b8c-48f8-8cf9-b2b8c12e86ec.png