Wrong keyboard layour on recovery console

I was in the middle of editing a file with nano when I accidentally pressed some buttons when I just wanted to save the file. There hell started…

Basically I somehow managed to change the keyboard layouut of the DigitalOcean recovery console.

Everithing is fine over ssh it is just the recovery console…

AnyhowI would like to know how to fix the issue as the keys are all over the place and the character# now is impossible to be found (so usfull for config files).

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.


Solution for Centos 7.0

do you install “yum install kbd” package console recovery if exist then and start command this “loadkeys us” for initial correct map keyboard.

start command “localectl set-keymap us” or your “map keys” try maps first and launch for confirm change

only command “localectl” ok??


Hello, all

The Droplet web console provides out-of-band access and is available regardless of your network settings. It emulates the access you would have if you were sitting down with a keyboard and monitor attached to the actual server. You can use this feature to log in and revert bad settings to regain normal access.

Also the Copy/Paste functionality of our web console is a bit odd; the code backing it is custom due to the way the VNC window is implemented for accessing your Droplet. It isn’t a good idea, in my experience, to rely on the console for long copy/pasting like an SSH key.

I will highly recommend you to use a ssh client for you daily tasks such as editing files and changing system configuration.

As mentioned you will usually use the console if you can’t access your droplet using ssh via a ssh client and it’s usually the last resort option when it comes to troubleshooting.

You can also check our docs on How to Connect to Droplets with SSH:

There are two options at the bottom of the doc: Connect with OpenSSH and Connect with PuTTY

Hope that this helps! Regards, Alex

I think the question is more complicated than that, because I have been testing it and none of the existing keyboards match the configuration, some keys jus don´t work at all and other characters are duplicated in differet keys. It only applies to characters, letters are fine.

As I said befere all good over ssh.