First Connection

After installing and launching Nexa, connecting to your first server only takes a few simple steps.

1. Create a New Server

In the left sidebar of the main interface, click the "+" button at the top (or use the shortcut Ctrl+N / Cmd+N), and select "New Connection".

The main workspace will now expand the connection configuration panel.

2. Fill in the Details

In the configuration panel, you need to provide the following core information:

• Name: Give this server an easily recognizable name (e.g., Production-DB).
• Host: Enter the IP address or domain name of the server.
• Port: Defaults to 22. If your server uses a custom SSH port, change it here.
• Username: Usually root or another user you created on the server (e.g., ubuntu, centos).

Authentication Method

Nexa supports two main authentication methods:

• Password: Enter the login password for the user directly into the password field.
• Private Key (Recommended):
  1. Switch the authentication method to "Private Key".
  2. Click browse to select your local private key file (e.g., ~/.ssh/id_rsa or a .pem file).
  3. If your private key is password-protected, enter it in the Passphrase field.

3. Save Connection

Once the information is filled out, click the "Save" button at the bottom right. Your newly created server will appear in the server list on the left. Nexa uses industry-standard encryption to securely store your credentials locally.

4. Open Terminal

Double-click the newly created server in the left list (or right-click and select "Connect"). Nexa will immediately open a new tab and attempt to establish the connection. If this is your first time connecting to this server, Nexa will prompt a Host Key verification window. Click "Accept and Save".

Wait a moment, and when you see a prompt like root@hostname:~#, congratulations, you've connected successfully!

---

Common Connection Failures

If you encounter errors while connecting, please check the following:

1. Connection Refused
   • Is the SSH service (sshd) running on the server?
   • Is the port number correct? (Some cloud providers use ports other than 22 by default).
2. Connection Timed Out
   • Check if the host IP address is correct and if it has a public IP or is in the same local network.
   • Check the cloud provider's security group/firewall settings to ensure the SSH port is open.
3. Authentication Failed
   • The username or password was entered incorrectly.
   • If using a key, ensure the server's ~/.ssh/authorized_keys contains the public key corresponding to the private key you used.