I have the solution! To those who are stuck click on the window and press one of these combinations.
one of the letters will end up "exiting" the program that is running. Allowing you to type again!
The Digital Ocean console did not work for me either. I tried to add an SSH key to
.ssh/authorized_keys with the DO console because I could not SSH into the droplet from a new computer because of "permission denied (publickey)". When I pasted in my new SSH key, it got altered. For example "ssh-rsa" became
"ssh_rsa" and upper-case letters became lower-case letters and the whole string was cut off at some random point. Then the console became unresponsive and wouldn't let me type anything at all. I had to google and eventually typed Ctrl+c at the command prompt repeatedly and reloaded the console repeatedly until I could type again. The pico and nano editors don't work properly either. And there was no way I could add an SSH key because pasting doesn't work and I didn't want to type in my SSH key manually into the non-working nano editor. To sum up, it's a completely unusable POS.
I have experienced this too. I was fiddling around with VIM, editing my hosts.allow file. I wanted to make sure I didn't lock myself out via SSH, so I used the console, but the console no-likey VIM. The cursor disappeared and I couldn't :q! out of VIM! Ultimately I had to kill the session via command line ssh to fix it :(. Basically - VIM doesn't work in the web console is what I'm saying.
DO Support team. It is 2018 and DO console is still unresponsive, buggy, and slow as molasses. Workaround of using SSH is not the answer we are looking for. There are unique circumstance where console is needed. However console experience is not good at all. Please fix this issue in the new year.
I am using console to read a file using Nano. I am able to hit Control + X to exit, however I am unable to pass keyboard press of letter "n" or "y" to the console. What is responsive is hitting control + c to cancel, however no way to exit out of Nano in the console. I a now forced to kill console session via SSH.
I've also run into this issue. The console seems to work only sporadically, in little bursts, and often with no indication of whether it is working or not. It doesn't seem reliable enough to use as a backup if something goes wrong with a droplet...
DO seems to forget we are paying for their fucking services. Everyone has an issue with keymappings in the web console with no actual solution. Hey Digital Ocean, you aren't running an open source free solution. Telling your customers to deal with it is a fucking shitty answer.
Same problem here, and the solution did not worked for me. Console is crazy, and I can not type anything, all looks like ^[a, ^[O, etc.
Digital Ocean, do you have a solution?
You can exit a systemctl status message contain hidden lines by typing "q"
Assume that's what's happening here