4.4: Error opening console

[whiterabbit]

Hi.
I just updated to pve 4.4 yesterday.
(pve-manager/4.4-1/eb2d6f1e (running kernel: 4.4.21-1-pve))

There was also an update of my firefox (here: Ubuntu 14.04. LTS with ff 50.1.0+build2-0ubuntu0.14.04.1).
Today I wanted to open a console of a VM but it doesn't work any more.
The console-windows opens but there's a red error-message:

Unable to create RFB client -- TypeError: ERROR.captureStackTrace is not a function

Is this a proxmox or a firefox problem? What to do? Of course I already cleared the browser cache...
Thanks.

 

[resoli]

Same error here. We found it related to the presence of anti-tracking/anti-ad extension, "privacy badger" and "adblock plus" in particular. Note that whitelisting the specific pve GUI site is not sufficient, the problem disappears only disabling the extension globally.
In Privacy Badger case there is impact also in correctly displaying the gui (no live graphs for cpu, io, ecc.).

 

[whiterabbit]

Wow -- you were absolutely right! I'd never have guessed that!
It was Privacy Badger -- but the problem must be new as it worked with pve 4.3 without any problems so far!
So: Is this a bug or what's the problem behind it?

 

[resoli]

I think is the combined effect of firefox (50.1 currently) upgrade with ad/tracking block extension. The 4.4 version of pve does not plays a primary role; we have some 4.3 in production, and the problem is exactly the same (exception in noVNC, no live graphs in the GUI)

 

[steba]

FYI, I'm experiencing the same problem with pve 3.4-15.

 

[jesusjimenez]

I confirm it is caused by Privacy Badger...
And no, it is not new as I have 4.3 installed and PB was installed maybe two days ago. So maybe is it some new version of PB?

 

[clickwir]

FWIW, I was having problems with the initial Proxmox 5.1 page not loading at all. Just blank. Disabled all my addons and made no difference.

Found I had dom.storage set to FALSE and that appears to be something Proxmox needs unfortunately. Enabled all my addons, restarted FF 57.0.1 with dom.stroage enabled and it works ok now.