register_member: confusing error when SSH password auth fails
Apra Fleet is an open-source MCP server
Brought to you by:
apralabs
Originally created by: kumaakh
When register_member is called with auth_type: password and either the password prompt doesn't appear (terminal window failed to open on Windows) or the wrong password is entered, the error returned is:
❌ Failed to connect to <host>:22 — All configured authentication methods failed
Member was NOT registered.
This message is identical regardless of cause:
The user cannot distinguish "wrong password" from "prompt didn't open" from "wrong host".
Additionally: the post-register hook fires and prints the onboarding checklist even when registration fails, which implies success.
Authentication failed (wrong password?) vs Connection refused vs TimeoutPassword prompt could not be opened — pass the password directly via thepasswordfieldregister_member with a valid host/port but wrong SSH password (or with a host where the GUI prompt doesn't open)
Originally posted by: kumaakh
Fixed in main: PR [#177] (fix: SSH username with spaces + improved SSH error messages) added
classifySshError()insrc/utils/ssh-error-messages.tswhich maps raw ssh2 errors to actionable messages: authentication failures, ECONNREFUSED (wrong host/port), ETIMEDOUT/ENOTFOUND (unreachable host), and OOB prompt failures. Applied inregisterMember()at the connection-failure return path. The onboarding hook was also verified to only fire on successful registration (the✅result path).Related
Tickets:
#177Ticket changed by: kumaakh