Looks like rebooting the server helps. Try to login through the console (although having the caps lock stuck) and issue the reboot command: sudo reboot
You will be logged out. After the reboot login again.
Hope this helps!

Same problem here (while setting up SSH– incredibly frustrating!)

My workaround had been to hold SHIFT for lowercase, which is fun while editing ssh_config in vim.

In case it saves someone some frustration, you can tell the console that caps lock is on with the command:

setleds -D +caps

…which will negate the confused console app. (Actual caps lock key may work, but mine is remapped to CTRL)

Oh, and yes, the problem began when I pasted my public key into the terrible console app. After failing for several minutes to configure sshd to allow password-based authentication, the ultimate solution was to put the public key in a pastebin and wget / curl it from the console.

Press Alt Gr once

I’m having this same problem however I am on a Dell XPS 13 9350 and there is no “Alt Gr” key on the keyboard.

Caps lock is out of sync. Happened when I tried to paste text into the console. I have a mac. I haven’t found a solution yet.

the console is dysfunctional to the point of being unusable. caps lock, and various other issues. not clear how to add the authorized_keys in, trying through console.

it is a chicken and egg question, how to get the login set up.

a nightmare

This is bs, so annoying

Shift+Caps Lock fixed the issue for me

Same problem here - console unusable!!!

this has been an issue for 4 years? typing seems fine, but copying and pasting in to the terminal changes the casing - completely unusable

Same is happening to me, I even tried rebooting but it didn’t help. I’m on MacOS and it all started after a copy paste… Problem is I need to add a new SSH manually (i changed my client) and the only way I can do it is from the web console… Any ideas?

Try running “reset” in the terminal

For all of you: I wasn’t able to fix this, but using PuTTY is a blessing anyways, as that console is way more responsive

The best way during a new droplet creation is create a new key (if you don’t already have one) with PuTTyGen tool. Then, on the new droplet screen click Add Key, paste in the key contents. Once the droplet is done creating, login with user root but reference the key you just created or your existing key. like this: ssh -i /path/to/private/key root@203.0.113.0

Works every time!

COMEON DIGI DO SOME SHIT ON IT

This is beyond useless. I can’t find any way to add an ssh key to my authorized_keys file.