[BUG] Windows Client Fails Silently on Host Key Verification After Activating SSL

[pedro-fm-angelo]

Title

Windows Client Fails Silently on Host Key Verification After Activating SSL

Platform

App - Windows

Server Installation Method

Docker

Version

1.11.1

Troubleshooting

• I have examined logs and tried to find the issue
• I have reviewed opened and closed issues
• I have tried restarting the application
• I have read Known Issues (Known Issues (Read Before Posting) #296)

The Problem

When switching the Termix Docker container from HTTP to HTTPS/SSL, the Windows desktop client fails when connecting to any host, instead of prompting the user to accept the new host key like the browser client does.

How to Reproduce

1. Have Termix running over HTTP with hosts configured
2. Switch the Docker container to use SSL/HTTPS
3. Attempt to connect to any host in the Windows desktop client

Additional Context

Log from server:

Error in host key verification [op:host_key_error,user:...,host:3]
TypeError: protocol._destruct is not a function
    at doFatalError (/app/node_modules/ssh2/lib/protocol/utils.js:189:14)
    at /app/node_modules/ssh2/lib/protocol/kex.js:1208:26
    at file:///app/dist/backend/backend/ssh/host-key-verifier.js:102:25
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)

Workaround

Access Termix via the browser — it correctly shows a popup to confirm the new host key.

[ZacharyZcR]

Is this still reproducible on v2.0.0? If so, could you share the full server log output from the connection attempt, including the lines before the TypeError?

[pedro-fm-angelo]

@ZacharyZcR can confirm: prompt to accept the new host key appears in the Windows client and it can successfully login to the new host.
Thank you, good job!