WebUI problem after migration pbs 3 to 4

[CyberCraft13]

Hello,
After migrating my PBS3 server to 4 I found myself with a webui display problem, that is to say that the page is displayed in black.
When putting the debug on the browser I have the following problems:

proxmoxlib.js:52 Uncaught ReferenceError: ngettext is not defined    at proxmoxlib.js:52:23
proxmox-backup-gui.js:549 Starting Backup Server GUI
proxmox-backup-gui.js:564 Uncaught TypeError: Cannot read properties of undefined (reading 'noText')    at proxmox-backup-gui.js:564:31

Any ideas ?
Thanks

 

[sterzy]

Are or were you using a specific language before? If so which one? Also does the problem persist after reloading the page with CTRL+SHIFT+R?

 

[CyberCraft13]

thanks for the quick response
I was in English on the webui.
I tried with brave and firefox browsers, even after clearing the cache
I'm on MacOS, but I also tried on Windows with brave, firefox and edge by clearing the cache.
I didn't specify it in the first post, but everything works on the backup service side.
I only have problems with the webui

 

[sterzy]

Can you post the output of the following command: proxmox-backup-manager versions --verbose. Thanks!

 

[CyberCraft13]

here is the configuration :

root@pbs-bdn-1:~# proxmox-backup-manager versions --verbose
proxmox-backup                      3.4.0        running kernel: 6.14.8-2-pve
proxmox-backup-server               3.4.4-1      running version: 3.4.4
proxmox-kernel-helper               9.0.3
proxmox-kernel-6.14.8-2-pve-signed  6.14.8-2
proxmox-kernel-6.14                 6.14.8-2
proxmox-kernel-6.8.12-13-pve-signed 6.8.12-13
proxmox-kernel-6.8                  6.8.12-13
proxmox-kernel-6.8.4-2-pve-signed   6.8.4-2
ifupdown2                           3.3.0-1+pmx9
libjs-extjs                         7.0.0-5
proxmox-backup-docs                 3.4.4-1
proxmox-backup-client               4.0.14-1
proxmox-mail-forward                1.0.2
proxmox-mini-journalreader          1.6
proxmox-offline-mirror-helper       0.7.0
proxmox-widget-toolkit              5.0.5
pve-xtermjs                         5.5.0-2
smartmontools                       7.4-pve1
zfsutils-linux                      2.3.3-pve1

Thanks

 

[sterzy]

proxmox-backup 3.4.0 running kernel: 6.14.8-2-pve proxmox-backup-server 3.4.4-1 running version: 3.4.4

That does not look like PBS 4, you are still running PBS 3.4. Are you sure you followed the upgrade guide correctly [1]? What does apt policy say?

[1]: https://pbs.proxmox.com/wiki/Upgrade_from_3_to_4

 

[CyberCraft13]

indeed it looks like I stayed on the old pbs version with debian 13

root@pbs-bdn-1:~# apt policy
Package files:
 100 /var/lib/dpkg/status
     release a=now
 500 https://packages.wazuh.com/4.x/apt stable/main amd64 Packages
     release o=4.x/apt stable,a=stable,n=stable,l=4.x/apt stable,c=main,b=amd64
     origin packages.wazuh.com
 500 http://download.proxmox.com/debian/pve trixie/pve-no-subscription amd64 Packages
     release o=Proxmox,a=stable,n=trixie,l=Proxmox Debian Repository,c=pve-no-subscription,b=amd64
     origin download.proxmox.com
 500 http://security.debian.org/debian-security trixie-security/main amd64 Packages
     release v=13,o=Debian,a=stable-security,n=trixie-security,l=Debian-Security,c=main,b=amd64
     origin security.debian.org
 500 http://deb.debian.org/debian trixie-updates/main amd64 Packages
     release v=13-updates,o=Debian,a=stable-updates,n=trixie-updates,l=Debian,c=main,b=amd64
     origin deb.debian.org
 500 http://deb.debian.org/debian trixie/non-free-firmware amd64 Packages
     release v=13.0,o=Debian,a=stable,n=trixie,l=Debian,c=non-free-firmware,b=amd64
     origin deb.debian.org
 500 http://deb.debian.org/debian trixie/main amd64 Packages
     release v=13.0,o=Debian,a=stable,n=trixie,l=Debian,c=main,b=amd64
     origin deb.debian.org
Pinned packages:

 

[sterzy]

Interesting, what does apt show proxmox-backup -a report? Also what does the packages.wazuh.com repository provide?

 

[CyberCraft13]

root@pbs-bdn-1:~# apt show proxmox-backup -a
Package: proxmox-backup
Version: 3.4.0
Status: install ok installed
Priority: optional
Section: admin
Maintainer: Proxmox Support Team <support@proxmox.com>
Installed-Size: 18.4 kB
Depends: proxmox-archive-keyring, proxmox-backup-client, proxmox-backup-server (>= 3.2~), proxmox-default-kernel, proxmox-kernel-helper (>= 8.0.3), systemd-sysv
Download-Size: unknown
APT-Manual-Installed: yes
APT-Sources: /var/lib/dpkg/status
Description: Proxmox Backup Server meta package
 This is a meta package which will install everything needed to run a
 Proxmox Backup server. This package also depends on the latest
 available Proxmox kernel.

WAZUH provides open source XDR/SIEM :

root@pbs-bdn-1:~# cat /etc/apt/sources.list.d/wazuh.list
deb [signed-by=/usr/share/keyrings/wazuh.gpg] https://packages.wazuh.com/4.x/apt/ stable main

 

[sterzy]

Ah sorry i missed that before, but you only seem to have Proxmox VE repository installed, not a Proxmox Backup Server one. Install it with the following command:

cat > /etc/apt/sources.list.d/proxmox.sources << EOF
Types: deb
URIs: http://download.proxmox.com/debian/pbs
Suites: trixie
Components: pbs-no-subscription
Signed-By: /usr/share/keyrings/proxmox-archive-keyring.gpg
EOF

Then run apt update and apt dist-upgrade after.

 

[CyberCraft13]

You rock !!
sorry, I did the PVE updates at the same time...

Many Thanks

 

[sterzy]

sorry, I did the PVE updates at the same time...

No problem, if your issue has been resolved, please mark this thread as “Solved” by clicking the “Edit Thread” button on top and adding the “Solved” prefix. Thanks!

 

[g4rb4g3]

I just had a very similar issue, followed the upgrade 3 to 4 upgrade wiki and after a restart no more ui

For me it turned out that this part of the instructions was off

Update all repository entries to Trixie:

sed -i 's/bookworm/trixie/g' /etc/apt/sources.list

sources.list had only a single line comment that I checked only after the failed update ​

cat sources.list
# See /etc/apt/sources.list.d/debian.sources

running sed on the proper debian.sources and apt again fixed it ​

 

[sterzy]

running sed on the proper debian.sources and apt again fixed it

Good point, I guess some bookworm based installations have already switched to the new deb822 format. In that case you need to adapt the .sources instead. However, running apt update and then apt policy should always show you the currently configured repositories. So checking that, especially during a release that switches how repositories are configured, makes a lot of sense. I'll check if we can make the upgrade guides a bit more explicit in terms of what repositories should be configured before actually running apt dist-upgrade.