How to Set a Static IP Address in Proxmox VE

Introduction

If your Proxmox VE host picked up its IP address automatically during installation, you might be wondering if that's actually a problem. In most cases, it is, at least for anything beyond quick testing.

Home routers and DHCP servers can hand out a different address to your Proxmox host after a reboot or a lease renewal. If that happens, the bookmark you saved for the web interface stops working, and any virtual machines or scripts that reference the host by IP break too. Giving your Proxmox host a fixed, predictable address solves that problem for good.

In this tutorial, we'll go through exactly what a static IP address is, why it matters for a virtualization host in particular, and how to set one up safely using both the Proxmox web interface and the command line.

What You Will Learn

The difference between a dynamic (DHCP) and a static IP address
Why a virtualization host benefits from a fixed address more than a regular computer does
How to check your current network settings before making changes
How to set a static IP address using the Proxmox web interface
How to set a static IP address by editing the network configuration file directly
How to safely test the change without locking yourself out
Common mistakes and how to recover if something goes wrong

What Is This Feature?

Every device on a network needs an IP address to be reachable, the same way every house needs a street address for mail to arrive. There are two common ways a device gets one:

Dynamic IP (DHCP): Your router automatically assigns an address from a pool whenever the device connects. It's convenient, but the address can change over time.
Static IP: You manually assign a specific address that never changes, no matter how many times the device reboots or reconnects.

On Proxmox VE, your network settings live in a file called /etc/network/interfaces. This file controls how the host's physical network card and its virtual bridge are configured. A bridge, usually named vmbr0 by default, is a piece of virtual networking hardware that lets your physical network card be shared between the Proxmox host itself and all the virtual machines running on it. Think of it as a virtual network switch living inside your server.

Why Would You Use It?

A regular laptop can usually get away with a dynamic address, since you mostly access it directly and don't rely on remembering its IP. A Proxmox host is different, because so many other things depend on it staying reachable at a predictable address:

Scenario	What Happens With a Dynamic IP	What Happens With a Static IP
Router reboots or renews leases	Proxmox may get a new address, breaking your saved bookmark	Address stays exactly the same
Accessing the web interface	You may need to search your router for the current address	You always use the same known address
Scripts, monitoring tools, or backup jobs referencing the host	They can silently fail after an address change	They keep working without any changes
Setting up port forwarding or firewall rules	Rules can point to the wrong device after a change	Rules remain accurate over time

Because Proxmox is the foundation everything else runs on, its address is worth locking down early, ideally right after installation, before you start creating virtual machines.

This matters even more once you start adding virtual machines and containers of your own. Each VM typically gets its own IP address too, but those are managed separately, inside each guest's own network settings. The static IP address you configure in this guide is specifically for the Proxmox host itself, the physical or cloud server that everything else runs on top of.

Prerequisites

Before you begin, make sure you have:

A working Proxmox VE installation with access to its web interface or a keyboard and monitor connected directly to the server
Your network details ready: the IP address you want to use, the subnet mask (commonly written as /24), your router's IP address (the gateway), and a DNS server address (your router's address usually works fine)
Physical or console access to the server as a backup, in case a mistake in the network configuration locks you out of the web interface
Root access to the Proxmox host, either through SSH or the built-in console

That last point is worth taking seriously. If you make a typo in a network file and access the host only through the web interface over the network, you could lose access entirely until you can plug in a monitor and keyboard directly, so always have a fallback option ready.

Step-by-Step Tutorial

Step 1: Check Your Current Network Settings

Before changing anything, it helps to see what you're working with. Log in to the Proxmox host, either through SSH or the console, and run:

ip a

This lists all network interfaces on the host along with their current IP addresses. Look for the interface named something like vmbr0, which is the default network bridge Proxmox creates during installation.

You should also note your router's address, since that will become your gateway. You can usually find it with:

ip route | grep default

Step 2: Set a Static IP Using the Web Interface

This is the safer option for most beginners, since the web interface won't let you save an invalid configuration.

Log in to the Proxmox web interface
Select your Proxmox node (the server itself) in the left-hand tree
Click System, then Network
Select the vmbr0 bridge and click Edit
Change IPv4/CIDR to your desired static address, written with a slash and the subnet size, for example 192.168.1.50/24
Set Gateway to your router's IP address, for example 192.168.1.1
Click OK, then click the Apply Configuration button at the top of the Network page

Proxmox will warn you that this change may disconnect your current session. That's expected, since you're changing the very address you're connected through.

Step 3: Set a Static IP by Editing the Configuration File

If you prefer working from the command line, or you're setting this up before the web interface is reachable, you can edit the network file directly.

Open the file with a text editor:

nano /etc/network/interfaces

Find the section for vmbr0 and adjust it to look similar to this, replacing the example values with your own network details:

auto vmbr0
iface vmbr0 inet static
    address 192.168.1.50/24
    gateway 192.168.1.1
    bridge-ports eno1
    bridge-stp off
    bridge-fd 0

Save the file, then exit the editor. In nano, that's Ctrl+O to save and Ctrl+X to exit.

Step 4: Apply the New Configuration

Changes to this file don't take effect automatically. Apply them with:

ifreload -a

This reloads the network configuration without requiring a full reboot. If ifreload isn't available on your system, a full restart of the networking service works as well:

systemctl restart networking

Step 5: Confirm the Change Worked

Reconnect to the web interface using the new address, for example https://192.168.1.50:8006. From the console, you can also confirm the change directly with the same command from Step 1:

ip a

You should see the new address listed under vmbr0.

Commands Explained

Command	What It Does
`ip a`	Lists all network interfaces on the host and their current IP addresses
`ip route \| grep default`	Shows the current default gateway, which is usually your router's address
`nano /etc/network/interfaces`	Opens the main network configuration file in a simple text editor
`ifreload -a`	Reloads all network interfaces using the updated configuration file, without a full reboot
`systemctl restart networking`	Restarts the entire networking service as a fallback if `ifreload` isn't available

Common Errors

Web interface becomes unreachable after applying changes

This almost always means the new IP address, subnet, or gateway doesn't actually match your network. Double-check that the address you chose is inside the same subnet as your router, and that you didn't mistype the gateway.

error: vmbr0 is not up

This usually points to a syntax mistake in /etc/network/interfaces, such as a missing line, incorrect indentation, or a typo in a keyword like bridge-ports. Review the file carefully against the example in Step 3.

Duplicate IP address on the network

This means another device is already using the address you tried to assign. Pick a different, unused address, ideally one outside your router's DHCP range so it never gets handed out to another device automatically.

Troubleshooting

Locked out of the web interface? Connect a monitor and keyboard directly to the server, log in at the console, and review or revert your changes in /etc/network/interfaces.
Not sure what subnet your network uses? Check your router's admin page, or look at the subnet mask of another device already connected to the same network.
Configuration file looks correct but changes won't apply? Try a full reboot of the host as a last resort: reboot. This forces networking to reinitialize from the saved file.
Picked an address that's inside your router's DHCP pool? Even if it works today, your router could eventually hand that same address to another device, causing a conflict. Choose an address outside the DHCP range, or shrink the DHCP range in your router's settings.

Best Practices

Choose a static address outside your router's DHCP range to avoid future conflicts
Write down or document your chosen IP address, gateway, and subnet somewhere outside the server itself
Always keep console access available (physical or through your server's remote management tools) before making network changes remotely
Make one change at a time and confirm connectivity before making further edits
Consider reserving the same address in your router's DHCP settings as a second layer of protection, so even a misconfigured Proxmox host reverts to a known address if it falls back to DHCP
If your server has more than one network card, keep the extra one unconfigured until you have a specific reason to use it, such as separating storage traffic from management traffic later on
Avoid changing the network configuration during a remote session unless you have console access as a fallback, especially on a server you can't easily walk over to

Frequently Asked Questions

What IP address should I choose?

Pick any unused address within your local network's subnet, ideally outside your router's DHCP range. For a typical home network using 192.168.1.0/24, an address like 192.168.1.50 is a common, safe choice.

Can I change my Proxmox host's IP address after I've already created virtual machines?

Yes. Changing the host's own IP address doesn't affect the virtual machines' configurations directly, though you may need to update any saved bookmarks or scripts that reference the old address.

Do I need to restart the whole server after changing the network settings?

Usually not. Running ifreload -a or restarting the networking service is enough. A full reboot is only needed if those commands don't resolve the issue.

What's the difference between the host's IP address and a virtual machine's IP address?

The host's address is used to reach the Proxmox web interface and manage the server itself. Each virtual machine has its own separate IP address, used to reach whatever is running inside that particular VM. Setting a static address for the host does not automatically set one for your VMs.

Is it safe to do this over SSH instead of the web interface?

It works, but it carries slightly more risk, since an SSH session will drop the moment the interface goes down during the change. If you're using SSH, keep a separate console session open as a backup in case you get disconnected.

Conclusion

A static IP address turns your Proxmox host into a stable, predictable part of your network instead of a moving target. It takes only a few minutes to set up, either through the friendly web interface or by editing the configuration file directly, and it prevents a whole category of annoying connectivity problems down the road.

Once your host has a fixed address, it's a good foundation to build on as you start creating virtual machines, containers, and the rest of your Proxmox setup.

Vormox is an independent virtualization management platform built on Proxmox VE. Proxmox® and Proxmox VE® are trademarks of Proxmox Server Solutions GmbH. Vormox is not affiliated with, endorsed by, or sponsored by Proxmox.

How to Configure a Static IP Address on Your Proxmox VE Host