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

Hello Jeff,

Thank you for reaching out to our forum. I wanted to check are you accessing the Gateway externally via VPN or through a reverse proxy?
If not, you won’t be able to reach internal resources that rely on the Gateway. However, if you are connected through VPN and still can't access the Gateway, it could be due to a network rule blocking the connection.
Let me know which scenario applies so I can assist you further.



Best regards,

We are making use of Devolutions Business Hub and the Gateways are set through that portal.
I presume that I would be to connect to entries using the RDM mobile app just as I would be able to use my Windows RDM app - i.e without the need to establish a VPN connection first. The idea of using Devolutions Gateway is to avoid having VPN's in the first place.

Thanks,
Jeffrey

I agree with your point; however, even when using Hub Business, it's important to remember that the Devolutions Gateway is hosted within your own infrastructure. The Hub primarily acts as a cloud-based password manager to store your credentials and sessions.
That said, the Gateway installed in your environment still needs to be accessible externally—either through a VPN or by being published to the internet. Without this, external connections through the Gateway will not function.
To make your Gateway accessible from outside your network, you’ll need to either expose it directly or use a tunneling solution such as Cloudflare Tunnel or ngrok. You can find the relevant knowledge base articles below for configuring both options:

• ngrok Tunnel KB: https://docs.devolutions.net/dgw/kb/how-to-articles/reverse-proxying/ngrok-tunnel-gateway/
• Cloudflare Tunnel KB: https://docs.devolutions.net/dgw/kb/how-to-articles/reverse-proxying/cloudflare-tunnel-gateway/

Best regards,

The Gateway is published via reverse proxy and hence can be accessible online via it's FQDN - note that this is the same way that the RDM desktop client works when we are accessing the entries (servers) from remote locations - without the need to establishing VPN connections.

Hello Jeffrey,
Thank you for bringing this to our attention. Could you please let me know which mobile OS you’re using, along with the version of Remote Desktop Manager and Gateway used for this test?
Best regards,

Sure. I am using Android 16 on my phone.
My desktop RDP version is: "2025.2.20.0"
My mobile RDP version is: "2025.2.0.17"
Devolutions Gateway versions include: "2025.2.0" and "2025.2.2"
Regards,
Jeffrey

Hey Jeffery,
I'm following up to confirm that RDM on Android is working with RDP sessions that use a gateway we tested it in our lab today.
However, I’d like to highlight one important point: if these sessions have Gateway Recording enabled and set to Required, RDM on Android does not support this feature. In such cases, the sessions won’t open on the Android client.
Could you share the exact error message you're encountering with these sessions?
The error prompt might help us identify what’s going on.
Best regards,

Hi @Michel Audi,

I do not have Gateway Recording enabled, however, it still is not working on Android. The 'Open' session button does nothing when selected - no errors or anything.

Regards,
Jeffrey

Hey Jeffre,
Thank you for your feedback.

1- As the next step, please open RDM on your mobile device and create a new session of type PowerShell Terminal (Local).

• Under the General tab, in the Command field, enter the following:
• tnc <yourgwhostname> -port 8181
• (Replace <yourgwhostname> with your actual Devolutions Gateway host name)
• Then go to the Host and Credentials tab:
  • Set the Host/IP to your Devolutions Server address (IP or hostname)
  • Provide the appropriate credentials used to connect to the server

This will allow you to test the TCP connection on port 8181, which is the one RDM uses to route sessions through the Gateway.


2- The other thing to check open a browser on your Android phone and try https://your-gateway-hostname:7171 let me know if you will encounter any certificate warning or the page doesn’t load,as the Gateway certificate should be trusted on your machine.

3-Could you test with SSH,RDP session is it the same with ssh ?

4-Is this issue happening with other users RDM mobile?


Please let me know the output .

Hi @Michel Audi ,

Thanks for following up.
Here are my replies:

1. PowerShell Terminal (Local) is not an available option in android RDM. I can only select PowerShell Terminal (Remote) - Experimental. When setting this entry from my desktop RDM, it is not available to be used on the phone. FYI - from the desktop RDM, this works perfectly well.
2. The gateway are not set with a web interface (as per Devolutions Gateway configuration with Devolutions Server - Devolutions Documentation). This said the SSL cert installed is from a public CA authority and not self-signed so it would not give any warnings (but the page does not load - not even from a computer browser)
3. Issue happens on all kind of entries - SSH, RDP, Website, etc
4. Did not test with other phones/users as I do not want to announce this to others still it is functional.

Regards,
Jeffrey

Hey Jeffrey,

Thank you for your feedback.

The URL https://yourgwhostname/jet/health should open correctly in your mobile browser could you confirm whether this page loads successfully on your mobile device?
Additionally, are you able to download any external app on your Android device that allows you to test network connectivity with a specific port? If so, try testing:
tnc <yourgwhostname or IP> -port 7171
tnc <yourgwhostname or IP> -port 8181
If these tests fail from your mobile device, that would likely explain the behavior you're experiencing.

Best regards,

Interesting...
On my desktop web browser I get: "Devolutions Gateway "FQDN" is alive and healthy."
while from my phone I get: ERR_INVALID_HTTP_RESPONSE

Port test from my phone to tcp/7171 and tcp/8181 both work.

That explains it the Gateway certificate is not trusted, which causes the connection to fail during the initial handshake stage. If trust cannot be established, the Gateway will automatically block the traffic.
Trusting the certificates for both the Gateway and Devolutions Server is essential. On Android, you can manage this under:
Settings > Security > Encryption & Credentials > Trusted Credentials > User not sure you can check this depends on your mobile model.

Ensure that the certificates are stored locally on the device and properly installed so they are recognized as trusted.

Best regards,

Thanks - but this should not apply for commercially bought SSL certificates, right? This particular SSL cert is issued by Sectigo Limited

Actually I had a type on my phone browser. I am getting the "Devolutions Gateway "FQDN" is alive and healthy." message there too.

Sorry about that

RDM still does not work though

Hello,

Quick heads-up.
From the description you gave, it does not sound like a configuration problem on your side.
Incidentally, we discovered a similar bug on platforms such as Linux and macOS.
A lot of code happens to be shared between RDM for Linux, RDM for mac and RDM for Android, so I suspect if we fix the bug for another platform, it will be fixed for Android as well.
We’ll open an investigation to make sure it is the case.
In the meantime, I’ll link the ticket to this thread, and keep you in touch when it’s fixed as appropriate.

Best regards,

Hi @Benoit Cortier ,

Thanks for that.
Hopefully will get resolved soon.
@Michel Audi - thank you too for your continuous input on this matter too and keep up the good work.

Regards,
Jeffrey

Hi @Michel Audi,

Were there any developments on this?
Regards,
Jeffrey

Hello Jefferey,
Thank you for your patience, and it's great that you followed up regarding this issue. I wanted to let you know that this bug is still under development, and it has been given high priority to ensure it’s resolved as soon as possible.
I’ll keep you updated as soon as there is any progress.
Thank you for your understanding.


Best regards,

Hello Jefferey,
Thank you for your patience, and it's great that you followed up regarding this issue. I wanted to let you know that this bug is still under development, and it has been given high priority to ensure it’s resolved as soon as possible.
I’ll keep you updated as soon as there is any progress.
Thank you for your understanding.


Best regards,

@Michel Audi
Thanks @Michel Audi. I understand that it can take some to get resolved. I followed up as this is something I would require in cases of emergency when away from my workstation.

Regards,
Jeffrey