📺 Video tutorial
If you're more of a visual learner, watch the video walkthrough of this tutorial.
|SSH Key File||cn_node_id|
|Remote IP address of our VPS|
|SSH Key Pair File Location|
|Local System||The system used to access our remote VPS|
|Remote System||The system (VPS) we created in the prior documentation (DO, AWS, or GCP) that we are connecting to|
|[...]||Indicates redacted text and/or information|
pretending our remote location (VPS) has an external IP address of
184.108.40.206 and our user name is
netmet ⬅️ do not use this!
Open up a new terminal session
- Click on the desktop to change your top menu bar to
- Click on
- Click on
Lets use the SSH command to connect to our VPS. Issue the
ssh command, including the
-i option to tell SSH to use our specific
identity file (ssh key file).
Issue these commands from your Local System to connect to the
IP address of your Remote System.
You may need to remove the ~/.ssh/ from the command if you did not save your SSH keys to the .ssh hidden directory.
Different cloud providers use different default users to access your VPS for the first time. GCP and DO use
root while AWS uses
ubuntu. We will use
root in our examples... make sure to change this to
ubuntu if you are using AWS, or review the documentation for the provider of your choice to determine their default username.
ssh -i ~/.ssh/cn-node-id firstname.lastname@example.org
SSH key passphrase to access your remote node.
When you are entering in your password, the key strokes will NOT be shown. It may seem like you are not entering in anything. This is a security measure.
Do not look at the screen as you are typing, this may help you to not make a mistake.
Output will look like below
Enter passphrase for key '/home/netmet/.ssh/cn_node_id':
We should now be challenged with a WARNING message about the authenticity of our SSH keys. We can accept this warning because we know that we just created them.
$ ssh -i ~/.ssh/id_cn_node email@example.com
The authenticity of host '220.127.116.11 (18.104.22.168)' can't be established.
ED25519 key fingerprint is SHA256:rGh+b304FFJeXct7xYU000=dkfjrEskafjDDjancifO.
This key is not known by any other names
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Access is granted!
Welcome to Ubuntu 20.04.3 LTS (GNU/Linux 5.4.0-89-generic x86_64)
* Documentation: https://help.ubuntu.com
* Management: https://landscape.canonical.com
* Support: https://ubuntu.com/advantage
System information as of [...]
System load: 0.34 Users logged in: 0
Usage of /: 2.1% of 154.90GB IPv4 address for eth0: 22.214.171.124
Memory usage: 5% IPv4 address for eth0: 10.17.0.6
Swap usage: 0% IPv4 address for eth1: 10.108.0.4
Last login: Thu [...]
Certain information was redacted from the output above.
From the instance output above above.
root@nodegarage : the
nodegarage would show as the
hostname that you supplied during the build process, in the previous steps. You may also see a
$ instead of a
#, this does not matter.
You should not use
NodeGarage as your
hostname. However, it should not make a difference in performance or functionality.
You are accessing on your remote system through your local system.