[SOLVED] Web UI doesn't work when PCIe card connected

[veejaypaal]

Hello all!

I did a fresh install of Proxmox VE 7.4 (and now also tried with 8.0) on a single Intel Optane P1600X SSD. After installing, I am able to access the web UI at https://192.168.0.100:8006. Everything works fine, no problems. But when I install a PCIe add-on card with two more identical Optane SSDs, the web UI doesn't load.
The add-on card is Ableconn PEXM2-130. It uses an ASMedia ASM2824 Switch for connecting 2 NVMe SSDs to one PCIe slot.

When I ping the Proxmox machine from my Windows laptop (192.168.0.107), I get this error - Reply from 192.168.0.107: Destination host unreachable.
When I ping my router (192.168.0.1) from my Proxmox machine, I get this error - From 192.168.0.100 icmp_seq=1 Destination Host Unreachable

I get the following result for 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 valid_lft forever preferred_lft forever 2: enp11s0: <BROADCAST, MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether c8:7f:54:55:cc:83 brd ff:ff:ff:ff:ff:ff 3: wlo1: <BROADCAST, MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether c8:cb:9e:ce:90:5a brd ff:ff:ff:ff:ff:ff altname wlp0s20f3 4: vmbr0: <NO-CARRIER, BROADCAST, MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether d2:0e:ca:af:d5:88 brd ff:ff:ff:ff:ff:ff inet 192.168.0.100/24 scope global vmbr0 valid_lft forever preferred_lft forever

And following is the result for cat /etc/network/interfaces

auto lo iface lo inet loopback iface enp6s0 inet manual auto vmbr0 iface vmbr0 inet static address 192.168.0.100/24 gateway 192.168.0.1 bridge-ports enp6s0 bridge-stp off bridge-fd 0

If I remove the add-on card then I'm able to access the web GUI again. Then I get the following results -

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 valid_lft forever preferred_lft forever 2: enp6s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP group default qlen 1000 link/ether c8:7f:54:55:cc:83 brd ff:ff:ff:ff:ff:ff 3: wlo1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether c8:cb:9e:ce:90:5a brd ff:ff:ff:ff:ff:ff altname wlp0s20f3 4: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether c8:7f:54:55:cc:83 brd ff:ff:ff:ff:ff:ff inet 192.168.0.100/24 scope global vmbr0 valid_lft forever preferred_lft forever inet6 fe80::ca7f:54ff:fe55:cc83/64 scope link valid_lft forever preferred_lft forever
and

auto lo iface lo inet loopback iface enp6s0 inet manual auto vmbr0 iface vmbr0 inet static address 192.168.0.100/24 gateway 192.168.0.1 bridge-ports enp6s0 bridge-stp off bridge-fd 0 iface wlo1 inet manual

I'm a total noob when it comes to Linux and Proxmox, so obviously I have no idea how to proceed. Thanks in advance for any guidance or help!

 

[UltraHKR]

This is an easy one

Replace on the network config:
iface enp11s0 inet manual

With these:
auto enp11s0 iface enp11s0 inet manual

What it does is tell the OS to bring up the network device at boot, why PVE does not include it by default, is beyond me.

EDIT: as @Neobin mentioned below the interface name is changing, so you need to adjust the config.
(I didn't see that at a glance good catch)

 

[Neobin]

Change:

iface enp6s0 inet manual

and:

bridge-ports enp6s0

to:

2: enp11s0: <BROADCAST, MULTICAST>

in your: /etc/network/interfaces and reboot the PVE-host.

 

[Neobin]

why PVE does not include it by default, is beyond me.

Afaik, the bridge brings up the underlaying interface(s) automatically and on the bridge you have e.g.: auto vmbr0.

Iirc, it might even be counterproductive to also bring up the underlaying interface(s) before/together with the bridge. But not sure on this; I think, I read about problems with it in the past...

 

[veejaypaal]

Thank you so much Neobin and UltraHKR!
I used nano /etc/network/interfaces to change the interface name to the one that gets assigned in ip a and now it works flawlessly.