Console stuck in caps lock mode?
Not sure how it happened, but my droplet's console (the browser one) is stuck in caps lock mode. How can I get it back to normal?
14 Answers
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!
-
Reboot was the solution for me. Unfortunately the terminal did not recognize the command when entered with caps, so I needed to reboot via droplet -> power -> powercycle. Thanks!
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.
-
I was having a similar issue but it turned out the caps lock was out of sync, ie. when my windows was in caps lock, the console was not and vice versa. Not sure yet how to correct this, but it's manageable at present lol.
-
I think the issue I was having with the Digital Ocean web console is related to the Logitech Mouse and Keyboard Settings app on my Windows PC. When I exit that, there is no problem. Not sure that is what you are running into but just thought I would mention it.
-
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
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.
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?
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 another answer? Share your knowledge.
This is happening to me also. Although it's always been caps lock for me. Really strange.
This issue was posted four years ago with over 5k views, but no solution yet… I wonder how may devs have wasted hours and ultimately ditched DigitalOcean because of this.