SSH/SCP

linux/macos quickstart on ubuntu or mac, first you need to generate an rsa ssh public/private keypair using the command ssh keygen t rsa next you may need to force the daemon to load the new private key, and confirm it's loaded ssh add; ssh add l then get the contents of the public key with cat / ssh/id rsa pub copy the entire output to your clipboard, then paste that into the "change ssh key" text box under console/account the key text includes the opening "ssh rsa" part and the ending "user\@something" part if you don't copy the entire thing, it won't work example ssh key text ssh rsa aaaab3nzac1yc2eaaaadaqabaazbaqddxwwxwn5lz7ubkmrxm57chhvzonzult5fhi7j8zfxcjhfr96w+ccbobo2rtbbttrdlnjjisklgbcc3+jgyzhpunmfrvij7meqdehghfvuuv/ubkb7rjbyyfcb4bcsyngguzkmnnongea3aqtbszt47bnugqkszs9bfacapftr9wo0b8p4iyil/gfoy5kusvwkqrbcwrg53/+t2rak/02mwnhxybktjau1q9qtwcyo68jtdd0sa+4apsu+csjmbjs3fcddral3bcpikwrbckq+n63ol4xdv3zqrebuc98cjph04gnc41w02lmdqfl2xg5u/rv8/jm7cawkiiz3dbkv bob\@velocity you can use a few ssh keys by pasting in each on a new line troubleshooting if you encounter "permission denied (publickey)", then the most likely causes are you are trying to run an ssh or scp command from inside the instance didn't setup your keys correctly or using the wrong/mismatched keys used incorrect/unsupported ssh key format didn't actually load your private key correctly with ssh add, may need to use i argument changed the key on the account page too recently (can take a minute or two to propagate) incorrect permissions on your local / ssh directory or files can also cause this error the private key file (e g , id rsa) should have permissions set to 600, and the directory ` / ssh should be 700 you can usually determine the exact cause by using the vv arguments with ssh to get more info connecting to instance from vs code you might find this vscode remote development using ssh guide helpful tmux we connect you to a tmux session by default for reliability you can create a new bash terminal window with "ctrl+b,c" (press ctrl and b, followed by c), and switch with "ctrl+b,n" but google "tmux cheat sheet" or "tmux guide" for more info you can disable tmux by with touch / no auto tmux; (in a bash terminal or in your onstart) windows windows 10+ has native ssh support if you use the windows powershell to both generate the ssh key and to connect to the instance otherwise, windows does not support native ssh key generation or connection this guide covers free windows tools that can generate ssh keys, ssh into vast instances and transfer files back and forth between the windows machine and instances most machine learning and ai programming is done on linux we recommend biting the bullet and installing a linux subsystem on your windows machine, like wsl https //docs microsoft com/en us/windows/wsl/install you can then access the vast cli tooling and ssh into your vast instance with regular linux ssh keygen and connect commands windows powershell windows offers typical ssh access through the powershell the typical ssh linux commands will work in the powershell step 1 open the windows powershell terminal click on the search bar in the bottom right and type in powershell click on the windows powershell icon to open up a new session step 2 run the ssh key generation command if you do not already have a default ssh key (id rsa) run the ssh key generation command in the terminal ssh keygen t rsa you will be prompted to enter a file in which to save the key hit enter to save in the default directory you will then be prompted for a passphrase for simplicity, hit enter to for no passphrase next you will need to copy the contents of the public ssh key to paste into your vast account use the following command to output the public key and copy it to your clipboard get content $env\ userprofile/ ssh/id rsa pub | set clipboard step 3 add ssh key to account navigate to the account page of vast and go to the change ssh key section there you can add the ssh key you just generated to your account sshsection any instances you create will now have your ssh key attached to the instance this only applies to new instances existing instances will not have your ssh key and you will have to add it manually to the instance step 4 find the ssh connection string go to the instances page and look for a bright blue button that says 'open ssh interface' on the instance card click it and you should see a screen similar to this sshmodal the connecting string we want is ssh p 42114 root\@1 160 174 125 l 8080\ localhost 8080 find that string for the instance you want to ssh into copy it to your clipboard step 5 connect via powershell copy the ssh connection string into powershell when it prompts you for anything just say 'yes' if you see yourself logged into a vast ai container you have connected successfully! windows putty guide alternatively you can use windows putty tootls here is a video guide https //www youtube com/embed/kralvgfs4vu for those who prefer a video walkthrough the tools puttygen exe a key generator used to create an rsa keypair putty exe the ssh client used to connect to the instance winscp a gui for scp to allow for file transfer to/from the instance step 1 establish ssh keys start by downloading and running the appropriate version of puttygen exe make sure that the rsa key type is selected and then hit the "generate" button you will move your mouse cursor around to generate some randomness for the key then select the entire public key (double check you get every character starting with ssh) and copy it to the clipboard like this spaces mgwtdaam0bo2skpvyo6q uploads k4aqlsk4p3mu6hslszaa puttygen now login to your vast account paste the contents of your clipboard in the "change ssh key" section and hit the blue set ssh key button your new ssh key is now set for all new instances and will be propagated to running instances after 15ish minutes go back to puttygen you will need to change the key format before you can save the private key at the top level menu select key >parameters for saving key files that will pop up the dialog change the ppk file version to 2 hit ok to save the change spaces mgwtdaam0bo2skpvyo6q uploads aubfezfylw4fymptiude ppk save options now you can hit the "save private key" button to save your private key into a local folder ignore the passphrase warning remember where you store the key as you will need to specify the path to the key when using putty step 2 ssh into a vast instance now that you have your ssh keys setup, it is time to rent an instance first make sure you have added credits to your account then go to the create instance page and click on the edit image & config in the upper left of the interface to specify the os image and type typical os images such as pytorch are preloaded select an empty template slot to use a custom os image pick if you want jupyter installed or to run it as an ssh instance then select if you want direct connections are not while direct connections are faster, you will limit the machines you see to ones only with open ports use the rest of the filters to search for gpu type, number of gpus and other machine specifics spaces mgwtdaam0bo2skpvyo6q uploads b8rsl7uojnbrt12qrqua 4xgpu vast search once you find a machine you like and rent it, the os image will start to load on it afterwards you will get connection information for the proxy connection only or both the proxy and direct you will need the port number, which appears after the p and the hostname spaces mgwtdaam0bo2skpvyo6q uploads 0hdfneavk5f7l4njwhtq ssh connect open up putty exe you can then entire the hostname and port into the putty client spaces mgwtdaam0bo2skpvyo6q uploads byxavxkdyqhp4yqf6icj putty you will also need to select your private key file, by selecting ssh >auth >credentials on the left hand menu and then select your key file that you saved in step 1 putty auth the final step is to save your session information navigate back to the session information pane, type in a name in the saved session box and then hit save your keypath, hostname and ip address should now all be saved under that name and will be readable by winscp ⚠️ warning after saving the key it is easy to hit the open button which will connect putty however once you close that session, the session information is lost navigate back to the session tab and save the session before opening the connection hit open to open up your ssh connection the terminal will ask to add the key fingerprint (type yes) and then connect to the instance you are in! step 3 winscp for file transfer the final tool you will want to use with windows is winscp if you saved your session information in putty, the setup is trivial in winscp it will simply import your putty session information and then allow you to connect to that instance! spaces mgwtdaam0bo2skpvyo6q uploads l5shagyyo6b9hi3pa8xb winscp once the session information is imported, simply hit the login button to authenticate with the instance and then start transferring files by dragging them and dropping them between your local machine and the instance let us know if you found this guide helpful and how we could improve