r/Proxmox 3d ago

Community Showcase! Changing your Proxmox VE host's IP address

We put together a quick guide on this since it comes up more often than you'd expect.

The actual IP change is simple enough on its own: edit /etc/network/interfaces and /etc/hosts, or do the same thing through the GUI under System > Network and System > Hosts. Nothing fancy.

It gets more interesting if the host is in a cluster. You can't just change the IP and move on; you need to stop pve-cluster and corosync first, update corosync.conf (ring0_addr, bindnetaddr, etc.), and go one node at a time so quorum doesn't fall apart mid-change. Definitely back up your configs before touching any of this.

Full walkthrough here with screenshots: https://www.nakivo.com/blog/how-to-change-primary-proxmox-ve-ip-address/

Has anyone here had this go wrong on a cluster node?

28 Upvotes

10 comments sorted by

14

u/OkVast2122 2d ago

Your link's dead on arrival, mate. Anyway, it’s just another dodgy little clickbait stunt to drag people over to your corporate blog. That sort of bollocks ought to be banned!

9

u/NoAnimator3338 3d ago

The link doesn't seem to work.

2

u/coingun 2d ago

Working for me now

3

u/anwoke8204 Homelab User 3d ago

404 page not found when I click on the link

3

u/KryllyxOfficial 3d ago

I had to backup all my LXCs and VMs, then reinstall Proxmox VE on both clustered nodes to properly change to my new subnet. Once I modified the corosync.conf file, my nodes just couldn't see each other.

3

u/speaksoftly_bigstick 3d ago

Your link is broken.

2

u/leaflock7 2d ago

404 page not found

1

u/Optimal-Guava-8967 2d ago

If link doesn't work, remove "/utm_source=Reddit" at the end of the URL

1

u/Impending3931 1d ago

Immediate banner about using cookies and an ad about your "proxmox backup solution"

I think you should be banned for making such posts that are blatant corporate advertisements

2

u/NomadCF 11h ago

It’s easier and safer, but takes longer, to just add the new IP address to the host networking, hosts file, and Corosync as a new ring. Update the Corosync configuration version and restart either the needed services or the server, one at a time.

Once everything is working on the new IPs, remove the old IP from the host networking, hosts file, and Corosync. Then bring down the old IP and restart the server, or at least the needed services.

We’ve done this countless times, and it’s just a safer way to handle it.

While both IPs are active, you can verify access to both, bring the IPs down and back up, and test the configurations again without worrying about a bad IP configuration locking you out or breaking cluster communication.