Chrome display issue (Web-GUI) since a few days

S

SimonB

Renowned Member
Aug 15, 2016
27
0
66
44
Hi there,

since a few days, I have a problem with chrome (55.0.2883.75 m) using the proxomx gui (4.3-12/6894c9d9) latest updates installed. Firefox (50.0.2) works fine.


Symptom: After selecting a server (in the most left panel), the navigation panel and the main panel disappear. Going back to the Node or Datacenter (in the most left panel view), the middle panel appears, but the navigation panel is still missing (until I logout and login again).


Does anybody else has the same/similar problem or an idea what the reason for this could be?


Thank you in advance,

Simon
 
SimonB said:
After selecting a server (in the most left panel), the navigation panel and the main panel disappear.
Click to expand...
can you maybe post a screenshot of this?

can you maye open the javascript console (ctrl + shift + i) and copy/paste if there are any errors/warnings?
 
Hi dcsapak,

(how) can I send you a PN, since I do not want to publish the whole thing here.

But a short teaser: in ctrl-shift-i mode when clicking on one of my servers system throws an:

Uncaught DOMException: Blocked a frame with origin "https://xxx.xxx.de:8006" from accessing a cross-origin frame.
at g.applyStyle ...

I would feel more comfortable not to post the whole stacktrace here.

Best regards,
Simon
 
Just wondering if this ever got resolved, as the same issue has arisen for me. The issue is that occasionally it will load correctly, but most of the time wont.

Virtual Environment 4.4-1/eb2d6f1e, Chrome 58.

Works fine in Firefox


charts.js:1 Uncaught DOMException: Blocked a frame with origin "https://homeserver.lan:8006" from accessing a cross-origin frame. at g.applyStyle (https://homeserver.lan:8006/pve2/ext6/charts.js:1:192926) at g [as setStyle] (https://homeserver.lan:8006/pve2/ext6/ext-all.js:22:78577) at g.updateTheme (https://homeserver.lan:8006/pve2/ext6/charts.js:1:193397) at g.updateTheme (https://homeserver.lan:8006/pve2/ext6/charts.js:1:205828) at g [as setTheme] (https://homeserver.lan:8006/pve2/ext6/ext-all.js:22:78634) at Ext.Configurator.configure (https://homeserver.lan:8006/pve2/ext6/ext-all.js:22:82320) at g.initConfig (https://homeserver.lan:8006/pve2/ext6/ext-all.js:22:89103) at g.constructor (https://homeserver.lan:8006/pve2/ext6/ext-all.js:22:495627) at g.callParent (https://homeserver.lan:8006/pve2/ext6/ext-all.js:22:88720) at new constructor (https://homeserver.lan:8006/pve2/ext6/charts.js:1:199076)
 
Hi Iteration,

it has been a long time since my post, but I think after an update (proxmox or chrome or both) it worked fo a while and then stopped working for me again

I assume, that it could have something to do with my Norton Chrome Extension, blocking some code. But since I did not have the time to investigate/debug this topic, I just started to use firefox for my proxmox (where I do not have any norton extension installed).

Do you use Norton extension or any other security extension? I could imagine, that it is blocking some code. But this is just an unproved assumption.

Greets,
Simon
 
EvertM said:
I'm experiencing the same issue, with Chrome 59:
Click to expand...
do you have any chrome extensions activated? maybe try without those
or try flushing the browser cache
 
  • Like
Reactions: VDNKH
I've tested the newest proxmox (as of this post) with Chrome 63.0.3239.86 (Official Build) beta (64-bit) on Windows, Linux, and ChromeOS (all with and without extensions and even incognito mode). I'm still having this issue. I have replaced /etc/pve/pve-root-ca.pem, /etc/pve/priv/pve-root-ca.key, /etc/pve/priv/pve-root-ca.srl, /etc/pve/local/pve-ssl.pem, and /etc/pve/local/pve-ssl.key with my own CA and node certs (single-node setup). I added my self-signed CA to both Chrome and Firefox. Chrome complains about cross-origin frames but Firefox doesn't. Everything seems to work as expected until I click on a VM, then the UI is broken everywhere. Clicking on Datacenter and refreshing fixes the UI until I click on a VM again.

Stacktrace is below:

charts.js:1 Uncaught DOMException: Blocked a frame with origin "https://proxmox.mydomain.com:8006" from accessing a cross-origin frame.
at g.applyStyle (https://proxmox.mydomain.com:8006/pve2/ext6/charts.js:1:192927)
at g [as setStyle] (https://proxmox.mydomain.com:8006/pve2/ext6/ext-all.js:22:78577)
at g.updateTheme (https://proxmox.mydomain.com:8006/pve2/ext6/charts.js:1:193397)
at g.updateTheme (https://proxmox.mydomain.com:8006/pve2/ext6/charts.js:1:205828)
at g [as setTheme] (https://proxmox.mydomain.com:8006/pve2/ext6/ext-all.js:22:78634)
at Ext.Configurator.configure (https://proxmox.mydomain.com:8006/pve2/ext6/ext-all.js:22:82320)
at g.initConfig (https://proxmox.mydomain.com:8006/pve2/ext6/ext-all.js:22:89103)
at g.constructor (https://proxmox.mydomain.com:8006/pve2/ext6/ext-all.js:22:495627)
at g.callParent (https://proxmox.mydomain.com:8006/pve2/ext6/ext-all.js:22:88720)
at g.constructor (https://proxmox.mydomain.com:8006/pve2/ext6/charts.js:1:199076)

Let me know if there's any more info that I could provide.
 
mjwhitta said:
Let me know if there's any more info that I could provide.
Click to expand...
you could start pveproxy in debug mode (stop pveproxy and start it again with -debug as parameter; this will run in the foreground)
and reload the site and post the error message

starting pveproxy in debug mode uses the non-minified versions of the js files
 
Here's the new stacktrace:

charts-debug.js:18770 Uncaught DOMException: Blocked a frame with origin "https://proxmox.mydomain.com:8006" from accessing a cross-origin frame.
at constructor.applyStyle (https://proxmox.mydomain.com:8006/pve2/ext6/charts-debug.js:18770:24)
at constructor.setter [as setStyle] (https://proxmox.mydomain.com:8006/pve2/ext6/ext-all-debug.js:10279:57)
at constructor.updateTheme (https://proxmox.mydomain.com:8006/pve2/ext6/charts-debug.js:18806:38)
at constructor.updateTheme (https://proxmox.mydomain.com:8006/pve2/ext6/charts-debug.js:20123:21)
at constructor.setter [as setTheme] (https://proxmox.mydomain.com:8006/pve2/ext6/ext-all-debug.js:10285:39)
at Ext.Configurator.configure (https://proxmox.mydomain.com:8006/pve2/ext6/ext-all-debug.js:10868:40)
at constructor.initConfig (https://proxmox.mydomain.com:8006/pve2/ext6/ext-all-debug.js:12271:17)
at constructor (https://proxmox.mydomain.com:8006/pve2/ext6/ext-all-debug.js:63907:12)
at constructor.callParent (https://proxmox.mydomain.com:8006/pve2/ext6/ext-all-debug.js:12118:32)
at constructor (https://proxmox.mydomain.com:8006/pve2/ext6/charts-debug.js:19598:12)

And here's the output from pveproxy:

28178: ACCEPT FH10 CONN1
28179: ACCEPT FH10 CONN1
close connection AnyEvent::Handle=HASH(0x55ae31fe73c8)
28178: CLOSE FH10 CONN0
28178: ACCEPT FH10 CONN1
close connection AnyEvent::Handle=HASH(0x55ae31fe73c8)
28179: CLOSE FH10 CONN0
 
i understand that you want to anonymize the output (so you replace your domain with proxmox.mydomain.com)
are all instances of the url in the output the same? are you behind a proxy or is the pve instance behind a reverse proxy?

the error does not make sense, because it does not access something from another domain
 
=) I can assure you that all instances are the same, and I'm not using any proxies of any sort. I agree that the error makes no sense. I was hoping someone here would understand better. At first I thought it was a cert issue as my self-signed CA wasn't being trusted. Turned out that my node cert needed a Subject Alternative Name. That fixed all my issues other than this cross-origin thingy. My best guess at this point is that I used Name.com to point proxmox.mydomain.com to my internal IP (192.168.1.181). However, if I run "hostname -f" on the proxmox server, it returns proxmox.lfytina1.metronetinc.com which may be causing this?
 
can you look on the 'network' tab of the chrome developer tools and check if the domains of the xhr requests are the same as the domain you entered? (they should, just to be sure)
 
All of the xhr requests look to go to my domain. I also modified /etc/hosts to contain "proxmox.mydomain.com" instead of just "proxmox". After rebooting, "hostname -f" behaves as expected but the error still persists so that rules out my best guess.
 
I just figured it out! Turns out it's a 1d10t error... I disabled all (or so I thought) extensions. Looks like I somehow missed the checkbox for cVim and now that it's disabled everything works. I figured this out by looking at the sources tab in chrome developer tools. There was only one domain (mine) but there was a second iframe on the page that was hidden. Apologies for wasting anyone's time but I'm posting this here so others remember to not make stupid mistakes like I do.

Edit: It's still not clear why this only happened when viewing the VM details page.
 
Just wanted to say, over a year later and was having this issue. Lo and behold, I'm using the same extension as OP. I disabled cVim and it works fine now.
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back