CloudBolt on Oracle Enterprise Linux (OEL) 7


How To: Convert an Oracle Enterprise Linux server into a CloudBolt Appliance.


You will need the following:

  • An Oracle Enterprise Linux 7 Server.

    • The server should be OEL 7.6.

      • Other OEL 7 versions may work.

      • CloudBolt does not support OEL 8.

    • The OEL VM should meet these system requirements:

      • 2+ CPUs

      • 8+ GB memory

      • 40+ GB storage (the initial VM will use ~2GB if thin provisioned, ~40GB if thick provisioned)

    • This should be a single-use VM. CloudBolt is not intended to run on a shared VM.

  • Download a copy of the CloudBolt 9.4+ Installer.


Installing CloudBolt

SSH into the CloudBolt server and escalate your privileges to be the root user.

In this example, the soon-to-be CloudBolt server has the IP

[user@your-workstation]$ ssh user@
[user@]$ sudo su

Next, unpack the CloudBolt Installer .tgz file and run the installation script.

[root@]# tar xzf cloudbolt_installer_VERSION.tgz
[root@]# cd cloudbolt_installer*/
[root@]# ./

This will unpack the installer and begin the installation process.

If the installation is successful you should see the following message at the end of the installer:

CloudBolt installer successfully finished!
verbose log saved to: /var/log/cloudbolt/install/install_200601.1620.log

Accessing CloudBolt via Firewall Rules

By default, the VM may prohibit inbound HTTP(s) traffic.
To enable HTTP(s) traffic, run the commands described in order below:

Disabling iptables service:

[root@]# systemctl mask iptables

Enabling Firewalld service:

[root@]# systemctl enable firewalld
[root@]# systemctl start firewalld

Enabling HTTP traffic:

[root@]# firewall-cmd --zone=public --permanent --add-service=http

Enabling HTTPS traffic:

[root@]# firewall-cmd --zone=public --permanent --add-service=https

Enabling SSH traffic:

[root@]# firewall-cmd --zone=public --permanent --add-service=ssh

You may need to run something like this to allow for all incomming traffic:

[root@]# firewall-cmd --zone=public --change-interface=ens192

You may also want to update the hostname of the VM to cloudbolt:

hostnamectl set-hostname "cloudbolt"


If the installation fails, please reach out to a support engineer to resolve the issue.

Have more questions? Submit a request


Please sign in to leave a comment.