Safari Only - PVE 8.2.4 - NoVNC Console Error

[Ramalama]

Hi, something changed either in PVE 8.2.4 or Safari got today an Update.
ISSUE: NoVNC Console doesn't work! xTerm Console works without issues.

-> Firefox: no Issues
-> Edge: no Issues
-> Chrome: Didnt tested, sorry
-> Safari: Doesn't work since Today.

I have like 8 PVE Servers and as Stupid as i am, i updated them all to 8.2.4 (Kernel 6.8.8) 2 days ago and yesterday. So i don't even have any Server left with PVE 8.2.2....

Issue:

Scrollbar test exception: TypeError: null is not an object (evaluating 'document.body.appendChild')
TypeError: globalThis.requestIdleCallback is not a function. (In 'globalThis.requestIdleCallback(this.processMutations, { timeout: 500 })', 'globalThis.requestIdleCallback' is undefined)

Should we Open an Issue on Github of NoVNC?
Cheers

 

[Reoccur0274]

I found this issue through Google.

Today, after updating Bitwarden in the App Store, I encountered the same problem. Checking the error messages in the console output revealed that it was caused by Bitwarden's auto-fill module, which leads to browser tabs freezing.

It appears to be a bug in the latest version of Bitwarden.

safari-web-extension://xxx/content/bootstrap-autofill-overlay.js

TypeError: globalThis.requestIdleCallback is not a function. (In 'globalThis.requestIdleCallback(this.processMutations, { timeout: 500 })', 'globalThis.requestIdleCallback' is undefined)

 

[Ramalama]

I found this issue through Google.

Today, after updating Bitwarden in the App Store, I encountered the same problem. Checking the error messages in the console output revealed that it was caused by Bitwarden's auto-fill module, which leads to browser tabs freezing.

It appears to be a bug in the latest version of Bitwarden.

safari-web-extension://xxx/content/bootstrap-autofill-overlay.js

TypeError: globalThis.requestIdleCallback is not a function. (In 'globalThis.requestIdleCallback(this.processMutations, { timeout: 500 })', 'globalThis.requestIdleCallback' is undefined)

You're amazing, thanks!
Now we need only a fix lol xD

 

[Reginard]

I have the same issue on Safari. The latest Safari Technology Preview works fine though.

 

[logopk]

Ooops they did it again

Today with 2025.1.4 and Safari 18.3 (20620.2.4.11.5), PVE 8.3.3

Good that there was this Post! Thank You

[Error] Scrollbar test exception: TypeError: null is not an object (evaluating 'document.body.appendChild')

[Error] TypeError: undefined is not an object (evaluating 'this.domQueryService')
    checkPageContainsShadowDom (bootstrap-legacy-autofill-overlay.js:6247)

 

[clyra]

You're amazing, thanks!
Now we need only a fix lol xD

You may already found this, but you can disable the bitwarden extension for the proxmox address.

 

[anderl1969]

You may already found this, but you can disable the bitwarden extension for the proxmox address.

But what if your proxmox password is stored in Bitwarden
So I have permanently to switch between allowing and disallowing... as a workaround kind of okay, but on the long term annoying. Does anyone know if the bug is reported to Bitwarden and if there is anyone working on it?

Before I forget: thanks to Reoccur0274 for his investigations

 

[jiveman]

You may already found this, but you can disable the bitwarden extension for the proxmox address.

man, would have taken me a while to figure this out. Thanks!
Seems to continue to error even when disabling it for the site for me (Mac/Safari). Your experience?

 

[anderl1969]

Discovered today that the noVNC console now works within Safari even with the Bitwarden extension active. As there was a Bitwarden update yesterday, I suppose this solved the issue. Anyone who can confirm?

 

[jiveman]

Discovered today that the noVNC console now works within Safari even with the Bitwarden extension active. As there was a Bitwarden update yesterday, I suppose this solved the issue. Anyone who can confirm?

Updated bitwarden via app store first, then checked already open proxmox tabs. No change. However did a private browser session and am not seeing it there. Maybe something cached on my main browser instance. Interestingly it seems only on my VM, not affecting my LXCs.

I opened another private browser and am not seeing the vnc error in the VMs either so I do think my issue is a caching issue.