No GUI after configuration changes

Penobscot

New Member
Nov 2, 2025
1
0
1
I am testing Proxmox on a spare server, with an eye toward a potential production cluster to replace our current infrastructure.

Initial installation went OK; however, that was just an unmanaged interface connected to an access mode switch port. Goal was to cable one server port to each switch and connect using LACP on trunked ports. Once I added a pair of OVSIntPorts and both an OVSBridge and OVSBond through the GUI, and updated the switches, the server had no connectivity; i.e., I could not ping the gateway from the server, nor could I ping the server.

I hand-edited interfaces, connectivity is good, and LACP works as expected. Unfortunately, I cannot get to the GUI. wget --no-check-certificate https://192.168.x.x:8006/ from the console shows the GUI is alive and well. Thanks for any help.

Code:
source /etc/network/interfaces.d/*

auto lo
iface lo inet loopback

auto enp0
iface enp0 inet manual
    ovs_mtu 1500

auto enp1
iface enp1 inet manual
    ovs_mtu 1500

auto vlanX
iface vlanX inet static
    address 192.168.X.X/24
    gateway 192.168.X.1
    netmask 255.255.255.0
    ovs_type OVSIntPort
    ovs_bridge vmbr0
    ovs_options tag=__
    ovs_mtu 1500
    dns-nameservers 192.168.X.X 192.168.X.X
    dns-search domain.local

auto vlanY
iface vlanY inet static
    address 192.168.Y.Y/24
    ovs_type OVSIntPort
    ovs_bridge vmbr0
    ovs_options tag=__
    ovs_mtu 1500
    dns-nameservers 192.168.X.X 192.168.X.X
    dns-search domain.local

auto bond0
iface bond0 inet manual
    ovs_type OVSBond
    ovs_bridge vmbr0
    ovs_bonds enp0 enp1
    ovs_options bond_mode=balance-tcp lacp=active

auto vmbr0
iface vmbr0 inet manual
    ovs_type OVSBridge
    ovs_ports vlanX vlanY bond0

Code:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue 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: enp0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system qlen 1000
link/ether xx:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff
inet6 fe80::xxxx:xxxx:xxxx:xxxx/64 scope link
valid_lft forever preferred_lft forever
3: enp1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system qlen 1000
link/ether xx:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff
inet6 fe80::xxxx:xxxx:xxxx:xxxx/64 scope link
valid_lft forever preferred_lft forever
4: ovs-system: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
link/ether xx:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff
5: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue qlen 1000
link/ether xx:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff
inet6 fe80::xxxx:xxxx:xxxx:xxxx/64 scope link
valid_lft forever preferred_lft forever
6: vlan__: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue qlen 1000
link/ether xx:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff
inet 192.168.X.X/24 scope global vlan__
valid_lft forever preferred_lft forever
inet6 fe80::xxxx:xxxx:xxxx:xxxx/64 scope link
valid_lft forever preferred_lft forever
7: vlan__: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue qlen 1000
link/ether xx:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff
inet 192.168.Y.Y/24 scope global vlan__
valid_lft forever preferred_lft forever
inet6 fe80::xxxx:xxxx:xxxx:xxxx/64 scope link
valid_lft forever preferred_lft forever
8: bond0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue qlen 1000
link/ether xx:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff
inet6 fe80::xxxx:xxxx:xxxx:xxxx/64 scope link
valid_lft forever preferred_lft forever