How to change Proxmox default IP at bootup

CancunManny

New Member
Dec 30, 2023
20
1
3
Hello, and thanks in advance for any and all help.

I set up my first Proxmox server. When I did my original setup I only had one ethernet port. I set up proxmox, HomeAssistant and Frigate with only that one ethernet port. It picked up a 192.168.0.x IP for Proxmox and another for HomeAssistant.

I then installed a pcie with 2 giga bit ethernet ports and ran OPNsense. I connect my WAN cable onto one of the ports, then the other port is connected to a switch. The switch then connects to the original ethernet port on my mother board, that ends up giving the IP to Proxmox, HA, etc.

Everything is working just fine. I went ahead and updated the IPs for Proxmox, HA, etc. I would say my system is 100% stable at the moment, but I did noticed that if I connect a monitor and keyboard to the server, after it boots it says system can be accessed via the 192.168.0.x address it picked up during the first time the machine was set up. How can I change that IP?
 
By default PVE will use static IPs and not DHCP. And I would also stick with that so you can SSH into the PVE host or access its webUI if your OPNsense running your DHCP server fails to start.

You can change its IP by changing the IP on the bridges and the hosts file via the webUI.
 
By default PVE will use static IPs and not DHCP. And I would also stick with that so you can SSH into the PVE host or access its webUI if your OPNsense running your DHCP server fails to start.

You can change its IP by changing the IP on the bridges and the hosts file via the webUI.
I seem to have redundancy. My OPNsense gives a specific IP to proxmox server, and proxmox server has the same IP set up as static. All that seems to be working fine. In fact if I run proxmox as most do, headless, I wouldn't even notice I have an issue.

When a monitor is plugged in to the server, when it reboots, before the login prompt shows up I get a message "you can access this server by pointing your browser to 192.168.1.x" The IP that shows is the first static IP I assigned with the old router, so it seems to be bad info.

I think bbgeek17 pointed me in the right direction. I will check.
 
https://man7.org/linux/man-pages/man5/issue.5.html



Blockbridge: Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Thank you so much! That is exactly what I was looking for. I went ahead and edited the file, put in the correct IP and added a little note reminding me to make sure to plug the network cable onto the motherboards ethernet port, as that is vmbr0, the one being used by proxmox.

For those that were wondering what I was talking about, this is the message I was getting :

"Welcome to the Proxmox Virtual Environment. Please use your web browser to
configure this server - connect to: 192.168.x.x"
 
iirc, /etc/issue is regenerated each boot by pvebanner service, you need to disable service if you want custom /etc/issue
 
iirc, /etc/issue is regenerated each boot by pvebanner service, you need to disable service if you want custom /etc/issue
Hola gabriel and thanks for your feedback. My system has had a couple of bad shut downs (power went out), but since then I've done over 10 reboots/shutdowns the proper way and I was still getting the old IP listed at bootup.

Since the correct IP wasn't been updated on the issue file at shutdown, would it mean that somehow pvebanner service got disabled somehow?
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!