Unable to access web GUI after Interface and IP change

datathinkmonkey

New Member
May 14, 2023
2
0
1
I changed my Network interface and IP address and now I'm unable to access the Web GUI. I was previously on interface eno1 with IP 192.168.9.3/24, I am now on interface eno2 with IP 192.168.1.3/24. I can ssh but can't access the web GUI.

pveversion
pve-manager/6.3-3/eee5f901 (running kernel: 5.4.78-2-pve)


/etc/network/interfaces
iface lo inet loopback iface eno1 inet manual iface eno2 inet manual iface eno3 inet manual iface eno4 inet manual auto vmbr0 iface vmbr0 inet manual bridge-ports eno1 bridge-stp off bridge-fd 0 bridge-vlan-aware yes bridge-vids 2-4094 auto vmbr1 iface vmbr1 inet static address 192.168.1.3/24 gateway 192.168.1.1 bridge-ports eno2 bridge-stp off bridge-fd 0 bridge-vlan-aware yes bridge-vids 2-4094

/etc/hosts
127.0.0.1 localhost.localdomain localhost 192.168.1.3 pve.lan pve # The following lines are desirable for IPv6 capable hosts ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters ff02::3 ip6-allhosts

/etc/hostname
pve

service pveproxy status
pveproxy.service - PVE API Proxy Server Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2023-05-12 23:35:49 CDT; 21h ago Process: 2481 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS) Process: 2483 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS) Process: 7144 ExecReload=/usr/bin/pveproxy restart (code=exited, status=0/SUCCESS) Main PID: 2485 (pveproxy) Tasks: 4 (limit: 4915) Memory: 136.4M CGroup: /system.slice/pveproxy.service ├─2485 pveproxy ├─7177 pveproxy worker ├─7178 pveproxy worker └─7179 pveproxy worker May 13 00:00:03 pve pveproxy[2485]: starting 3 worker(s) May 13 00:00:03 pve pveproxy[2485]: worker 7177 started May 13 00:00:03 pve pveproxy[2485]: worker 7178 started May 13 00:00:03 pve pveproxy[2485]: worker 7179 started May 13 00:00:08 pve pveproxy[2488]: worker exit May 13 00:00:08 pve pveproxy[2486]: worker exit May 13 00:00:08 pve pveproxy[2487]: worker exit May 13 00:00:08 pve pveproxy[2485]: worker 2486 finished May 13 00:00:08 pve pveproxy[2485]: worker 2487 finished May 13 00:00:08 pve pveproxy[2485]: worker 2488 finished

systemctl status pvedaemon
pvedaemon.service - PVE API Daemon Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2023-05-12 23:35:47 CDT; 21h ago Process: 2402 ExecStart=/usr/bin/pvedaemon start (code=exited, status=0/SUCCESS) Main PID: 2476 (pvedaemon) Tasks: 4 (limit: 4915) Memory: 138.9M CGroup: /system.slice/pvedaemon.service ├─2476 pvedaemon ├─2477 pvedaemon worker ├─2478 pvedaemon worker └─2479 pvedaemon worker May 12 23:35:44 pve systemd[1]: Starting PVE API Daemon... May 12 23:35:47 pve pvedaemon[2476]: starting server May 12 23:35:47 pve pvedaemon[2476]: starting 3 worker(s) May 12 23:35:47 pve pvedaemon[2476]: worker 2477 started May 12 23:35:47 pve pvedaemon[2476]: worker 2478 started May 12 23:35:47 pve pvedaemon[2476]: worker 2479 started May 12 23:35:47 pve systemd[1]: Started PVE API Daemon.


ss -antlp | grep pveproxy
LISTEN 0 128 0.0.0.0:8006 0.0.0.0:* users:(("pveproxy worker",pid=7179,fd=6),("pveproxy worker",pid=7178,fd=6),("pveproxy worker",pid=7177,fd=6),("pveproxy",pid=2485,fd=6))

curl https:/127.0.0.1:8006 -s -k | grep title
<title>pve - Proxmox Virtual Environment</title>
 

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!