Can't Access Droplet via Putty or Terminal

For any other users having this problem remember to allow access to port 22 for ssh in your firewall settings.

ufw users $ sudo ufw allow 22

Hi @xMudrii @ryanpq,

I blurred it out because I didn’t know what was important or should be kept secret. I had my developer look and he’s having issues to. I logged a ticket.

But this is what we found so far:

Can’t login at all. Even at the console access from UI, it won’t budge. I created a live snapshot of the droplet, created a new droplet from that, same issue. I power cycled the original droplet, still can’t login through either ssh or the console access.

Couple of errors jumping out from the console access:

init: startpar-bridge (mountall–stopped) main process (161) terminataed with status 255

every time, the last message I can get from console access is:

random: nonblocking pool is initialized.

I can’t access it at all.

Another error in the console access (I can’t type anything, just gives me a few lines on display)

init: error while reading from descriptor: Bad file descriptor

Ryan, when I open the console, I get a pop up window with a black screen, but have no idea how to even type inside of it. I keep clicking in it…and nothing happens. Am I using this wrong?

http://imgur.com/a/uEHkS

If you are unable to access your droplet via SSH (using putty or another client)

• If you have a password set for the root user (or another user with sudo) you can log in via the console in the control panel (I am not sure if this is what you are referring to as the “terminal”.

• If you have not set a root password and do not have another user account with a password you will not be able to access the console.

If you are not able to access the console:

• If there are errors or other information being displayed in the console sharing that information here can help to track down the source of the problem.

• Using the option in the control panel, reboot your droplet and once it has rebooted try accessing the console or connecting to the ssh service again.

If you are still not able to access your droplet via ssh or the console:

• Open a ticket with our support team here or here and request that they reboot your droplet to a recovery ISO. From there you can investigate and make changes to your filesystem.

or

• Destroy or rebuild your droplet from a clean image (this will replace/delete all contents of your droplet so this option would only be feasible if you have either not completed your setup of the droplet or you have a snapshot or backup image available to restore from).