Shift+Caps Lock fixed the issue for me

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.

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

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!

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

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.

This is bs, so annoying

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

COMEON DIGI DO SOME SHIT ON IT

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.

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!

Have same issue. Costed me two hours of my life. Happened after copy-pase ssh key. Solved only via rebooting droplet several times.

This is ridicuous - copying password does not work, as it comes with case toggled.

Gods, this console app is so bad and buggy…

If you print ’>’ in this stuck-caps mode, keys are ok for me. Try typing ’>reset’ and removing the >.

PS
Figured this out accidentally pasting an html code while trying to emulate keypressess from js:) This console should not exist in such an evil form

Double tapping shift worked for me.

<<Work-Around to paste ssh keys>> When using the clipboard to copy an SSH key then paste into the console terminal the shift/cap-lock will show up as it’s pasting the contents of the clipboard. To avoid this behavior, copy the key in smaller pieces (less characters at a time) and paste each to form the full key in the console terminal.

A workaround for adding your SSH key: host a Python file server, use NGrok to get public URL, fetch it from your Digital Ocean box.

# For MacOS:

mkdir /tmp/serve
cp ~/.ssh/id_rsa.pub /tmp/serve/ # Copy since ~/.ssh also contains id_rsa
cd /tmp/serve/
python -m SimpleHTTPServer 8000 # Leave this running

# Create new tab: Cmd + T
brew install ngrok # See https://dashboard.ngrok.com/get-started
ngrok http 8000 # Leave this running. Use HTTPS URL below

# From Digital Ocean box:
mkdir ~/.ssh
chmod 711 ~/.ssh

curl -s https://{ngrok id here}.ngrok.io/id_rsa.pub >> ~/.ssh/authorized_keys
chmod 600 ~/.ssh/authorized_keys

# Voilà!

You can now SSH into your box.

Got the issue too. VERY annoying. Ended up:

• creating a quick git public repository
• add a file
• click on “raw” button and look at URL
• curl https://raw.githubusercontent.com/human/readable/url >> .ssh/authorized_keys
• delete git repository.

Done.

Now I can use my favorite SSH client that works.