starred/proxcenter-ui

Fork 0

mirror of https://github.com/adminsyspro/proxcenter-ui.git synced 2026-04-24 22:15:58 +03:00

[GH-ISSUE #87] [Bug]: VLAN view broken in inventory #135

New issue

Open

opened 2026-03-13 17:18:26 +03:00 by kerem · 5 comments

kerem commented

2026-03-13 17:18:26 +03:00

Owner

Originally created by @flpmonstro on GitHub (Mar 9, 2026).
Original GitHub issue: https://github.com/adminsyspro/proxcenter-ui/issues/87

Bug Description

When I try to view the VLAN in the inventory, I get this error:

MUI X: The Tree View component requires all items to have a unique id property. Alternatively, you can use the getItemId prop to specify a custom id for each item. Two items were provided with the same id in the items prop: "vm:cmmataiav000001mme26vxtez:pve-ha-01:qemu:111"

Steps to Reproduce

Inventory
Network
Untagged or the tree

Expected Behavior

Show the number of vlans in each node and the vlans .

Actual Behavior

ProxCenter Version

bedd4f5

Proxmox VE Version

8.4.16

Browser

Chrome and Firefox

Logs / Screenshots

No response

Originally created by @flpmonstro on GitHub (Mar 9, 2026). Original GitHub issue: https://github.com/adminsyspro/proxcenter-ui/issues/87 ### Bug Description When I try to view the VLAN in the inventory, I get this error: MUI X: The Tree View component requires all items to have a unique `id` property. Alternatively, you can use the `getItemId` prop to specify a custom id for each item. Two items were provided with the same id in the `items` prop: "vm:cmmataiav000001mme26vxtez:pve-ha-01:qemu:111" ### Steps to Reproduce 1. Inventory 2. Network 3. Untagged or the tree <img width="701" height="453" alt="Image" src="https://github.com/user-attachments/assets/1477b6f9-9e6d-41f0-a370-7790780d0885" /> ### Expected Behavior Show the number of vlans in each node and the vlans . ### Actual Behavior <img width="619" height="245" alt="Image" src="https://github.com/user-attachments/assets/bc4cb2c8-8d1e-4cfb-9518-3b2c91543c10" /> <img width="2377" height="471" alt="Image" src="https://github.com/user-attachments/assets/7f1e7dda-c8b6-40f9-a200-eed57c272b65" /> ### ProxCenter Version bedd4f5 ### Proxmox VE Version 8.4.16 ### Browser Chrome and Firefox ### Logs / Screenshots _No response_

kerem added the

bug

enhancement

feature-request

labels

2026-03-13 17:18:26 +03:00

kerem commented

2026-03-13 17:18:37 +03:00

Author

Owner

@adminsyspro commented on GitHub (Mar 9, 2026):

Thanks for reporting this! The issue was caused by duplicate itemId values in the MUI TreeView — when a VM has multiple network interfaces (e.g. on different VLANs or bridges), it appeared multiple times in the tree with the same ID.

Fixed in commit 675aff9: the TreeItem ID now includes the network interface name and VLAN tag, making each entry unique.

This fix will be available in the next build. Let us know if you still encounter the issue after updating!

@adminsyspro commented on GitHub (Mar 9, 2026): Thanks for reporting this! The issue was caused by duplicate `itemId` values in the MUI TreeView — when a VM has multiple network interfaces (e.g. on different VLANs or bridges), it appeared multiple times in the tree with the same ID. Fixed in commit 675aff9: the TreeItem ID now includes the network interface name and VLAN tag, making each entry unique. This fix will be available in the next build. Let us know if you still encounter the issue after updating!

kerem commented

2026-03-13 17:18:42 +03:00

Author

Owner

@flpmonstro commented on GitHub (Mar 9, 2026):

Hi everyone ,

Fixed the tree, but the number of VLANs in the node still isn't right.

@flpmonstro commented on GitHub (Mar 9, 2026): Hi everyone , Fixed the tree, but the number of VLANs in the node still isn't right. <img width="296" height="94" alt="Image" src="https://github.com/user-attachments/assets/3361240b-74f9-49a4-81a6-f2c81e66c6bd" />

kerem commented

2026-03-13 17:18:47 +03:00

Author

Owner

@adminsyspro commented on GitHub (Mar 10, 2026):

Thanks for the follow-up! Could you share a bit more about your network setup?

Specifically:

Are your VMs using VLAN tags on their network interfaces, or are they all on untagged bridges (e.g. vmbr0 without a tag parameter)?
What does a typical VM network config look like? (e.g. net0: virtio=...,bridge=vmbr0,tag=100 vs net0: virtio=...,bridge=vmbr0)

In the meantime, we've improved the node label in commit 833dc30 — it now shows the VM count alongside the VLAN count, and hides the "0 VLANs" label when all interfaces are untagged. This should give a more accurate picture of what's on each node.

@adminsyspro commented on GitHub (Mar 10, 2026): Thanks for the follow-up! Could you share a bit more about your network setup? Specifically: - Are your VMs using VLAN tags on their network interfaces, or are they all on untagged bridges (e.g. `vmbr0` without a `tag` parameter)? - What does a typical VM network config look like? (e.g. `net0: virtio=...,bridge=vmbr0,tag=100` vs `net0: virtio=...,bridge=vmbr0`) In the meantime, we've improved the node label in commit 833dc30 — it now shows the VM count alongside the VLAN count, and hides the "0 VLANs" label when all interfaces are untagged. This should give a more accurate picture of what's on each node.

kerem commented

2026-03-13 17:18:52 +03:00

Author

Owner

@flpmonstro commented on GitHub (Mar 10, 2026):

Hi guys !!

I don't have the tag applied directly to the VM interface. In my environment, I use SDN and apply the vnet to the bridge.

That's why I was confused... But I think this is important information. And it should be visible.

@flpmonstro commented on GitHub (Mar 10, 2026): Hi guys !! I don't have the tag applied directly to the VM interface. In my environment, I use SDN and apply the vnet to the bridge. That's why I was confused... But I think this is important information. And it should be visible.

kerem commented

2026-03-13 17:18:57 +03:00

Author

Owner

@adminsyspro commented on GitHub (Mar 10, 2026):

Thanks for the details! That makes sense — your VLANs are managed at the SDN level (vnets/zones) rather than as tags on VM interfaces, which is why they don't appear in the current network tree.

We don't support SDN mapping yet, but this is definitely something we want to integrate. We'll look into fetching vnet/zone data from the Proxmox SDN API to properly display the VLAN topology in your case.

I'll keep this issue open and update you when we have progress on SDN support. Thanks for helping us improve ProxCenter! 🙏

@adminsyspro commented on GitHub (Mar 10, 2026): Thanks for the details! That makes sense — your VLANs are managed at the SDN level (vnets/zones) rather than as tags on VM interfaces, which is why they don't appear in the current network tree. We don't support SDN mapping yet, but this is definitely something we want to integrate. We'll look into fetching vnet/zone data from the Proxmox SDN API to properly display the VLAN topology in your case. I'll keep this issue open and update you when we have progress on SDN support. Thanks for helping us improve ProxCenter! 🙏