From 94737e700fe0c53b262c5df0ff02890ffe89a5f1 Mon Sep 17 00:00:00 2001 From: Alvaro Gonzalez Date: Thu, 23 Jan 2025 14:00:59 +0200 Subject: [PATCH] Update docs/support/faq/why-cant-i-connect-to-my-vm-in-pouta.md Co-authored-by: Tristan <74349933+trispera@users.noreply.github.com> --- docs/support/faq/why-cant-i-connect-to-my-vm-in-pouta.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/support/faq/why-cant-i-connect-to-my-vm-in-pouta.md b/docs/support/faq/why-cant-i-connect-to-my-vm-in-pouta.md index 9aba6030a5..18a6ae1b40 100644 --- a/docs/support/faq/why-cant-i-connect-to-my-vm-in-pouta.md +++ b/docs/support/faq/why-cant-i-connect-to-my-vm-in-pouta.md @@ -112,7 +112,7 @@ The fingerprints must match. ![Instance log](../../cloud/img/log-instance.png) - You will be able to see the username, the file where the keys are configured and the list of finger prints of the configured keys. In the exampe above the output shgows the `MD5` algorithm. + You will be able to see the username, the file where the keys are configured and the list of finger prints of the configured keys. In the example above the output shows the `MD5` algorithm. If you do not find the corresponding private key, you will need to either [re-create the VM](../../cloud/pouta/launch-vm-from-web-gui.md)) with a ssh key pair that you own and control, or use our [How to rescue instances?](./pouta-openstack-rescue-mode.md) guide to be able to access the VM's disk and change the public key installed in the `authorized_keys` file. This last option is complex and it is only needed if you already have data and/or software in the VM's local disk. If you need to follow this second option, but are confused on how, please create a ticket with us at , we will help you step by step.