---
title: How to use the serial console
description: This page explains how to use the serial console on a Scaleway Dedibox server
tags: dedibox serial console serial-console
dates:
  validation: 2025-09-03
  posted: 2021-06-11
---
import Requirements from '@macros/iam/requirements.mdx'

import image from './assets/scaleway-serial-console.webp'
import image2 from './assets/scaleway-serial-console-2.webp'
import image3 from './assets/scaleway-serial-console-esxi.webp'
import image4 from './assets/scaleway-serial-console-esxi2.webp'
import image5 from './assets/scaleway-serial-console-esxi2.webp'


Some Dedibox server models do not have KVM over IP, but allow the visualization of a video output on a serial console. This allows you to interact with the server even if you have locked yourself out, for example by a malicious network configuration.

<Requirements />

- A Dedibox account logged into the [console](https://console.online.net)
- [Created](/dedibox/how-to/order-a-server/) and [installed](/dedibox/how-to/install-a-server/) a dedicated server

## How to access the serial console

1. From the console, click **Server** > **Server list** on the top menu. A list of your servers displays.
2. Click **Manage** next to the relevant server.
3. Click **Serial Console**. The connection information displays.
    <Lightbox image={image} />
4. Click **Access** to access the serial console of your server.
    <Lightbox image={image2} />

## How to configure the serial console

On certain installations, the serial console may not be activated by default. These steps show you how to activate it from the command line of your server.

### On SystemD-based operating systems (Ubuntu 18.04 and later / Debian 8 and later / CentOS)

To activate it on each reboot:

```
systemctl enable getty@ttyS1.service
```

To activate it on an already booted server:

```
systemctl start getty@ttyS1.service
```

### On Ubuntu 14.04

Create the folder `/etc/init/ttyS1.conf`:

```
# ttyS1 - getty
#
# This service maintains a getty on ttyS1 from the point the system is
# started until it is shut down again.

start on stopped rc RUNLEVEL=[12345]
stop on runlevel [!12345]

respawn
exec /sbin/getty -L 9600 ttyS1 vt102
```

After a reboot of the server, the serial console will be activated.


### On Debian 7 (Wheezy)

1. Edit the file `/etc/inittab`.
2. Uncomment the following line:
    ```
    T1:23:respawn:/sbin/getty -L ttyS1 9600 vt100
    ```

    To put the changes into effect type:

    ```
    init q
    ```

### GRUB

In certain cases, GRUB may not be configured to show the serial console.

1. Edit `/etc/default/grub`, to add/change the following lines:
    ```
    GRUB_TERMINAL=serial
    GRUB_SERIAL_COMMAND="serial --unit=1 --speed=9600 --word=8 --parity=no --stop=1"
    ```
2. Save the changes.
3. Update your GRUB:
    ```
    update-grub or update-grub2.
    ```

### On ESXi

Directly from the vSphere client:

<Lightbox image={image3} />

1. Enter the Configuration tab (1). In the **Software** section, click on **Advanced Settings** (2).

    A new window will open.
2. Go to VMKernel and open it by clicking on the small + icon on the left.
3. Click on Boot (1).
4. On the right side of the window, look for the VMKernel.Boot.com2_baud option
5. Enter 9600 (2) as value:
    <Lightbox image={image4} />
6. Look for the VMKernel.Boot.tty2Port value5. Enter 9600 (2) as value:
    <Lightbox image={image5} />
6. Look for the VMKernel.Boot.tty2Port value.
8. Reboot the ESXi host. You can now use the serial console of your server.

### On FreeBSD

1. Edit the `/boot/loader.conf` file:
    ```
    boot_multicons="YES"
    boot_serial="YES"
    comconsole_speed="9600"
    console="comconsole"
    comconsole_port="0x2F8"
    ```

  This will activate the console during the boot process of your server.
2. Edit the `/etc/ttys` file to add the following information at the ttyu1 line:
    ```
    ttyu1   "/usr/libexec/getty std.9600"   vt100   on  secure
    ```
3. Reboot your server to access the serial console.