Skip to content

Commit be0b44c

Browse files
bene2k1RoRoJ
andauthored
Update pages/instances/troubleshooting/cant-connect-ssh.mdx
Co-authored-by: Rowena Jones <[email protected]>
1 parent ee69082 commit be0b44c

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

pages/instances/troubleshooting/cant-connect-ssh.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ When you create your Instance, check step 6 of the creation wizard and make sure
3434

3535
- You can view and manage your public SSH keys from the [credentials section of the console](https://console.scaleway.com/project/credentials).
3636
- Credentials are specific to each [Project](/organizations-and-projects/concepts/#project) of your Organization.
37-
- If you [add a new public key to your Project credentials](/organizations-and-projects/how-to/create-ssh-key/#how-to-upload-the-public-ssh-key-to-the-scaleway-interface) **after** creating a new Instance, it will not automatically be uploaded to the existing Instance. You can either reboot your Instance to transfer the new key to it during the boot process or manually run the command `scw-fetch-ssh-keys --upgrade` to download the new key to the Instance.
37+
- If you [add a new public key to your Project credentials](/organizations-and-projects/how-to/create-ssh-key/#how-to-upload-the-public-ssh-key-to-the-scaleway-interface) **after** creating a new Instance, it will not automatically be uploaded to the existing Instance. You can either reboot your Instance to transfer the new key to it during the boot process or manually run the command `scw-fetch-ssh-keys --upgrade` to upload the new key to the Instance.
3838

3939
### Check that you have the correct private key on your local machine
4040

0 commit comments

Comments
 (0)