Console fails to connect

Hey all,

Usually, when you have such an issue, an issue with connecting to your Droplet, you should always try the Recovery Console:

https://docs.digitalocean.com/products/droplets/how-to/recovery/recovery-console/

The Recovery Console provides out-of-band access and is available regardless of your network settings. It emulates the access you would have if you were sitting down with a keyboard and monitor attached to the actual server. You can use this feature to log in and revert bad settings to regain normal access.

@alexdo,

I was able to figure out a bit more with this issue. I didn’t realize that Digital Ocean now has a new kind of Droplet Console. I have not needed to use the console for a couple years. I was expecting the Droplet Console to function the way it used to. I now see that the Recovery Console is what the Droplet Console used to be and that is what I was originally looking for. I feel much better knowing that I can get into my Droplet using the Recovery Console if needed.

Based on the new type of Droplet Console, it was not connecting because I do not allow ssh to the Droplet. I opened up ssh in the firewall and now I’m getting this error. “All configured authentication methods failed”.

Since I cannot find any solutions to this error, I have opened a ticket with support.

Thank you again for your assistance.

The Droplet Console is meant as a lightweight, browser-based way to manage a Droplet. It connects to Droplets using the network, like other SSH-based clients, and has features similar to local terminals.

The Recovery Console (previously referred to as the Droplet Console) is an older, browser-based connection option based on VNC. Using it is like plugging a keyboard and monitor directly into the Droplet.