# How to Connect to Droplets with the Droplet Console

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

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

The Droplet Console has a native-like terminal experience, so you can run commands on your Droplet from a familiar command-line interface. It also provides one-click SSH access to your Droplet without the need for a password or manual SSH key configuration.

## Requirements

The Droplet Console is available at no extra cost for Droplets that meet the following requirements:

- **The Droplet must be running a supported operating system.**

  The Droplet Console is supported for all DigitalOcean-provided Linux distributions: Ubuntu, Debian, CentOS, and Fedora. This also includes all Marketplace images built on top of these distributions.
- **Your [cloud firewall](https://docs.digitalocean.com/products/networking/firewalls/index.html.md) and any [host firewalls](https://docs.digitalocean.com/support/my-firewalls-are-not-working-correctly/index.html.md) must accept SSH traffic on the port that `sshd` uses.**

  If you have configured any of your firewalls to block SSH traffic on the port the SSH daemon listens on, you need to reconfigure their rules to accept incoming SSH connections on that port.

**Note**:

  If you need to recover network access to your Droplet, [use the Recovery Console](https://docs.digitalocean.com/products/droplets/how-to/recovery/recovery-console/index.html.md) instead.

  ## Learn more about the difference between the Droplet Console and the Recovery Console.

  [The Droplet Console](https://docs.digitalocean.com/products/droplets/how-to/connect-with-console/index.html.md) 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](https://docs.digitalocean.com/products/droplets/how-to/recovery/recovery-console/index.html.md) (previously referred to as the Droplet Console) is an older, browser-based connection option based on [VNC](https://en.wikipedia.org/wiki/Virtual_Network_Computing). Using it is like plugging a keyboard and monitor directly into the Droplet.

  The Recovery Console is available even if a Droplet has lost network access or the `sshd` process has failed, but its functionality is limited compared to the Droplet Console. For example, it requires password authentication on the Droplet and doesn’t fully support features like copying and pasting.

  Use the Recovery Console only to recover from network issues when you can’t connect to your Droplet and to boot into the [recovery ISO](https://docs.digitalocean.com/products/droplets/how-to/recovery/recovery-iso/index.html.md). The Droplet Console is otherwise a better option for general command-line management of your Droplets.

## Install and Configure the Droplet Agent

To connect to a Droplet using the Droplet Console, the Droplet must have the Droplet agent installed. The agent is installed by default on all new Droplets created after August 2021, and you can [install the agent manually on older Droplets](https://docs.digitalocean.com/products/droplets/how-to/manage-agent/index.html.md#install).

By default, the Droplet Console connects on the first port defined in the Droplet’s SSH daemon configuration, `/etc/ssh/sshd_config`. If you launch `sshd` with a different configuration file, or if you define multiple ports in that file and want to use one other than the first, you need to update the service file for the Droplet agent.

The Droplet agent service file is `/etc/systemd/system/droplet-agent.service` on Droplets with systemd and `/etc/init/droplet-agent.conf` on older Droplets with `initctl`.

To define a custom `sshd` configuration file, find the `ExecStart` line in the service file and append the `-sshd_config` flag with the path to your `sshd` configuration file:

```
ExecStart=/opt/digitalocean/bin/droplet-agent -syslog -sshd_config="/path/to/your/custom/sshd_config"
```

To define a specific port, find the `ExecStart` line in the service file and append the `-sshd_port` flag with the port number you want to use.

```
ExecStart=/opt/digitalocean/bin/droplet-agent -syslog -sshd_port=123
```

After making changes to the service file, restart the service. On Droplets with `systemd`:

```shell
systemctl daemon-reload
systemctl restart droplet-agent
```

On Droplets with `initctl`:

```shell
initctl stop droplet-agent
initctl reload-configuration
initctl start droplet-agent
```

Once the agent restarts, you can connect to your Droplet with the Droplet Console.

## Access the Droplet Console

Once the Droplet agent is installed (and configured if necessary), you can access the Droplet Console from the DigitalOcean Control Panel.

First, click the name of the Droplet you want to access to expand its detail window, then click the name again to go to its detail page. From the detail page, click the **Access** tab in the left menu.

![](https://docs.digitalocean.com/screenshots/droplets/pages/access-consoles-only.de4e5d87beee4a01212407163d1c667a30d5bc7911020a3265230be942347437.png)

In the **Droplet Console** section, enter the user you want to log in as in the **Log in as…** field. By default, this is set to `root`. Once you choose a user, click **Launch Droplet Console** to open the Droplet console.

When the console loads, you can use the command line to run commands on your Droplet.