Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

To change a standalone Proxmox VE host’s management IP, update the address and prefix on its management bridge or interface, update the node’s hostname mapping in /etc/hosts, and apply the configuration using the method supported by your installation. Have local or out-of-band console access ready: applying a network change can disconnect the web interface. If the address also carries Corosync or Ceph traffic, plan those network changes separately before editing the host.

First identify what the IP address serves

The IP shown for a Proxmox VE node in the web interface is its host management address. It is not automatically the address used by virtual machines, storage, or every cluster service. Before changing anything, identify the bridge or interface that owns the management address and determine whether other traffic depends on it.

  • Confirm whether the node is standalone or part of a cluster.
  • Check whether Corosync cluster communication or Ceph/storage traffic uses the address or network being changed.
  • Record the current address, prefix or netmask, gateway, bridge, and physical port. Confirm the correct target values and that the new address is available.
  • Arrange console access that will remain available if the current management connection drops.

The ServeTheHome guide by Eric Smith, published August 11, 2021, demonstrates a basic management-interface change and updates /etc/hosts. Its example values are specific to that example; in particular, its gateway remains unchanged and should not be assumed correct for your destination network. See ServeTheHome’s Proxmox VE IP address guide.

Change the management address on a standalone node

Proxmox VE allows network configuration through the web interface or by editing /etc/network/interfaces. The official network guidance describes both routes and the GUI’s staged apply flow. Since interface names and network layouts vary, change only the bridge or interface you identified as carrying management traffic. The official documentation catalogue lists the Proxmox VE Administration Guide 9.2, last updated August 10, 2026; use documentation matching the installed release because UI labels and details can change.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Option 1: Use the web interface

  1. Open the node’s System > Network page and identify the management bridge or interface.
  2. Edit its address and prefix/netmask to the values for the destination network. Change the gateway only if the destination network requires a different route.
  3. Update the node’s hostname mapping on System > Hosts so the hostname resolves to the intended address.
  4. Review the pending configuration carefully, then use Apply Configuration. The management session may disconnect while the new configuration takes effect.

Option 2: Edit the host configuration

  1. Back up the relevant configuration file before editing. The network settings are commonly in /etc/network/interfaces.
  2. Change the address and prefix/netmask on the management bridge or interface. Set the gateway only if the target network’s routing requires it; do not copy an example gateway without checking your network.
  3. Edit /etc/hosts so the node’s hostname maps to its intended address.
  4. Apply the change with ifreload -a when the installation supports ifupdown2. Proxmox recommends ifupdown2 and includes it by default on new installations since Proxmox VE 7.0, but an installation’s actual package and configuration may differ. A planned reboot is another way to apply staged network changes if live reload is not appropriate.

Proxmox’s Network Configuration documentation explains the GUI and file-based approaches and warns that incorrect network configuration can make a node inaccessible. It also describes applying GUI changes with the Apply Configuration button. Use the matching release documentation to confirm exact labels and behavior.

Check name resolution and connectivity after applying

Once the change is applied, reconnect to the node at its new address. Confirm that the hostname resolves as intended and that the node’s management network has the expected address, prefix, and route. If your DNS servers or resolver settings were specific to the old network, update them as needed; DNS changes are conditional, not a required step for every host.

Rank #2
HP High-End Virtualization Server 36-Core 256GB RAM 16TB DL360 G9 (Renewed)
  • HP Proliant DL360 G9 4-Bay LFF Server | 2x E5-2695v4 2.10GHz 18-Core CPU (36-Cores Total)
  • 256GB DDR4 RAM | 4x 4TB 7.2K SATA 3.5" HDD
  • Smart Array P440ar w/ 2GB FBWC | 4x1Gbe NIC
  • 2x 500W PSU | Windows Server 2019 Standard Evaluation
  • Verify access to the Proxmox web interface at the new address.
  • Check the host’s local hostname resolution against the updated /etc/hosts entry and your DNS setup.
  • Confirm that dependent management services and any relevant cluster or storage services remain healthy.

If the address is also used by a Proxmox cluster

A management-IP edit is not a complete cluster-network migration when Corosync uses the network being changed. Proxmox’s Cluster Manager documentation says to update the relevant Corosync link addresses on all affected nodes, keep node names correct, increment config_version, and verify the resulting configuration. The legacy field name for link addresses is ring0_addr.

Coordinate the change across the cluster rather than editing one node in isolation. Proxmox warns that nodes restart Corosync one after another during a communication-network change, which can cause brief quorum loss. Cluster state changes require a majority of votes; as the documentation puts it, “The cluster switches to read-only mode if it loses quorum.” Check Corosync afterward with systemctl status corosync. A restart is not strictly required for every valid live configuration change, but may occur if other settings change or Corosync reports problems.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Proxmox’s Cluster Manager documentation on cluster networking says stable cluster networking requires latency under 5 milliseconds. That is a stated cluster-network requirement, not a result measured for an individual deployment.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Keep VM and Ceph address changes separate

Changing the host management address does not by itself change virtual-machine addresses or migrate a Ceph/storage network. Treat those as separate network changes with their own dependencies and recovery plans. Proxmox’s basic host-address guidance does not provide a complete Ceph address-migration procedure, so do not assume the management-IP steps cover a Ceph deployment.

Best Value
GMKtec Mini PC Ryzen 5 3500U 16GB RAM 512 SSD Office Home Business Computer
  • POWERFUL OFFICE & LIGHT GAMING MINI PC --- The GMKtec NucBox G10 features the AMD Ryzen 5 3500U (4C/8T, up to 3.7GHz) with Radeon Vega 8 Graphics up to 1200MHz. Built on Zen+ 12nm architecture, it delivers 35% faster performance than Intel N150/N100 series chips, making it ideal for light gaming, video playback, home office, and multitasking workstations.
  • HIGH-SPEED 16GB DUAL DDR4 + 512GB PCIe SSD --- Comes preinstalled with 16GB dual-channel DDR4 (2×8GB) and a 512GB M.2 PCIe 3.0 SSD for blazing-fast boot, load, and transfer speeds. Easily upgradeable up to 32GB RAM and 2×8TB SSDs with dual M.2 2280 PCIe 3.0 slots for unmatched storage flexibility.
  • SMOOTH TRIPLE 4K@60Hz DISPLAY OUTPUT --- Supports triple-display setup via HDMI 2.1 TMDS, DisplayPort 1.4, and USB-C. The Radeon Vega 8 GPU handles 4K@60Hz video editing, office visuals, and casual design tasks smoothly. Ideal for financial trading, productivity dashboards, and multi-window workflows.
  • 2.5GbE ULTRA-FAST NETWORKING + SERVER READY --- Equipped with a 2.5GbE RJ45 LAN port, the G10 offers up to 2500Mbps stable wired internet speed. Perfect for office work, media server setups, Pfsense, Untangle routers, or secure network appliances. No more bottlenecks in data-intensive environments.
  • COMPACT SIZE, FULL I/O, NEXT-GEN WIRELESS --- Palm-sized mini desktop comes packed with dual USB 3.2 Gen1, USB 2.0, USB-C (Full-Function: PD/DP/Data), DisplayPort, HDMI, and 3.5mm audio jack. Stay connected with WiFi 5 + Bluetooth 5.2. Great for office desks, minimalist setups, or VESA mounting.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.