Skip to content

Commit

Permalink
Update docs/support/faq/why-cant-i-connect-to-my-vm-in-pouta.md
Browse files Browse the repository at this point in the history
Co-authored-by: Tristan <[email protected]>
  • Loading branch information
lvarin and trispera authored Jan 23, 2025
1 parent e828bdb commit 94737e7
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/support/faq/why-cant-i-connect-to-my-vm-in-pouta.md
Original file line number Diff line number Diff line change
Expand Up @@ -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 <[email protected]>, we will help you step by step.

Expand Down

0 comments on commit 94737e7

Please sign in to comment.