Error codes · Terminal

PULSE-TERM-002 Can't connect to SSH host

What does this mean

Pulse asked system ssh log in to the saved host - check the connection, show folders for “Where is the project on the host” or confirm the project path, - and ssh didn't enter. The host remains in the list; tasks cannot be created on it yet.

Why does this happen

Pulse doesn't keep its SSH client: it runs ssh this computer with your keys, ~/.ssh/config and known_hosts, no passwords (BatchMode). Therefore, the reasons are the same as for ordinary ssh in the terminal, and written on the card with the words ssh: “Connection rejected” - sshd is not running on the host or the port is closed; “Host unreachable” and “Host name not found” - network, VPN or typo in the address; “SSH rejected key” - the host did not accept your key or user; “SSH host is not trusted” - the host fingerprint has not yet been recorded in known_hosts, and Pulse does not accept fingerprints itself; “The SSH host key has changed” - the fingerprint does not match the one recorded, this should be checked with the administrator.

What to do

  1. Open a terminal and log into the host normally ssh same address: ssh user@host -p 22. If he asks about the fingerprint, answer yes, and known_hosts the host will remember.
  2. If ssh asks for a password - configure the key: ssh-copy-id user@host, or specify the path to the key in the host form (“Key”). Pulse does not store passwords.
  3. Check the address, port and user in “Settings → Remote hosts → Edit” and click “Connect” again.

When to write to support

If normal ssh enters from the terminal, but Pulse does not, click “Send report”: diagnostics will go into it ssh from "More" (addresses and hostnames are hidden in it), and we will see how the Pulse call differs from yours.