DVLS-Gateway not connected

Resolved

DVLS-Gateway not connected

avatar

Hi,

When trying to check my DVLS gateway logs I get the following error:

Devolutions Gateway is unreachable. Please make sure it is up and running.
DevolutionsGatewayUnreachable

Pushing the revocation list gives met this:

TypeError: Cannot read properties of null (reading 'length') at Object.next (https://dvls.be.jit-c.eu/dvls/chunk-5UHK4QTL.js:1:179627) at bi.next (https://dvls.be.jit-c.eu/dvls/chunk-56GO2EBD.js:3:3484) at we._next (https://dvls.be.jit-c.eu/dvls/chunk-56GO2EBD.js:3:3208) at we.next (https://dvls.be.jit-c.eu/dvls/chunk-56GO2EBD.js:3:2935) at https://dvls.be.jit-c.eu/dvls/chunk-56GO2EBD.js:3:15822 at Pi._next (https://dvls.be.jit-c.eu/dvls/chunk-56GO2EBD.js:3:13436) at Pi.next (https://dvls.be.jit-c.eu/dvls/chunk-56GO2EBD.js:3:2935) at o.subscribe.a (https://dvls.be.jit-c.eu/dvls/chunk-56GO2EBD.js:3:23503) at Pi._next (https://dvls.be.jit-c.eu/dvls/chunk-56GO2EBD.js:3:13436) at Pi.next (https://dvls.be.jit-c.eu/dvls/chunk-56GO2EBD.js:3:2935)

When pushing the test button I get this:

Success
Devolutions Gateway 'https://sbebrjump01.be.jit-c.eu:7171' is alive and healthy.


SETUP:

Devolutions server
subnet A (servers)
latest version
Windows Server 2025 datacenter (evaluation)

Devultuions gateway on subnet B (jump)
Subnet B (jump)
Linux ubuntu 22.04.5 LTS (jammy)
dvls gateway 2025.3.2
powershell latest
cerbot + acme dns plugin eurodns
certificates for client - gateway are generated by certbot and adjusted into the correct formats

Gateway status errors:

Revision error / update:

Certificate is now ok.
I've linked the json file directly to the fullchain.pem and privkey files certbot generates.

Nov 03 17:19:53 sbebrjump01 devolutions-gateway[28930]: 2025-11-03T16:19:53.590018Z INFO listener{port=7171}:https{client=10.100.0.2:59933}>
Nov 03 17:19:53 sbebrjump01 devolutions-gateway[28930]: 2025-11-03T16:19:53.628529Z ERROR listener{port=7171}:https{client=10.100.0.2:59934}>
Nov 03 17:20:41 sbebrjump01 devolutions-gateway[28930]: 2025-11-03T16:20:41.602349Z ERROR listener{port=7171}:https{client=10.100.0.2:59942}>
Nov 03 17:20:41 sbebrjump01 devolutions-gateway[28930]: 2025-11-03T16:20:41.602366Z INFO listener{port=7171}:https{client=10.100.0.2:59942}>
Nov 03 17:21:29 sbebrjump01 devolutions-gateway[28930]: 2025-11-03T16:21:29.833892Z ERROR listener{port=7171}:https{client=10.100.0.2:59944}>
Nov 03 17:21:29 sbebrjump01 devolutions-gateway[28930]: 2025-11-03T16:21:29.833940Z INFO listener{port=7171}:https{client=10.100.0.2:59944}>
Nov 03 17:21:38 sbebrjump01 devolutions-gateway[28930]: 2025-11-03T16:21:38.717003Z ERROR listener{port=7171}:https{client=10.100.0.2:59945}>
Nov 03 17:21:38 sbebrjump01 devolutions-gateway[28930]: 2025-11-03T16:21:38.730433Z ERROR listener{port=7171}:https{client=10.100.0.2:59947}>
Nov 03 17:21:38 sbebrjump01 devolutions-gateway[28930]: 2025-11-03T16:21:38.730487Z INFO listener{port=7171}:https{client=10.100.0.2:59947}>
Nov 03 17:21:45 sbebrjump01 devolutions-gateway[28930]: 2025-11-03T16:21:45.611778Z ERROR listener{port=7171}:https{client=10.100.0.2:59948}>
:request{method=PATCH path=/jet/config}: devolutions_gateway::middleware::log: duration=200.44µs status=401 Unauthorized
:request{method=GET path=/jet/heartbeat}: devolutions_gateway::http: error=401 Unauthorized at devolutions-gateway/src/middleware/auth.rs:17>
:request{method=POST path=/jet/jrl}: devolutions_gateway::http: error=401 Unauthorized at devolutions-gateway/src/middleware/auth.rs:178:28 >
:request{method=POST path=/jet/jrl}: devolutions_gateway::middleware::log: duration=199.29µs status=401 Unauthorized
:request{method=GET path=/jet/diagnostics/logs}: devolutions_gateway::http: error=401 Unauthorized at devolutions-gateway/src/middleware/aut>
:request{method=GET path=/jet/diagnostics/logs}: devolutions_gateway::middleware::log: duration=198.13µs status=401 Unauthorized
:request{method=GET path=/jet/heartbeat}: devolutions_gateway::http: error=401 Unauthorized at devolutions-gateway/src/middleware/auth.rs:17>
:request{method=GET path=/jet/diagnostics/configuration}: devolutions_gateway::http: error=401 Unauthorized at devolutions-gateway/src/middl>
:request{method=GET path=/jet/diagnostics/configuration}: devolutions_gateway::middleware::log: duration=203.12µs status=401 Unauthorized
:request{method=GET path=/jet/heartbeat}: devolutions_gateway::http: error=401 Unauthorized at devolutions-gateway/src/middleware/auth.rs:17>


Anyone any idea's ?

6065d955-9d08-4a3b-8648-d9899c15fdf1.png

64c2fc45-440b-4de9-aa30-498bcdde2d78.png

cf7e19f6-5d15-4025-9a67-3c700478a94f.png

89332e93-8f15-434f-83c2-b57c9480579c.png

All Comments (3)

avatar

HelloJitser ,

Based on the points we discussed, please check the following:

  1. Make sure the time is synchronized on both hosts.
  2. Verify the exact Gateway URL in DVLS by going to Administration > Devolutions Gateway > Gateways > Edit your gateway.
  3. Confirm that the URL is https://sbebrjump01.be.jit-c.eu:7171, matching the same FQDN and port covered by the certificate.
  4. Check the management key. On the Gateway side, run cat provisioner.pem and verify that the public key hash matches the one you can download from the Devolutions Server web interface under Administration > Devolutions Gateway > top-right ellipsis > Download public key. The two keys must be identical.


Best regards,

Michel Audi

avatar

@Michel Audi Thanks for the tip, it was the time synchronization within my windows domain lab environment which was off. (TimeZones did not line up.)
After removing the gateway and re-adding it, everything is ok now.

avatar

Hello Jitser,

Thank you for your input. That’s great it’s working for you now.
Please feel free to reach out if you have any further questions.

Best regards,

Michel Audi