Question

Stuck: can't type anything in console acces

Posted May 26, 2014 81.9k views
I was setting up PHP over Nginx when all of the sudden my console access stoped working. It displays what it should but cat't type any character. Tried refresh, changed the computer but the problem persists.
2 comments
  • I’m going through a similar problem right now… the console logged me out automatically and now its asking me to login but when I type the letter popup as ^E^L etc and when I try back spacing I get ^H^H^H^H^H^H^H^H every letter I type seems to pop us as a capital with ^ in front of it like im typing by holding control before each letter. Does anyone know how to solve this? Thank you in advance!

  • I was having the same problem. What I did was reset the Droplet and then the error disappeared.

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.

×
19 answers

I have the solution! To those who are stuck click on the window and press one of these combinations.

CTRL+X
CTRL+C
CTRL+(anything)

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.

Tried CTRL + C ended up CMD + CTRL + C worked for me.

Why are you using the console?
I'm new to DigitalOcean. What are you using?
You should use SSH, console is for emergency access.
The web console is really only provided as a fail safe. You can use it to access your droplet when you don't have any other way. For day to day work on your server, you'll be much better off connecting with SSH like Wouter mentioned. If you're on Windows, take a look at PuTTY:

https://www.digitalocean.com/community/articles/how-to-log-into-a-vps-with-putty-windows-users
by Saleh Salem
This tutorial will allow you to log Into a VPS with Putty (Windows Users).
  • I’m in the same situation and your answer doesn’t help, at least in my case. I do have ssh keys uploaded, but during the morning I work in a place where ssh protocol is blocked for outside communications and firewall also blocks ssh over http/https (even using corkscrew), so good console access is mandatory.

    Anyway, even for the case you mentioned, emergency/fail safe use is not really “fail safe” if you can’t type anything in console.

  • Hmmm. What is really happening to me is something weird: when I open the console during the first seconds I can type whatever I want, but after this time is elapsed no regular key is working, just a few special keys are working (PgUp, PgDown, cursor keys, function keys and that’s it)

    • Yes, it’s 2017 and console slows down after to non-responsive, where console prompts me to either kill or wait. I click on wait, half the time the console session times-out.
      SSH with key from PuTTY has been working great, but right now key authentication isn’t working. So really need this, because when editing sshdconfig and slow console session which eventually times out creates a locked sshdconfig file. then trying to fix the lock with incredibly slow console takes hours. HOURS!

  • I think his comment isn’t helpful as well. The real question remains, how do you fix the web console issue?

  • @kjszives What is the problem you are actually experiencing? If the console isn’t working at all, then open a support ticket so the team can investigate the problem. If you are having issues with certain keys not working, you should reconfigure the keyboard layout setting on your server. A proper SSH session will handle the input from keystrokes for you, but sing the console is more like plugging a keyboard directly into the server.

    • asb,

      The reason why your comment is not helpful is because you still did not answer the question. I am searching the forums to resolve this issue because I locked myself out by blocking root access (stupidly). Now the only way to fix this is to access the online virtual console, and access to it is blocked.

      Now, if you have any solution to the actual issue at hand, which is that we cannot type anything into the console access, you will solve the problem for many users in the future like me.

    • I plugged keyboards directly into routers and servers for years, but never had the slowness and serious problems getting commands to run in a console before. This situation is unique to Digital Ocean’s console access. Console slowness is not taken seriously by DO’s support team. They always say to use SSH, otherwise put up with the slowness. This is not a good response, the slowness is a serious threat to the server due to session timeouts with a config file open.

  • Thank you for your suggestion. It’s work for me :)

  • a fail safe which is not safe as long as it doesn’t work actually

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.

  • I am facing the same problem. I cannot :q out of the vim. Also, there is no SSH connection in my case. Please tell me how to exit the VIM. I tried Ctrl+c/x too.

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…

almost 4 years and we still wait for a solution

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.

  • If the console is equivalent to a USB keyboard, then how about telling us what the layout for your virtual usb keyboard is so we can set it right in our settings?

    • A little testing with the console program showkey. I am having issues with the pipe symbol. The pipe symbol resides on keycode 43 “|". without shift it shows as the proper keycode. But when I press shift the keycode changes to 86 which is ”>“. Shift should not change keycodes! This is an issue with your software

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

It’s the main reason why i left DO. 5 years and still not working console. Always typing “^[a” etc.

woohh....+5 years …my web console is buggy....just a black screen in the background, bottom right I read ‘If you see a black screen just click on it and press any key to activate the console window’ did not work, I need to perform a small sw upgrade over the console to prevent connection issues in SSH

If you are using DigitalOcean, login and in the list of your Droplets you will see at the far right an option that says MORE, click on it and select Access Console, from there you will be able to use the same command screen that you use in Putty.

You guys should provide a place to temporarily upload a keyfile within DO web platform with a short bitly style url/id, and provide the instructions on how to curl that keyfile into your authorized keys file on a droplet. I’ve been running into an xkcd success#349 moment trying to get my pub key copied into the droplet. From… using ctrl shift v and having the console log me out and get stuck with the caps-state mismatch, to the modifier keys getting stuck, to using outdated JS from a gist to try to paste in a key, to google drive giving me a super long public link to copy in–it all leaves a very bad taste in my mouth. We all want to avoid the web console since you guys intend it for absolute-must situations, but you should REALLY provide a more robust way to get a key into a machine.

I just had the same issue. On a new droplet.
Keyboard accepted only spaces and numbers (and Ctrl+letter), and I could paste, and it pasted everything reverted. And reboot did not help.

I had to “paste” ROOT for it to input “root” and then I had to revert the password as well. And then pasting an rsa-key to add it to authkeys was a challenge.
I pressed Ctrl+Anything 1000 times and at some point with “Q” it got fixed and later broke again and so on.

Since 2014, DO, really??

Submit an Answer