Gateway integrated with NGrok not detected as offline with Hub

A fix for this issue has been implemented in version 2025.3
Implemented

Gateway integrated with NGrok not detected as offline with Hub

avatar

Hello,

When a Gateway is integrated with nGrok, and the machine is shutdown, the gateway still shows as online in the Hub Administrative portal, subsequently connection launches are still routed to it and eventually fail/timeout. The test connection button seems to detect the gateway is offline, but the gateway remains green in the list.

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

Thanks
Joe

All Comments (8)

avatar

Issue also seems to occur with gateways integrated with Cloudflare

avatar

Hello Jm2,

Thank you for reaching out to our forum. Could you let us know which Gateway version you are using?
Also, did you find any relevant information in the Gateway logs?

Best regards,

Michel Audi

avatar

Hi Michel,

Using gateway v2025.2.3.

There isnt anything relevant in the logs. When the gateway machine is shutdown, shouldn't hub detect it as being offline and prevent routing connections to it?

Thanks
Joe

avatar

Hello Joe,
Thank you for sharing these details. To clarify, in Hub the green status for a Gateway indicates that it is healthy based on its last successful heartbeat. It does not directly represent whether the Gateway host machine is currently online or offline.
When the machine is shut down, the Gateway may still appear green for a while since Hub has not yet marked it otherwise. The Test Connection button checks the reachability of your Gateway and confirms that the service is started and responding. If the Gateway machine is down for any reason, the Gateway status will change to a red X. However, if the nGrok tunnel is down, the Gateway will still respond on the HTTPS listener, but the connection will ultimately be dropped.

Please let us know if you’d like assistance adjusting those settings.
Best regards,

Michel Audi

avatar

Hi Michel,

According to Devolutions Gateway farms - Devolutions Documentation, it should accommodate 'continuous service availability' when a member is unavailable. As you described, when a member is shutdown (or the tunnel stops) it remains in a healthy status for a 'while' (my experience was hours, if not days) and any connections routed to it fail. I have logged another feature request to enable client side detection of an unavailable gateway but there is currently no ETA or indication whether that will be undertaken Gateway Farm member client side failover

In effect, these limitations result in customers being unable to utilize gateway farms for high availability / failover capability. Hopefully the Devolutions team can find a way to address that via enhanced availability detection, whether it be server/hub or client side or both.

As a side note, gateway farms also have a dependency on a PAM service being installed/available as per Devolutions Gateway farms configuration - Devolutions Documentation. Ideally any enhancement of gateway availability would accommodate state detection of the PAM service also.

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

Thanks
Joe



025b8a8b-2228-4d46-8dd6-c2cdb272f3cd.png

avatar

Hello,

Thank you for the clarification regarding the farm. The Hub Business team has indicated that an improvement to this behavior is planned for the 2025.3 release.
Thank you for your patience.


Best regards,

Michel Audi

avatar

Sounds good, thanks Michel.

avatar

Hello,

Thank you for being so patient!

I'm letting you know that version 2025.3 of Hub Business is now available with this feature included.

Please let us know if this works or if you encounter any issues.

Best regards,

Maxim Robert

A fix for this issue has been implemented in version 2025.3