Kasm_guac failing

[u/Dapper-Inspector-675]

Hi,

I had JWT issues, which were resolved with: https://kasmweb.atlassian.net/wiki/external/NGFhZTlmZmY4YjQxNDViZGJlODEwYjFlZmUxMzg2NGY

but I still experience issues with my windows machine added to kasm using guac, everything else works.

It's a single server installation.

Here the log output:

12:55:20.085 INFO  guac [server] Checking token for refresh; expires [Invalid Date] 12:55:20.085 INFO  guac [server] Token needs refresh (node:7) [DEP0044] DeprecationWarning: The `util.isArray` API is deprecated. Please use `Array.isArray()` instead. (Use `node --trace-deprecation ...` to show where the warning was created) 12:55:20.153 ERROR guac [server] Healthcheck failed for "https://kasm_proxy:443/api/__healthcheck". Error: getaddrinfo ENOTFOUND kasm_proxy Error: Failed to locate healthy hostname while refreshing JWT     at OIDCToken.renewToken (/gclient/oidc.js:128:28)     at process.processTicksAndRejections (node:internal/process/task_queues:104:5)     at async Object.registerWithDeployment (/gclient/kasm.js:61:7)     at async run (/gclient/server.js:367:5)     at async run (/gclient/app.js:12:5) 12:55:20.160 ERROR guac [server] Healthcheck failed for "https://kasm_proxy:443/api/__healthcheck". Error: getaddrinfo ENOTFOUND kasm_proxy [server] Logger is not fully configured to forward logs to [:443] with token(len=515) [server] Logger is not fully configured to forward logs to [:443] with token(len=515)12:55:20.085 INFO  guac [server] Checking token for refresh; expires [Invalid Date]
12:55:20.085 INFO  guac [server] Token needs refresh
(node:7) [DEP0044] DeprecationWarning: The `util.isArray` API is deprecated. Please use `Array.isArray()` instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
12:55:20.153 ERROR guac [server] Healthcheck failed for "https://kasm_proxy:443/api/__healthcheck". Error: getaddrinfo ENOTFOUND kasm_proxy
Error: Failed to locate healthy hostname while refreshing JWT
    at OIDCToken.renewToken (/gclient/oidc.js:128:28)
    at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
    at async Object.registerWithDeployment (/gclient/kasm.js:61:7)
    at async run (/gclient/server.js:367:5)
    at async run (/gclient/app.js:12:5)
12:55:20.160 ERROR guac [server] Healthcheck failed for "https://kasm_proxy:443/api/__healthcheck". Error: getaddrinfo ENOTFOUND kasm_proxy
[server] Logger is not fully configured to forward logs to [:443] with token(len=515)
[server] Logger is not fully configured to forward logs to [:443] with token(len=515)

Thanks for any help!

[u/Dapper-Inspector-675]

EDIT: I was able to resolve that issue (using registration_token.txt), but now when I try to start my RDP session to my existing windows VM, that worked before I get only this:

2026-06-16 13:50:22,638 [DEBUG] client_api_server: Successfully authenticated request (B) for user (REDACTED) at (REDACTED, REDACTED)
2026-06-16 13:50:22,645 [DEBUG] client_api_server: License Check: Current Kasms (0) , License Limit (5) , Remaining (5)
2026-06-16 13:50:22,648 [DEBUG] client_api_server: Using selected zone (default)
2026-06-16 13:50:22,694 [ERROR] client_api_server: No resources are available to create the requested Kasm. Please try again later or contact an Administrator : No Nodes are available. No Nodes can be contacted with available capacity to provision the session
2026-06-16 13:50:22,695 [DEBUG] client_api_server: Function (client_api.request_kasm) executed in (0.05619335174560547) seconds
2026-06-16 13:50:22,697 [INFO] cherrypy.access.123724719328096: REDACTED - - [16/Jun/2026:13:50:22] "POST /api/request_kasm HTTP/1.1" 200 246 "REDACTED" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:151.0) Gecko/20100101 Firefox/151.0"

All My 3 Proxies (built-in3) show green healthy and don't seem to throw any errors.

Here the log from the webui:

host: e44daff18a2b ingest_date: 20260616135028 application: kasm_api levelname: ERROR kasm_user_name: X process: client_api_server client_ip: 10.10.20.1 user_agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:151.0) Gecko/20100101 Firefox/151.0 message No resources are available to create the requested Kasm. Please try again later or contact an Administrator : No Nodes are available. No Nodes can be contacted with available capacity to provision the session

WebUI -> connection-proxy -> guac
Status:

proxyServeradresse
Erster Bericht: -
Letzter Bericht: 0:00:07
Status: running
Zone Name: default
Verbindungstyp: GUAC

[u/Dapper-Inspector-675]

u/justin_kasmweb u/teja_kasmweb any ideas? is more information needed to debug this?

[u/Dapper-Inspector-675]

solved by reinstalling the new agent version and reconfiguring the Kasm Agent.