[8.4] Can't connect to GUI after update

V

vduvernet

New Member
Jun 2, 2025
1
0
1
Hello,

this seems to be a problem that several users are experiencing.
Being new to Proxmox, I realize that it will take me some trial and error to get the hang of it.
My initial goal was to migrate my two VMs to a new Proxmox VE 9 server. I didn't create a cluster (as I wasn't supposed to).
I wanted to change the name of the old Proxmox server (from "pve" to "pve-01") and then perform the updates. It seems that after several consecutive updates and reboots, something went wrong.
I logged in locally, changed the DNS settings to 8.8.8.8 and 8.8.4.4, as my VM was acting as the DNS server.
I ran the following update commands:
Bash: 
apt list upgrade
apt full-upgrade
I can connect to it using PuTTY.
Bash: 
ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: ens5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr 0 state UP group default qlen 1000
link/ether 00:8e:25:79:02:cb brd ff:ff:ff:ff:ff:ff
altname enp3s0
3: enp1s0f0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 00:1e:67:2c:1f:08 brd ff:ff:ff:ff:ff:ff
4: enp1s0f1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 00:1e:67:2c:1f:09 brd ff:ff:ff:ff:ff:ff
5: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 00:8e:25:79:02:cb brd ff:ff:ff:ff:ff:ff
inet 172.20.32.11/16 scope global vmbr0
valid_lft forever preferred_lft forever
inet6 fe80::28e:25ff:fe79:2cb/64 scope link
valid_lft forever preferred_lft forever

Bash: 
cat /etc/network/interfaces
auto lo
iface lo inet loopback

iface ens5 inet manual

auto vmbr0
iface vmbr0 inet static
address 172.20.32.11/16
gateway 172.20.0.1
bridge-ports ens5
bridge-stp off
bridge-fd 0

iface enp1s0f0 inet manual

iface enp1s0f1 inet manual

source /etc/network/interfaces.d/*

I can ping gateway and outside :
root@pve:~# ping 172.20.0.1
PING 172.20.0.1 (172.20.0.1) 56(84) bytes of data.
64 bytes from 172.20.0.1: icmp_seq=1 ttl=64 time=0.392 ms
64 bytes from 172.20.0.1: icmp_seq=2 ttl=64 time=0.291 ms
^C
--- 172.20.0.1 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1036ms
rtt min/avg/max/mdev = 0.291/0.341/0.392/0.050 ms
root@pve:~# ping www.google.fr
PING www.google.fr (216.58.214.163) 56(84) bytes of data.
64 bytes from mad01s26-in-f163.1e100.net (216.58.214.163): icmp_seq=1 ttl=114 time=8.74 ms
64 bytes from par10s42-in-f3.1e100.net (216.58.214.163): icmp_seq=2 ttl=114 time=8.34 ms
^C
--- www.google.fr ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 8.335/8.537/8.739/0.202 ms

And from my LAN, I can ping 172.20.32.11

In my browser tab, I see these 2 pages I followed :
S

[SOLVED] Thread 'Proxmox change IP address'

Hi,

I recently attempted to change the IP address of my Proxmox server (192.168.3.12---> 192.168.10.54) and updated it in the /etc/network/interfaces file but to no success. Surprisingly, reverting to the old IP (192.168.3.12) while connected to the (192.168.10.XX) network resolved the issue.

Any insights into what might be causing this?
https://pve.proxmox.com/wiki/Renaming_a_PVE_node

Thanks for help,
Vincent
 
You must log in or register to reply here.
Top Bottom