You just installed Proxmox VE on an old desktop or a mini PC tucked away in a closet, and somewhere between confirming the install and watching the reboot, you lost track of one small detail: the IP address. The monitor's unplugged now, there's no keyboard attached, and you're sitting at your laptop with no idea how to reach that web interface everyone talks about.
This happens to almost everyone the first time. Proxmox doesn't email you the address or text it to your phone. It shows it to you once, briefly, and then it's up to you to remember or go find it again. The good news is there are several reliable ways to track it down, and none of them require plugging a monitor back into the server.
What You Will Learn
- Why Proxmox VE doesn't make the IP address obvious after installation
- How to read the console banner if you do have temporary monitor access
- How to find the address through your router's admin page
- How to scan your network from another computer using
nmaporarp-scan - What to do on Windows if you don't want to install anything extra
- How to stop this from happening again
What Is This Feature?
When you install Proxmox VE, the installer asks you to confirm a management network interface, an IP address, a netmask, a gateway, and a DNS server. It pre-fills those fields using whatever address your router handed out over DHCP the moment you booted the installer. Most people click through that screen without writing anything down, because at that point you're focused on getting the install finished, not memorizing an address you'll need later.
Once installation finishes and the box reboots, Proxmox brings up a Linux bridge called vmbr0 using whatever settings you confirmed. That bridge is what carries traffic to the web interface, and it's also what your virtual machines and containers will eventually plug into. The address itself doesn't change on its own after that point, but knowing it and remembering it are two very different problems.
There's a small feature built into Proxmox that helps here: a script called pvebanner generates the text shown on the console login screen, and it prints the current management IP directly into that message. If you have a monitor connected, this is usually the fastest way to get the address. If you don't, you'll need one of the other methods below.
Why Would You Use It?
You need this address for one simple reason: it's how you reach https://youripaddress:8006, the web interface where you actually manage Proxmox — creating VMs, uploading ISOs, checking backups, all of it. Without the IP, you're locked out of the GUI entirely, even though the server is running fine.
This matters even more for what people in the homelab world call a "headless" setup — a server with no monitor, keyboard, or mouse attached during normal operation. Mini PCs, old laptops with the lid closed, and rack-mounted servers tucked in a closet are usually run this way. You manage them entirely over the network, so if you don't know the address, you don't have a way in.
It's also worth knowing these methods for a second reason: sometimes the address changes on its own, usually because your router handed out a new DHCP lease after a long power outage or a router reboot. When that happens, your bookmarked URL stops working and you'll need to track down the new address the same way.
Prerequisites
You don't need much for this, but a couple of things make it easier:
- Access to your router's admin page, or a second computer on the same network
- The root password you set during installation, in case you need console or SSH access
- A wired network connection between the Proxmox host and your router or switch
That last point matters more than people expect. The Proxmox VE installer only configures wired Ethernet during setup — it has no built-in support for Wi-Fi as the management interface. If your server has a USB Wi-Fi dongle and no cable plugged in, the installer likely never got an address in the first place, and none of the methods below will find one. Plug in a cable before you go any further.
Step-by-Step Tutorial
Method 1: Read the Console Banner
If you can connect a monitor and keyboard for just a minute — even temporarily, even by carrying the whole machine to another room — this is the quickest option. Boot the server (or let it finish booting if it's already on), and once it reaches the login prompt you'll see a short message above it, something like:
Welcome to the Proxmox Virtual Environment. Please use your web browser to
configure this server - connect to: https://192.168.1.50:8006/That's your address. Type it into a browser on any device on the same network, accept the certificate warning (Proxmox uses a self-signed certificate by default, which is normal and not a sign of a problem), and you're in.
If you have IPMI, iDRAC, or iLO on a rack server, or you're running Proxmox inside a VM on a hypervisor with its own console viewer, you can read this same banner without touching any physical cables at all.
Method 2: Check Your Router's DHCP Client List
No monitor handy? Your router already knows the address — it's the one that handed it out. Log into your router's admin page (commonly something like 192.168.1.1 or 192.168.0.1, printed on a sticker on the router itself) and look for a page called Connected Devices, DHCP Client List, or LAN Clients. The exact wording depends entirely on your router's brand and firmware.
Scan the list for a hostname like pve or whatever you set as the hostname during installation. If the hostname isn't showing, look at the MAC address vendor prefix instead — Dell, Intel, and Realtek are common ones for typical homelab hardware, and most routers display the manufacturer name next to each MAC address automatically.
Method 3: Scan the Network with nmap (Linux and macOS)
If you have another Linux machine, a Mac, or WSL on Windows, a network scan will find the Proxmox host directly. Install nmap if you don't already have it:
sudo apt install nmap # Debian/Ubuntu
brew install nmap # macOSThen scan your local subnet. Adjust the range to match your own network — most home networks use 192.168.1.0/24 or 192.168.0.0/24:
sudo nmap -sn 192.168.1.0/24This sends a quick ping sweep across every address in that range and lists what responds, along with the MAC vendor for each device. Look through the results for a device made by the same manufacturer as your Proxmox hardware, or for a hostname of pve.
Method 4: Use arp-scan for a Faster, More Reliable Result
On Debian-based systems, arp-scan is often more reliable than a ping sweep, because it works at the network layer directly instead of relying on ICMP, which some devices or firewalls quietly ignore.
sudo apt install arp-scan
sudo arp-scan --localnetThis prints every device on your local network segment along with its MAC address and vendor name in a couple of seconds, no subnet math required.
Method 5: Find It From Windows Without Installing Anything
If Windows is the only machine you've got, open Command Prompt and ping your network's broadcast address once, just to populate your ARP table:
ping 192.168.1.255Then check what responded:
arp -aThis lists every IP and MAC address pair Windows has recently seen on the network. It's less precise than nmap or arp-scan since it won't show vendor names, so you may need to cross-reference the MAC address with your router's client list to be sure which one is the Proxmox host. If you'd rather have a proper GUI for this, a free tool like Advanced IP Scanner will do the same job with hostnames and vendor names shown right in the results.
Bonus: Give It a DHCP Reservation Once You Find It
Once you've tracked down the address, log into your router and set up a DHCP reservation tied to the Proxmox host's MAC address. This isn't the same thing as configuring a static IP on the host itself — it just tells your router "always give this specific device the same address," so you never have to repeat this whole process after the next power outage or router restart.
Commands Explained
| Command | What It Does |
|---|---|
ip a | Shows every network interface on the Proxmox host and its current IP address. Run this at the console or over SSH once you're already logged in. |
hostname -I | A shortcut that prints just the IP addresses assigned to the machine, without the rest of the interface details. |
nmap -sn 192.168.1.0/24 | Performs a ping sweep across the given subnet and lists which addresses responded, along with MAC vendor information. |
arp-scan --localnet | Sends ARP requests to every address on your local network segment and lists what answers — faster and more reliable than a ping sweep. |
arp -a | Windows and Linux both support this. It shows the ARP cache — recently seen IP-to-MAC address pairings — without sending any new network traffic. |
Common Errors
A few things trip people up once they think they've found the right address:
- "This site can't be reached" at port 8006 — almost always means you've got the wrong IP, or you're on a different subnet or VLAN than the Proxmox host. Double-check the address and confirm both devices are on the same network.
- Certificate warning in the browser — this is expected. Proxmox ships with a self-signed certificate out of the box, so every browser will flag it as untrusted until you either accept the warning or install your own certificate later.
- Multiple unknown devices in the router's client list — common on networks with several IoT gadgets or smart devices. Cross-reference by MAC vendor, or temporarily disconnect other devices to narrow it down.
- nmap finds nothing at all — either your scanning machine's firewall is blocking outbound ICMP, or you typed the wrong subnet range.
Troubleshooting
If none of the methods above turn up anything, work through these in order:
Check the physical connection first. A loose Ethernet cable, or a cable plugged into the wrong switch port, is the single most common reason a freshly installed server doesn't show up anywhere. Look for link lights on the NIC itself — no lights usually means no physical connection at all.
If you have multiple network cards in the server, confirm you plugged the cable into the same NIC you selected as the management interface during installation. It's an easy detail to get backwards, especially on machines with more than one onboard port.
If the cable is connected and you still can't find the address, get temporary console access (even once) and run ip a. If you see an address in the 169.254.x.x range instead of something from your normal LAN, that's a link-local address, meaning the interface never actually got a response from your router's DHCP server. That points to a DHCP pool that's run out of addresses, or a port on a managed switch that isn't passing DHCP traffic through.
Best Practices
Write the IP address down somewhere the moment you find it — a sticky note on the server case works better than most people expect. Set up that DHCP reservation mentioned earlier so the address never changes again without your say-so. If your router supports local DNS entries, give the server a friendly hostname like pve.home so you're not memorizing a numeric address at all.
Once you're comfortable finding the address, it's a good time to also enable SSH access and change the root password if you haven't already, since you'll likely need both the next time something changes on your network.
Frequently Asked Questions
What port does the Proxmox VE web interface use?
Port 8006, over HTTPS. The full address always looks like https://youripaddress:8006.
Can Proxmox VE connect over Wi-Fi?
Not through the installer. It only configures a wired NIC as the management interface during setup. Wi-Fi can be configured manually afterward, but it isn't officially supported for managing the host and most homelab guides recommend against it.
Why did my Proxmox server's IP address change after a power outage?
Your router likely handed out a new DHCP lease. Set up a DHCP reservation tied to the server's MAC address to stop this from happening again.
Do I need to install anything to scan my network?
On Windows, no — arp -a works out of the box. On Linux or macOS, nmap and arp-scan are small packages you can install in seconds with your package manager.
Is it safe to leave the server accessible this way?
Finding the IP address doesn't expose anything by itself. The web interface still requires your root password to log in, same as always.
Conclusion
Losing track of a freshly installed server's address is one of those small, slightly annoying moments almost every Proxmox user runs into once. It looks like a bigger problem than it actually is — your router, or a two-second network scan, already has the answer sitting there. Once you've found it and locked in a DHCP reservation, this becomes a one-time inconvenience rather than something you deal with every time the power flickers.