Table of Contents
Was this article helpful?
Try Vultr Today with

$50 Free on Us!

Want to contribute?

You could earn up to $600 by adding new articles.

How to Install Cockpit on CentOS 7

Last Updated: Mon, May 1, 2017
CentOS Linux Guides Server Apps System Admin

Cockpit is a free and open source program for Linux server management. It is very lightweight and has a beautiful, easy to use web interface. It allows system administrators to easily perform tasks such as starting Docker containers, storage administration, and network configuration.

In this tutorial you will learn how to install the latest version of Cockpit on CentOS 7.


  • A Vultr CentOS 7 server instance.

  • A sudo user.

Step 1: Update system packages

Before installing any packages on the CentOS server instance, it is recommended to update the system. Log in using the sudo user and run the following commands to update the system.

sudo yum -y install epel-release

sudo yum -y update

sudo shutdown -r now

Once the system has restarted, log in again as the sudo user and proceed to the next step.

Step 2: Install Cockpit

We can install the software from the default CentOS repository using the following command.

sudo yum -y install cockpit

Once you have installed Cockpit, start and enable it using the following commands.

systemctl start cockpit

systemctl enable cockpit.socket

Step 3: Configure firewall

Run the following commands to allow all of the required ports through the firewall.

sudo firewall-cmd --add-service=cockpit

sudo firewall-cmd --add-service=cockpit --permanent

firewall-cmd --reload

The installation of Cockpit is now complete, you can access the dashboard by navigating to the following URL.


You may be prompted with a security warning about the SSL certificate of the site as it is self-signed, but you can ignore the warning and proceed to login area. Log into Cockpit using the root credentials of your VPS.

Installing new SSL certs

In order to use SSL certificates you need to combine them into one file in the following location with the cert file ending in .cert. The public key should be first, then the private.


It should look something like this.

















Want to contribute?

You could earn up to $600 by adding new articles.