Introduction
I was recently given an HP ProLiant DL380 G6 server, a generous gift from a friend who had already set up Proxmox for his homelab. Today, I finally found the time to dive into the world of server administration and set up this impressive machine in my home lab.
The Initial Hurdles
I brought the server home, eagerly plugged it in, and fired it up. My goal was to configure it with a static IP on my network for easy management. With excitement, I accessed the terminal and began to tinker. I needed to modify the network settings by editing the /etc/network/interfaces
file. However, I overlooked a crucial step: creating a backup of the file. As you might guess, this oversight came back to haunt me.
SSL Error and ILO Challenges
After making the changes to the network settings, I rebooted the server. Upon startup, I was greeted by the Proxmox message, instructing me to access it via a web browser at https://xxx.xx.x.x:8006
. The x’s in the address represented the static IP I had assigned earlier. Excited to continue, I opened my laptop and attempted to access this address, only to be met with an intimidating “ERR_SSL_VERSION_OR_CIPHER_MISMATCH” error.
I decided to explore the Integrated Lights-Out (ILO) interface for an alternative solution, but my efforts were met with the same error. This error was due to unsupported protocols, specifically related to the outdated ILO3 and Internet Explorer, which was also no longer in favor.
The Fresh Install Approach
Recognizing that I needed a fresh start, I opted for a complete Proxmox reinstallation. I started by downloading the latest Proxmox ISO from the Proxmox website.
Choosing the Right Tool
To create a bootable USB drive, I first tried using Etcher, a versatile tool for flashing OS images onto USB drives. Etcher is known for its simplicity and cross-platform compatibility. However, in my case, it didn’t work as expected. I then gave Ventoy a shot, which successfully wrote the ISO to the USB drive.
Nevertheless, when I attempted to boot from the USB on the server, it failed, presumably due to formatting or BIOS compatibility issues.
In my determination to overcome these obstacles, I accidentally rendered my USB drive unrecognizable
by my computer. To resolve this, I turned to Bootice, a software program that can install, back up, and restore Master Boot Records (MBR). You can find it here. Bootice helped me restore the USB drive.
Once my flash drive was back in working order, I successfully wrote the Proxmox ISO to it using Rufus. With the bootable USB drive ready, I inserted it into the server, turned the server on, and waited for the POST phase. During this stage, I pressed F11 to acces
s the boot options. A menu appeared, offering various choices, including “3. Boot from USB key.”
Resolution Woes and “nomodeset”
I initially attempted to install Proxmox with the graphical option, but my monitor displayed an “Out of range signal” error, suggesting I change my computer’s display input. To troubleshoot, I powered down the server and tried the console installation, only to encounter the same error.
In a last-ditch effort, I experimented with a different monitor, but this change didn’t resolve the problem. Frustrated but determined, I turned to Google for assistance. A Reddit post came to my rescue, as it described a similar issue.
A Glimmer of Hope: Advanced Options and “nomodeset”
The Reddit community recommended accessing “Advanced Options” instead of choosing graphical or console installation. Once inside, they advised selecting “nomodeset.” I followed this advice, and it worked like a charm. The installation proceeded with the appropriate resolution and guided me to the End-User License Agreement (EULA).
With a sense of relief, I agreed to the terms, set my country and timezone, and established the root password.
Network Configuration and EULA
The next crucial step was configuring the network settings. Proxmox thrives on static IPs, making this an important part of the process. To set a static IP, I logged into my network’s gateway, located the server, and established the static IP, subnet mask, and gateway IP.
The Finish Line
With network settings in place, my setup was nearly complete. The screen displayed a welcoming message: “Welcome to the Proxmox Virtual
Environment. Please use your web browser to configure this server—connect to:
https://xxx.xxx.xx.x:8006
” (with the x’s representing the static IP I’d set earlier).
Eager to witness the results of my hard work, I opened a web browser on my network, entered the IP and port number provided by Proxmox, and was greeted with the graphical user interface of my Proxmox server.
Now, with my Proxmox server up and running, I’m all set to dive into the world of virtualization and start my homelab projects. Stay tuned for updates as I share my experiences and insights to help others set up their own homelabs.
Pingback: How to Create an OpenVPN Server in Proxmox - The Bluff City Geek