Connect to Your Instance Via Openssh on MacOS or Linux

Connect to your FCS Instance through an opened terminal on linux or MacOS. If you don't have Bash on Windows, use PuTTY instead.

The username for CentOS and Ubuntu are root, respectively. Enter the following SSH command in the opened terminal. 

ssh username@server_ip

For multiple SSH keys, specify the path to your private key using the -i flag, like this; ssh -i /path/to/your_private_key username@server_ip.

The username for CentOS and Ubuntu are root, respectively Ensure you substitute your FCS Instance's IP address after the @.

At first log in, the server isn't known to your localhost, so you'll be prompted if you're sure you want to continue connecting. Type yes and then press ENTER.

                The authenticity of host 'server_ip (server_ip)' can't be established.
                ECDSA key fingerprint is SHA256:uvbiwhb85hdPiZPc1FOZp4s30O1TGzVjsh6IGkmK8CM.
                Are you sure you want to continue connecting (yes/no)? yes

Then, the host key fingerprint is saved to your local machine and you'll receive this confirmation:

Warning: Permanently added 'server_ip' (ECDSA) to the list of known hosts.
Note

You may receive a remote host identification warning:

                
                @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
                @    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
                @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
                IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
                Someone could be eavesdropping on you right now (man-in-the-middle attack)!
                It is also possible that a host key has just been changed. 
                The fingerprint for the ECDSA key sent by the remote host is
                SHA256:uvbiwhb85hdPiZPc1FOZp4s30O1TGzVjsh6IGkmK8CM.
                Please contact your system administrator.

This happens most often when you've destroyed a FCS Instance immediately before creating and trying to connect to a new one. If the new FCS Instance gets assigned the same IP address as the FCS Instance that was destroyed, the host key of the old server is stored and conflicts with the new host key.

If this happens, you can delete the old FCS Instance's host key from your local system with the command ssh-keygen -R server_ip and then reconnect.

This is followed by an authentication. If you've already added SSH keys (and the optional key passphrase), you can now establish a secure connection to the FCS Instance.

If you haven't added SSH keys, you'll be prompted for your password:

root@server_ip's password:

When you enter your password, nothing is displayed in the terminal, so it can be easier to paste in the initial password. You can also right-click to paste if you enable QuickEdit mode.

Once you've entered the password, press ENTER.

Default passwords aren't secure, so the first time you log in with the default password, Please change it.


                Changing password for root.

To do that, first re-enter the current password, then press ENTER. Nothing displays on the screen when you type.

On Linux : # sudo passwd root
 (current) UNIX password :

After that, enter your new password and press ENTER. Again, nothing displays on the screen as you type. You'll be asked to supply the new password a second time to confirm that you've typed it accurately.

Enter new UNIX password:
                Retype new UNIX password:

When you've successfully logged in, you'll receive an operating system-specific welcome screen. Your command prompt changes to display the username you've logged in as, separated by the @ symbol from the hostname of the FCS Instance, like root@ubuntu-:~#.

If you're having trouble connecting to your FCS Instance with SSH, you can try connecting with the FCS Instance console to recover normal SSH access.