Changes between Version 59 and Version 60 of Documentation/bAccountManagement/DSSHConf

Timestamp:

Jun 21, 2018, 10:12:10 PM (6 years ago)

Author:

jkol

Comment:

—

Documentation/bAccountManagement/DSSHConf

@@ -71 +71 @@
  You should be prompted to enter your key file passphrase and be able to successfully connect.
 
+ Type {{{exit}}} and press the Enter key to end the SSH session.
+
 [[BR]]
 ==== Common issues and how to solve them ====
@@ -160 +162 @@
  1. Open PuTTY
 
- 2. 
+ || [[Image(putty.png, 250px)]] ||
+
+ 2. Navigate through the left side menu tree to "SSH" then "Auth"
+
+ || [[Image(putty.png, 250px)]] ||
+
+ 3. Click the "Browse" button next to the "Private key file for authentication" field
+
+ || [[Image(putty.png, 250px)]] ||
+
+ 4. Navigate through the left side menu tree back to "Session"
+
+ || [[Image(putty.png, 250px)]] ||
+
+ 5. Enter a name for this connection in the "Saved Sessions" field and click the "Save" button
+
+ || [[Image(putty.png, 250px)]] ||
+
+ 6. Now any time you open PuTTY, select the session name you gave in the previous step and click "Load", this will load the private key file automatically (as long as you do not move it to a different folder on your computer).
+
+ || [[Image(putty.png, 250px)]] ||
+
+ 7. Type {{{your_orbit_username@gw.orbit-lab.org}}} into the "Host Name (or IP address)" field and click the "Open" button. You should be prompted to enter your key file passphrase and be able to successfully connect.
+
+ || [[Image(putty.png, 250px)]] ||
+
+ 9. Type {{{exit}}} and press the Enter key to end the SSH session.
 
 [[BR]]
 ==== Common issues and how to solve them ====
- * TODO
+ * If you receive a message like the following:
+{{{
+The authenticity of host 'gw.orbit-lab.org (128.6.192.134)' can't be established.
+ECDSA key fingerprint is SHA256:iLKtq2Z8wB3ADJdEyM1CwoU85gOeqIUyB4GOJ2YloQg.
+Are you sure you want to continue connecting (yes/no)?
+}}}
+ This is a normal message that occurs when your computer connects via SSH to another that it has never connected to before or if the "fingerprint" of the other machine changed (due to replacement or reconfiguration). Simply type {{{yes}}} and connection will proceed normally.
+[[BR]]
 
 [[CollapsibleEnd]]