https://www.reddit.com/r/Proxmox/s/KrmvrSdtmR
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
FWIW - identical proble, but this is going form 8.4 to 8.4.13 upgrade from CLI using these steps:
apt-cache policy pve-manager
apt install pve-manager=8.4.13
apt dist-upgrade
apt-mark hold proxmox-ve pve-manager
apt dist-upgrade
rebooted and now I have <span> tags everywhere. Single node - no cluster.
apt-cache policy pve-manager
apt install pve-manager=8.4.13
apt dist-upgrade
apt-mark hold proxmox-ve pve-manager
apt dist-upgrade
rebooted and now I have <span> tags everywhere. Single node - no cluster.
we were already 9.1 out of the gate so I was a bit surprised we had this issue, but mentioned above, a host rebuild fix it. We run FC storage and have a 3 node test cluster, so it didn't take long to get back into working again.
@Hank42, have you installed helper scripts on your system at any point?
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
No helper scripts - fresh install of 8.4 - > upgrade to 8.4.13 (adding to an existing cluster is the goal).
Hoping this helps someone else as I found the root cause and fixed my issue . To resolve the issue, I did a force (re)install of proxmox-widget-toolkit to my specific version.
Apparently, specifying the version upgrade :
apt install pve-manager=8.4.13
Followed by the :
apt dist-upgrade
caused the latest proxmox-widget-toolkit (4.3.16) to to be installed/upgraded - which is not in sync with pve-manager 8.4.13
Forcing the version on the toolkit fixed my issue
apt install --reinstall pve-manager=8.4.13 proxmox-widget-toolkit=4.3.13
(be sure to flush your browser cache to avoid ghosts)
Hoping this helps someone else as I found the root cause and fixed my issue . To resolve the issue, I did a force (re)install of proxmox-widget-toolkit to my specific version.
Apparently, specifying the version upgrade :
apt install pve-manager=8.4.13
Followed by the :
apt dist-upgrade
caused the latest proxmox-widget-toolkit (4.3.16) to to be installed/upgraded - which is not in sync with pve-manager 8.4.13
Forcing the version on the toolkit fixed my issue
apt install --reinstall pve-manager=8.4.13 proxmox-widget-toolkit=4.3.13
(be sure to flush your browser cache to avoid ghosts)
Last edited:
Thank you for sharing, @Hank42.
In your post #25, it stood out to me that you mentioned holding some packages while upgrading others. In general, this is not a good idea. The various components of the system are interconnected, and partial upgrades can easily lead to inconsistencies. Unless specifically directed by PVE support, I would not recommend doing that.
Is it possible that you held other packages in the past? Reviewing the full upgrade output from your very first attempt might reveal something interesting. However, given the unusual upgrade approach you described, it is quite possible that the issue is isolated to your system, and further debugging is not a good time-investment.
So far, I've seen three reports of the <span> issue. The user on Reddit started their report by mentioning that helper scripts had been installed. Your report referenced a “non-standard” upgrade procedure. While @mikewich’s report did not show anything obviously suspicious, it is worth keeping the broader context in mind: thousands of users upgrade their Proxmox Virtual Environment systems regularly, tens of thousands reboot frequently, and hundreds of thousands of installations are running worldwide. Yet only three reports of this issue have surfaced so far, and two of them already show potential environmental causes.
If additional reports appear, it would be very helpful to include a full system overview: package versions, APT configuration, upgrade history, and any customizations.
Cheers.
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
In your post #25, it stood out to me that you mentioned holding some packages while upgrading others. In general, this is not a good idea. The various components of the system are interconnected, and partial upgrades can easily lead to inconsistencies. Unless specifically directed by PVE support, I would not recommend doing that.
Is it possible that you held other packages in the past? Reviewing the full upgrade output from your very first attempt might reveal something interesting. However, given the unusual upgrade approach you described, it is quite possible that the issue is isolated to your system, and further debugging is not a good time-investment.
So far, I've seen three reports of the <span> issue. The user on Reddit started their report by mentioning that helper scripts had been installed. Your report referenced a “non-standard” upgrade procedure. While @mikewich’s report did not show anything obviously suspicious, it is worth keeping the broader context in mind: thousands of users upgrade their Proxmox Virtual Environment systems regularly, tens of thousands reboot frequently, and hundreds of thousands of installations are running worldwide. Yet only three reports of this issue have surfaced so far, and two of them already show potential environmental causes.
If additional reports appear, it would be very helpful to include a full system overview: package versions, APT configuration, upgrade history, and any customizations.
Cheers.
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Last edited:
@Hank42 solved this on a different version. Me also encountered this <span> bug in the resource tree with PVE 9.1.6. The fix is to downgrade proxmox-widget-toolkit to the version that actually matched pve-manager 9.1.6 at release time:
Then do a browser refresh (Ctrl+Shift+R) or start a new private window.
Root cause: proxmox-widget-toolkit 5.1.6 (released Feb 18, 2026) introduced renderer: Ext.htmlEncode as the default renderer for all grid columns. Since Ext.tree.Column inherits from Ext.grid.column.Column, the resource tree's text column now HTML-encodes node names - turning <span>hostname</span> into literal visible text instead of rendered HTML.
The pve-manager 9.1.6 was released on Feb 12, six days before this breaking change landed. The subsequent 5.1.7 and 5.1.8 releases fixed some regressions but did not address the tree column. Pinning back to 5.1.5 (the version compatible with pve-manager 9.1.6) resolves it.
Bash:
sudo apt install --reinstall pve-manager=9.1.6 proxmox-widget-toolkit=5.1.5 --allow-downgrades
sudo systemctl restart pveproxyThen do a browser refresh (Ctrl+Shift+R) or start a new private window.
Root cause: proxmox-widget-toolkit 5.1.6 (released Feb 18, 2026) introduced renderer: Ext.htmlEncode as the default renderer for all grid columns. Since Ext.tree.Column inherits from Ext.grid.column.Column, the resource tree's text column now HTML-encodes node names - turning <span>hostname</span> into literal visible text instead of rendered HTML.
The pve-manager 9.1.6 was released on Feb 12, six days before this breaking change landed. The subsequent 5.1.7 and 5.1.8 releases fixed some regressions but did not address the tree column. Pinning back to 5.1.5 (the version compatible with pve-manager 9.1.6) resolves it.
I came across this and thought I'd provide a little info, cause I have the exact same problem.
For me this behaviour started immediately after I ran the Unifi installation script: https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/unifi-os-server.sh
Hope this helps or maybe makes it recreatable.
For me this behaviour started immediately after I ran the Unifi installation script: https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/unifi-os-server.sh
Hope this helps or maybe makes it recreatable.
Thank you for adding this very concrete data point.
Please report this to the community-scripts (that are not provided or supported by Proxmox) issues page. The people there know the script and might be able to pinpoint and fix the problem.
Found this report. It helped me fix the issue. Thanks: https://github.com/community-scripts/ProxmoxVE/issues/12837