Cant change proxmox ip address

catdog

New Member
Nov 29, 2024
3
0
1
I needed to change ip from 192.168.1.185 to other subnet 172.16.0.185 so I did it in GUI network/edit linux bridge.
Rebooted.
But after that I was not able to log in not new and not old address. I looked locally and there was still text "log in 192.168.1.185" - that's old address. When I do
Code:
nano /etc/network/interfaces
I see correct new address.
So I am stuck now
 
Hi @catdog,
changing an IP address on an appliance, which one could consider Proxmox to be, is often more complex than a single file/click.
Please review the following resources and implement the steps you missed:
https://www.servethehome.com/how-to-change-primary-proxmox-ve-ip-address/
https://www.reddit.com/r/Proxmox/comments/xdkeqz/actual_correct_way_to_change_the_ip_of_proxmox/
https://www.youtube.com/watch?v=3JR5XPkab-c
https://www.youtube.com/watch?v=iMawZgbEMAg

Good luck


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
Last edited:
  • Like
Reactions: UdoB
You are not the only one. Fresh 8.3 installation, and I changed the IP of the bridge adapter and hosts file in the GUI. Applied changes lost connection. Then I rebooted the server, the old IP was still listed on the banner however I could not communicate over the old ip or new one.

I then from the command line checked the /etc/network/interfaces and it showed the correct IP address, subnet mask and gateway.
I checked the hosts file and it also was updated but I still could not connect. I could not ping out from the server either.

I set another machine to the same IP and plugged into the same switch port the PVE host was plugged into and I could connect and scan the network no problem.

Something is definitely off in the updating of the IP address. Searching the forums was Zero help although it enforced my belief that this problem has existed for far longer than 8.3.

The only way to resolve it was to reinstall the OS. Based on this alone I am not moving forward with Proxmox. Sad really as it looked so promising.

Your tech team really needs to do a better job at the basics of your product. I know most people are going to reply it works for me. That's fine, but if I was a fringe case I would give it second thought, but I see far to many posts over the years of people having the exact same issues. For a product current on its 8th release and 3rd sub version, problems like this should not exist.

No clear documentation in the docs on how to troubleshoot it. Firewall was not enabled either. Very disappointing. Going back to Cockpit with BTRFS, KVM, and Dockge.

I can't stress enough how disappointing this was.
 
You are not the only one. Fresh 8.3 installation, and I changed the IP of the bridge adapter and hosts file in the GUI. Applied changes lost connection. Then I rebooted the server, the old IP was still listed on the banner however I could not communicate over the old ip or new one.

I then from the command line checked the /etc/network/interfaces and it showed the correct IP address, subnet mask and gateway.
I checked the hosts file and it also was updated but I still could not connect. I could not ping out from the server either.

I set another machine to the same IP and plugged into the same switch port the PVE host was plugged into and I could connect and scan the network no problem.

Something is definitely off in the updating of the IP address. Searching the forums was Zero help although it enforced my belief that this problem has existed for far longer than 8.3.

The only way to resolve it was to reinstall the OS. Based on this alone I am not moving forward with Proxmox. Sad really as it looked so promising.

Your tech team really needs to do a better job at the basics of your product. I know most people are going to reply it works for me. That's fine, but if I was a fringe case I would give it second thought, but I see far to many posts over the years of people having the exact same issues. For a product current on its 8th release and 3rd sub version, problems like this should not exist.

No clear documentation in the docs on how to troubleshoot it. Firewall was not enabled either. Very disappointing. Going back to Cockpit with BTRFS, KVM, and Dockge.

I can't stress enough how disappointing this was.
Okay so I changed to DHCP and added an entry into the reservation for the MAC address. I got the IP address on the correct VLAN and everything is working.

So I tried again to set the IP configuration to STATIC and used the same IP currently assigned. Not working again, rebooted, nothing.
 
Last edited:
I found the reason. The web gui does not write /etc/network/interfaces with the correct syntax!@!@!@!@


When editing the IP configuration in the GUI it attempts to write the file as such

address 192.168.1.10/24

*** this is incorrect ** OR not working correctly ***

it should be formatted like the below:

auto vmbr0
iface vmbr0 inet static
address 192.168.1.10
netmask 255.255.255.0
gateway 10.0.12.1
bridge-ports enp4s0
bridge-stp off
bridge-fd 0


Applied these edits and ran ifdown and ifup .... working.

PVE Team please fix the GUI so that it writes the /etc/network/interfaces file correctly.
 
Last edited:
When editing the IP configuration in the GUI it attempts to write the file as such

address 192.168.1.10/24

*** this is incorrect
This works fine here and has worked for years (and is in the manual and Wiki). Are you running a Proxmox older than 7? Do you have ifupdown2 installed?

EDIT: Sorry for not reading this thread more closely. I have no clue why your fresh up-to-date installation behaves differently.
 
Last edited:
This works fine here and has worked for years (and is in the manual and Wiki). Are you running a Proxmox older than 7? Do you have ifupdown2 installed?
Apologies, I am sharing my experience. If you read my post this is a fresh installation of 8.3. What I did above resolved it for me. Please reread the thread and then offer additional advice.

Furthermore since when does a reboot or restart of the networking service not accomplish the same thing as ifupdown2?

If this is a required step, and not installed by default with a fresh installation, why on earth would the apply configuration button NOT run these steps as a scripted action?

The question should be why does it not work like intended when changing the IP from the GUI. As a software designer if you want new user adoption which is why most softwares include a GUI, you should make the basics work flawlessly.

An additional question should be, if you CAN omit the netmask declaration (I do understand this is the case in most distros, I am not a linux newb), and instead use the CIDR notation, WHY was it NOT working?

I tried several recommended guides, the node was not part of a cluster, so sync files did not exist so they did not need to be edited.
 
Last edited:

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!