Differences

This shows you the differences between two versions of the page.

--- ssh_login_nopass [2026/04/29 14:21] – pwolinsk
+++ ssh_login_nopass [2026/05/10 21:44] (current) – pwolinsk
@@ Line 1: / Line 1: @@
-====SSH Password-less Login====
+==== SSH Password-less Login ====
-The secure shell (SSH) server on **hpc-portal1.hpc.uark.edu**  does not accept passwords as an authentication method for the SSH protocol.  Instead SSH key files are used for access.  A public SSH key file is stored in your account on Pinnacle.  You must supply a matching private key (pinnacle.key) file as a parameter to the ssh command on the client to log in.
+The secure shell (SSH) server on **hpc-portal2.hpc.uark.edu** does not accept passwords as an authentication method. Instead, SSH key files are used for access. A public SSH key file is stored in your account on Pinnacle. A matching private key (pinnacle.key) file has to be supplied as a parameter to the ssh command on the client to log in.
 <code>
-ssh -i pinnacle.key ffinfinn@hpc-portal1.hpc.uark.edu
+ssh -i pinnacle.key ffinfinn@hpc-portal2.hpc.uark.edu
 </code>
-Both private and public keys are generated and configured automatically via the web portal using **Clusters->SSH keys** option in the top menu.
+Both private and public keys are generated and configured automatically on Pinnacle via the web portal. To enable SSH password-less access:
-{{:hpc-portal1-auth5.png?400|}}
+**1.** Log into the web portal at: https://hpc-portal2.hpc.uark.edu
-At this point the public key is configured in your account.  Next you have to download the private key file to your local computer.  Click on  **Create New SSH Key** or **Use Existing SSH Key** button if you have already created SSH keys previously.
+**2.** In the top menu go to **Clusters -> SSH keys**
-Both buttons will redirect your browswer to a file manager window allowing you to download your private SSH key **pinnacle.key** file to your client device.  Once downloaded, the file permissions have to be updated on MacOS and Linux devices to "400" before you can use your key for SSH.
+{{:hpc-portal1-auth5.png?400|SSH keys menu}}
+**3.** Click on **Create New SSH Key** or **Use Existing SSH Key** if available.
+Both buttons will redirect your browser to a file manager window allowing you
+to download your private SSH key **pinnacle.key** file to your client device.
+{{:hpc-portal1-auth6.png?400|SSH key download}}
+**4.** Click on the checkbox next to the **pinnacle.key** file and press the
+**Download** button at the top. The file will likely be saved to your **Downloads** directory.
+**5.** Before you can use the file for SSH, the file permissions must be updated
+to read-only for owner, mode ''400'' on MacOS and Linux:
+<code>
+cd Downloads/
+chmod 400 pinnacle.key
+</code>
+**6.** Use the new key to SSH into Pinnacle:
+<code>
+ssh -i pinnacle.key ffinfinn@hpc-portal2.hpc.uark.edu
+  ************ PLEASE CITE AHPCC ********** in your publications ***************
+  ******************************************************************************
+  **    This research is supported by the Arkansas High Performance Computing **
+  **    Center which is funded through multiple National Science Foundation   **
+  **    grants and the Arkansas Economic Development Commission.              **
+  ******************************************************************************
+  Login nodes are for file operations and job submission.
+    - Don't run R or Python on login nodes.
+  To start an interactive job on a shared cloud compute node:
+     srun -N1 -n1 -c1 -p cloud72 -q cloud -t 72:00:00 --pty /bin/bash
+Last login: Fri Apr 10 10:14:51 2026 from 167.224.131.232
+      Pinnacle file system usage for ffinfinn
+          Filesystem                Usage/Quota               Files/Quota
+              /scrfs               4.059T/10TB             21798831/10.0 million
+               /scr1                  16k/ 1TB                    4/ 2.5 million
+               /scr2                  96k/ 1TB                   24/ 2.5 million
+pinnacle-l11:ffinfinn:$
+</code>