iDatam

IN AFRICA

ALBANIA

ARGENTINA

AUSTRALIA

AUSTRIA

AZERBAIJAN

B AND H

BANGLADESH

BELGIUM

BRAZIL

BULGARIA

CANADA

CHILE

CHINA

COLOMBIA

COSTA RICA

CROATIA

CYPRUS

CZECH

DENMARK

ECUADOR

EGYPT

EL SALVADOR

ESTONIA

FINLAND

FOR BACKUP AND STORAGE

FOR DATABASE

FOR EMAIL

FOR MEDIA STREAMING

FRANCE

GEORGIA

GERMANY

GREECE

GUATEMALA

HUNGARY

ICELAND

IN ASIA

IN AUSTRALIA

IN EUROPE

IN NORTH AMERICA

IN SOUTH AMERICA

INDIA

INDONESIA

IRELAND

ISRAEL

ITALY

JAPAN

KAZAKHSTAN

KENYA

KOSOVO

LATVIA

LIBYA

LITHUANIA

LUXEMBOURG

MALAYSIA

MALTA

MEXICO

MOLDOVA

MONTENEGRO

MOROCCO

NETHERLANDS

NEW ZEALAND

NIGERIA

NORWAY

PAKISTAN

PANAMA

PARAGUAY

PERU

PHILIPPINES

POLAND

PORTUGAL

QATAR

ROMANIA

RUSSIA

SAUDI ARABIA

SERBIA

SINGAPORE

SLOVAKIA

SLOVENIA

SOUTH AFRICA

SOUTH KOREA

SPAIN

SWEDEN

SWITZERLAND

TAIWAN

THAILAND

TUNISIA

TURKEY

UK

UKRAINE

UNITED ARAB EMIRATES

URUGUAY

USA

UZBEKISTAN

VIETNAM

Building Your Own Private Cloud: Installing and Securing Proxmox VE on Bare Metal

Turn a massive bare-metal server into a secure, self-hosted private cloud with Proxmox VE.

Illustration of a bare metal server transforming into a private cloud infrastructure

The public cloud offers incredible flexibility—allowing you to spin up Virtual Private Servers (VPS) in seconds for your development team. However, that flexibility comes with exorbitant per-hour pricing, egress fees, and hypervisor latency.

What if you could own the hardware but keep the cloud-like flexibility?

By deploying Proxmox Virtual Environment (VE) on a massive bare-metal server (such as an AMD EPYC machine with 128 cores), you capture the ultimate infrastructure cheat code: the instant provisioning and flexibility of the public cloud, but with the raw power and fixed monthly cost of dedicated hardware. In this tutorial, we will show you how to take a fresh Unmetered Dedicated Server from iDatam and transform it into your own secure, private VPS network using Proxmox VE.

What You'll Learn

Step 1: Prepare the Hostname on a Clean Debian OS

While you can install Proxmox directly from an ISO, most remote dedicated server deployments begin with a clean installation of Debian 12 (Bookworm).

First, connect to your server via SSH. You need to ensure your server's hostname is properly resolvable. Check your current hostname:

bash

hostname
                                

Edit your /etc/hosts file to assign your server's static public IP to its hostname.

bash

nano /etc/hosts
                                

Make sure the file looks like this (replace 198.51.100.10 with your server's actual IP, and proxmox with your chosen hostname):

plaintext

127.0.0.1       localhost
198.51.100.10   proxmox.yourdomain.com proxmox
                                

Save and exit, then test the resolution. (It should return your public IP, not 127.0.0.1).

bash

hostname --ip-address
                                

Step 2: Add the Proxmox Repositories

Next, add the Proxmox VE repository to your Debian package manager so it can fetch the hypervisor files. We will use the "No-Subscription" repository for this setup.

bash

echo "deb [arch=amd64] http://download.proxmox.com/debian/pve bookworm pve-no-subscription" > /etc/apt/sources.list.d/pve-install-repo.list
                                

Add the official Proxmox repository GPG key to ensure the packages are authentic:

bash

wget https://enterprise.proxmox.com/debian/proxmox-release-bookworm.gpg -O /etc/apt/trusted.gpg.d/proxmox-release-bookworm.gpg
                                

Now, update your system and perform a full upgrade to ensure all base packages are current:

bash

apt update && apt full-upgrade -y
                                

Step 3: Install Proxmox VE

You are now ready to install the Proxmox hypervisor, its custom kernel, and necessary networking tools.

bash

apt install proxmox-ve postfix open-iscsi chrony -y
                                

Note: During the installation, you may be prompted to configure postfix (the mail server). If you don't need email alerts right now, just select "Local only."

Once the installation completes, reboot the server to boot into the new Proxmox kernel:

bash

reboot
                                

Step 4: Access the Proxmox Web Interface

Once the server comes back online, the Proxmox Web GUI will be active. Open your web browser and navigate to: https://your_server_ip:8006

(You will likely get a "Connection is not private" warning because Proxmox generates a self-signed SSL certificate by default. Click "Advanced" and proceed to the site).

  • Username: root
  • Password: (Your server's standard root password)
  • Realm: Linux PAM standard authentication

Step 5: Configure the Virtual Network Bridge

To allow your new Virtual Machines to access the internet, you must create a "Linux Bridge."

  1. Inside the Proxmox Web GUI, click on your node name (e.g., proxmox) in the left-hand menu.

  2. Navigate to System > Network.

  3. Click Create > Linux Bridge.

  4. Name it vmbr0.

  5. Enter your server's primary network interface name (e.g., eno1 or eth0) into the Bridge Ports field.

  6. Click Create, and then click Apply Configuration at the top of the network screen.

Now, whenever you create a new VM for your development team, assign its network device to vmbr0, and it will behave exactly like an independent cloud VPS.

Step 6: Secure the Proxmox Interface

Proxmox exposes its admin panel on port 8006 to the public internet by default. This is a massive security risk. You should restrict access so only your office IP address or VPN can load the login page.

Log back into your server via SSH and use UFW (Uncomplicated Firewall) to lock it down:

bash

apt install ufw -y
ufw default deny incoming
ufw default allow outgoing

# Allow standard SSH access
ufw allow 22/tcp 

# Allow port 8006 ONLY from your specific office IP (replace with your IP)
ufw allow from 203.0.113.50 to any port 8006 proto tcp

ufw enable
                                

Conclusion: Scale Your Private Cloud

You have successfully replaced the expensive public cloud with your own high-performance private cloud. You can now use the Proxmox interface to slice your massive bare-metal server into dozens of isolated Linux or Windows virtual machines for your team.

As your team's storage and bandwidth requirements grow, you can seamlessly link multiple iDatam servers together to create a high-availability Proxmox cluster. For massive private cloud deployments that require seamless VM live-migration across nodes, explore our 100Gbps Dedicated Servers to provide the ultimate unmetered backbone for your infrastructure.

Discover iDatam Dedicated Server Locations

iDatam servers are available around the world, providing diverse options for hosting websites. Each region offers unique advantages, making it easier to choose a location that best suits your specific hosting needs.

Up