Learn Proxmox VE - Web UI Navigation, Node Management & System Configuration

#Introduction

The Proxmox web UI is not just a display panel — it's the command center for your entire infrastructure. After the installation in episode 0, it's time to master its navigation structure, get to know the parts you'll use most often, and finish the node's basic configuration so the system runs optimally.

Episode 2 takes you through three areas: understanding the web UI structure, understanding the Summary, Console, and Task Log, and then basic system configuration covering DNS, timezone, NTP, system updates, and repositories. Master this episode, because all subsequent episodes will interact with the same elements.

#Understanding the Web UI Navigation Structure

#Datacenter View, Node View, and VM View

When you log in, you'll see a left panel with a three-level hierarchy. Datacenter View shows settings that apply to the whole cluster: datacenter firewall, storage, backup jobs, and HA. Node View represents a single physical server — where you manage local storage, networking, and node services. Below the node, you'll find VMs and Containers, each with its own configuration page.

Datacenter
 └── node pve
      ├── VM 100
      ├── VM 101
      └── CT 102

This file-tree-like view is the key to understanding where a setting lives: whether it belongs to the cluster, the node, or the VM.

#The Main Elements of Every Page

Every entity in the web UI has its own left menu: Summary, Console, Hardware, Options, Network, Disks, and Tasks. These menus are contextual — a node has Disks and Network, while a VM has Hardware and Cloud-init. Getting used to this menu pattern keeps you from getting lost while exploring.

#Summary, Console & Task Log

#Summary

The Summary page shows an at-a-glance overview: node CPU and RAM usage, storage in use, and running VMs. For a VM, the Summary shows the OS, IP address, and allocated resources. This is the first page you should look at when checking system health.

#Console: noVNC, xterm.js, and SPICE

The Console lets you access the VM screen or container terminal directly from the browser. Proxmox offers several options: noVNC (web-based VNC, the default and easiest), xterm.js (a serial terminal), and SPICE, which provides a richer desktop experience with better performance for remote access.

Click VM  ->  Console menu  ->  choose noVNC / xterm.js / SPICE

The Console is the primary way to interact with the OS inside a VM before networking is configured.

#Task Log

Every Proxmox operation — creating a VM, backup, migration, snapshot — runs as a task. Click the hourglass icon in the top-right corner of the web UI to see the list of running and completed tasks. The Task Log shows the full output, and it's the first place to check when an operation fails.

#Basic Node System Configuration

#Configuring DNS, Timezone, and NTP

A Proxmox node must have accurate time, because many components depend on it — backup scheduling, logs, and replication are all time-sensitive. In Datacenter -> Options, you can set the timezone for the whole cluster. For NTP and DNS, Proxmox uses systemd-timesyncd and the Debian configuration.

timedatectl status

The output shows the timezone and the NTP synchronized: yes status. If it's not synchronized yet, enable it with timedatectl set-ntp true.

#System Updates Through the CLI

Although the web UI provides an update page, the most reliable way is through the CLI. Run it on the Proxmox node:

apt update && apt full-upgrade -y

This command fetches the latest package lists, then upgrades the system thoroughly. Do this regularly — Proxmox releases security patches and fixes that are important for stability.

#Managing Repositories via the UI

Besides editing files as in episode 0, you can manage repositories from the web UI at Datacenter -> Repositories. This page shows all active repositories, lets you add or disable them, and can copy them to all cluster nodes. It's the most ergonomic way to keep repository configuration consistent.

cat /etc/apt/sources.list

What you see in the UI and the file at /etc/apt/sources.list should always be in sync. The apt update command will give a clear picture if any repository is wrong.

#Making Sure the System Is Ready

After the basic configuration is done, do a quick check that the node is functioning normally:

pveversion
uptime
df -h

pveversion confirms the Proxmox version, uptime confirms the node is stable, and df -h confirms the storage has enough space. If all three are healthy, your node is ready for the next phase: creating your first virtual machine.

#Closing

Episode 2 made you comfortable with the web UI: the three-level navigation structure, the Summary, Console, and Task Log features, as well as the basic configuration covering DNS, timezone, NTP, system updates, and repositories from the browser.

The key takeaways:

• The Proxmox web UI consists of the Datacenter, Node, and VM/Container hierarchy.
• The Console provides noVNC, xterm.js, and SPICE for screen access.
• The Task Log is the first place to check the results and failures of operations.
• Node time must be synchronized: check with timedatectl status.
• Update regularly with apt update && apt full-upgrade -y.
• Repositories can be managed from Datacenter -> Repositories as well as the configuration file.

In the next episode, episode 3, we will cover creating and managing KVM virtual machines — from the KVM hypervisor concept, uploading ISOs, configuring CPU type, RAM ballooning, machine type, VirtIO virtual disks, to the lifecycle operations of start, stop, shutdown, pause, and suspend. Your node is ready — now it's time to power on your first virtual machine!