[SOLVED] Web GUI not available after update to 7.2

[krawallovic]

Hello,

we updated last friday to proxmox-ve 7.2 and rebooted our server afterwards. After the reboot the web GUI was just blank. Some more reboots didn't help to bring the web GUI back to life.

So we tried the following things:

• apt --fix-broken install
  • as there was nothing to repair, nothing happened
• temporarily added the No-Subscription repository and updated the kernel to an even newer version
  • we have the enterprise repository enabled and took the 7.2 update files from there
  • after this the web GUI stayed blank, so we removed the No-Subscription repository
• apt install --reinstall proxmox-widget-toolkit
  • reinstallation worked, web GUI stayed blank
• apt install --reinstall pve-manager
  • reinstallation worked, web GUI stayed blank
• apt install --reinstall libjs-extjs
  • reinstallation worked, web GUI stayed blank

After some more troubleshooting, we saw an error in the Developer tools:


So i removed the '=' from the pvemanagerlib.js file:


After that, we restarted the pveproxy service and everything worked again as expected.

Is there some error in the update process? We did not edit this file in any way, so that we cannot see from where this character came from.

 

[spirit]

do you have a subscription license for the enteprise repo?

if not, did you have configured the non-subscription repository before update ?

what is the result of

#pveversion -v

?

 

[krawallovic]

do you have a subscription license for the enteprise repo?

if not, did you have configured the non-subscription repository before update ?

what is the result of

#pveversion -v

?

Subscription license:


The No-Subscription repository was added after the update to 7.2 (and the resulting blank wnb GUI). Then we only updated the kernel from there and removed the No-Subscription repository again.
The No-Subscription repository was active for a short time, but we don't know exactly what was possibly updated from there before adding the Enterprise repository.

pveversion -v:

 

[datschlatscher]

so that we cannot see from where this character came from.

It is supposed to be there. This is called a Logical AND assignment (&&=), your problem is most likely an out-of-date browser. The &&= parameter was added, for example, in Chromium version 85 and Firefox version 79

Could please tell me what Browser you are using and which version you are running on? You can find the version somewhere in the settings, usually in About.
If an old Browser version is actually at play here, you should update as soon as possible, as Browsers not just ship new features but also important security fixes with every new update!

 

[krawallovic]

Thank you! Indeed, this was the culprit!

We use Microsoft Edge in our environment and i thought that the automatic updater is going to always check for the latest version. Well, our environment is some kind of strict in terms of internet access, so... im going to update this old Edge (version 83) to the latest version and everything should be fine

 

[aliistif]

Hello,

we updated last friday to proxmox-ve 7.2 and rebooted our server afterwards. After the reboot the web GUI was just blank. Some more reboots didn't help to bring the web GUI back to life.

So we tried the following things:

• apt --fix-broken install
  • as there was nothing to repair, nothing happened
• temporarily added the No-Subscription repository and updated the kernel to an even newer version
  • we have the enterprise repository enabled and took the 7.2 update files from there
  • after this the web GUI stayed blank, so we removed the No-Subscription repository
• apt install --reinstall proxmox-widget-toolkit
  • reinstallation worked, web GUI stayed blank
• apt install --reinstall pve-manager
  • reinstallation worked, web GUI stayed blank
• apt install --reinstall libjs-extjs
  • reinstallation worked, web GUI stayed blank

After some more troubleshooting, we saw an error in the Developer tools:
View attachment 36711

So i removed the '=' from the pvemanagerlib.js file:
View attachment 36712

After that, we restarted the pveproxy service and everything worked again as expected.

Is there some error in the update process? We did not edit this file in any way, so that we cannot see from where this character came from.

how did you get to this screen can you share the command

 

[Matthias.]

If you mean the developer console, in your browser press F12 and click on "console"