From ee69082609f353c243f927a04a6f7514a75030e2 Mon Sep 17 00:00:00 2001 From: Benedikt Rollik Date: Wed, 24 Sep 2025 11:59:28 +0200 Subject: [PATCH 1/2] docs(ins): fix wrong doc --- pages/instances/troubleshooting/cant-connect-ssh.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/instances/troubleshooting/cant-connect-ssh.mdx b/pages/instances/troubleshooting/cant-connect-ssh.mdx index 62851472b8..8c2caca71f 100644 --- a/pages/instances/troubleshooting/cant-connect-ssh.mdx +++ b/pages/instances/troubleshooting/cant-connect-ssh.mdx @@ -34,7 +34,7 @@ When you create your Instance, check step 6 of the creation wizard and make sure - You can view and manage your public SSH keys from the [credentials section of the console](https://console.scaleway.com/project/credentials). - Credentials are specific to each [Project](/organizations-and-projects/concepts/#project) of your Organization. -- 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. Scaleway only uploads the public SSH keys specified at the time of the Instance's creation. To add a new public SSH key after that point, you will need to connect to your Instance and add the additional public key yourself. Public keys are stored by default in `~/.ssh` with a filename similar to `id_rsa.pub`. +- 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. ### Check that you have the correct private key on your local machine From be0b44c9174c9c090e82c135caa1470ec62c0ba5 Mon Sep 17 00:00:00 2001 From: Benedikt Rollik Date: Wed, 24 Sep 2025 12:03:49 +0200 Subject: [PATCH 2/2] Update pages/instances/troubleshooting/cant-connect-ssh.mdx Co-authored-by: Rowena Jones <36301604+RoRoJ@users.noreply.github.com> --- pages/instances/troubleshooting/cant-connect-ssh.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/instances/troubleshooting/cant-connect-ssh.mdx b/pages/instances/troubleshooting/cant-connect-ssh.mdx index 8c2caca71f..c21f8c26d6 100644 --- a/pages/instances/troubleshooting/cant-connect-ssh.mdx +++ b/pages/instances/troubleshooting/cant-connect-ssh.mdx @@ -34,7 +34,7 @@ When you create your Instance, check step 6 of the creation wizard and make sure - You can view and manage your public SSH keys from the [credentials section of the console](https://console.scaleway.com/project/credentials). - Credentials are specific to each [Project](/organizations-and-projects/concepts/#project) of your Organization. -- 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. +- 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. ### Check that you have the correct private key on your local machine