How to I make an SSH connection?

Connections
1

First you will need to make sure that SSH is enabled and running & Remote.It is installed and configured on the device you want to connect to (target device):

  1. Refer to your device OS documentation to enable SSH if you do not know how to do so.
  2. Install Remote.It on the device by logging into https://app.remote.it or the Remote.It desktop application and clicking the “+” (Add device) icon, then selecting your device type.
  3. Follow the installation instructions (most cases it is copying the command and pasting it into a command line on your target device)
  4. After it registers, make sure that you have an SSH service and that it is online.

Make your connection:
From the computer or device which is going to be using the connection, for example your Windows desktop.:

  1. Open https://app.remote.it or the Remote.It Desktop Application
  2. Search for or click on your device from the device list.
  3. Click on the “Connect” button on the SSH service when on the device page.
  4. Once connected, Remote.It might prompt you for the username for the login. Enter that (it is case sensitive)
  5. Click launch if it doesn’t launch automatically.
    Remote_It_Application
    Remote_It_Application1556×950 95.7 KB

You may want to use a different application such as putty for your SSH connections and/or want to use launch commands to pass keys. See this article on setting connection defaults https://link.remote.it/support/connection-settings

2

Some Mac users have discovered that SSH is not working on their Mac since updating to macOS Ventura 13 or newer, including Sonoma. Typically you will see a “no matching host key type found. Their offer: ssh-rsa“ or “kex_exchange_identification: Connection closed by remote host” when this occurs.

The cause is that the version of OpenSSH that ships with MacOS Ventura disables RSA signatures by default, thus you can resolve the problem by either using a more secure hash, or by allowing for RSA signatures.

You can also refer to this post. My SSH connections are failing with kex_exchange_identification