The Droplet Console has a native-like terminal experience where you can run commands on your Droplet from command-line interface. Bobcares as a part of DigitalOcean Managed Service guides you with the Digitalocean droplet console not working article.

Droplet console not working overview

DigitalOcean Droplets have Linux-based virtual machines (VMs) that have to run on top of the virtualized hardware systems. Each Droplet that you create is a new server that you can use, this is either standalone or as part of a larger, cloud-based infrastructure.

The Droplet Console is very much a browser-based way to connect the Droplets. Alternatively, of using ssh in a local terminal you can use the Droplet Console in your preferred web browser.

Troubleshooting Digitalocean droplet console

Let’s look at a few troubleshooting steps on why the Digitalocean droplet console not working:

• Check the control panel. Make sure there are no occurring issues.

• Check if Droplet have disabled because of abuse. If your Droplet has been disabled, You will be receiving an that is linked to your DigitalOcean account with the title Networking Disabled:<your-droplet-name>.  Further, you can contact the support team for further information regarding suspected abuse,

• Recover root access. Reset your credentials if you do not have the current root password using the reset root password function in the control panel.

• Access the Recovery Console. If you cannot log in to the Droplet recovery Console is another way to gain access .

• Reboot your Droplet. If you’re experiencing connectivity issues try rebooting the Droplet as many connectivity problems can be resolved after a reboot. It is recommended to take backup before rebooting. To reboot you can run the following command: sudo reboot

• Review file management and permissions. Few solutions may require reviewing or editing

• Check logs. Check the system’s log files if you get any warning or error message

Droplet service running

If you are facing any connectivity issue with a service on your Droplet then it’s useful to verify which services initially are running on the Droplet. At times service might go down or be under heavy load which may cause down or intermittent connection problems.

On your Droplet, you can view the services that have bound to a port by running netstat command:

sudo netstat -plunt

The given -plunt flag returns a better readable output. Likewise netstat returns output similar as shown:

Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      13704/nginx -g daem
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      1762/sshd
tcp6       0      0 :::80                   :::*                    LISTEN      13704/nginx -g daem
tcp6       0      0 :::22                   :::*                    LISTEN      1762/sshd

Next check the port numbers and interfaces from the Local Address column against your expected services. If one of your expected services is not present in the netstat output then you can conclude that your service isn’t running. This would cause connection attempts to fail.