noVNC window has HTML format issues and does not work

eddi1984

Active Member
Oct 8, 2014
46
0
26
Hi,

I have reinstalled proxmox4.4 (was on 5.3 but experienced the issues described here: https://forum.proxmox.com/threads/node-with-question-mark.41180/. 5.3 was a fresh install.).

Everything is working fine on 4.4, but noVNC does not open properly. Please see attached picture.

I installed 4.4 from iso and did an apt update/upgrade. After that, apt recommended to remove unused packages with apt-get autoremove. That's what I did.
Apt wanted to remove these packages:
Code:
ceph-fuse fonts-font-awesome libappconfig-perl libpve-http-server-perl libtemplate-perl proxmox-widget-toolkit
  pve-i18n

However, I am not sure, if this apt autoremove caused noVNC not to work anymore.

My version is:
pve-manager/4.4-1/eb2d6f1e (running kernel: 4.15.18-9-pve)

Any ideas on how to fix this? Btw, opening a KVM with spice viewer does work.

Cheers,

Eddi
 

Attachments

  • proxmox noVNC.png
    proxmox noVNC.png
    50.8 KB · Views: 9
Anybody any idea on how to solve this? Its very annoying to not having the console working.

Thanks.
 
did you already try to clear the browser cache ?
 
... libpve-http-server-perl ... proxmox-widget-toolkit pve-i18n
These 3 packages, which were automatically removed are necessary for PVE.
Try to install the meta-package `proxmox-ve`

Just for completeness sake: PVE 4.x is EOL since 6 Months (https://pve.proxmox.com/wiki/FAQ) and it does not receive any security updates!
 
These 3 packages, which were automatically removed are necessary for PVE.
Try to install the meta-package `proxmox-ve`

Just for completeness sake: PVE 4.x is EOL since 6 Months (https://pve.proxmox.com/wiki/FAQ) and it does not receive any security updates!

I forced the re-installation of proxmox-ve and the 3 separate packages you pointed out. The installation worked without a hiccup, but the noVNC still is not working.

I am aware that 4.4 is EOL, but after upgrading my original 4.4 install to 5.3, I experienced the issues described in this thread: https://forum.proxmox.com/threads/node-with-question-mark.41180/page-3
That is the reason why I installed 4.4 again, however, I am experiencing the same issue again with my fresh install of 4.4. I am thinking of going back to 4.0 unless the issue will be resolved soon by an update.

Thanks.
 
pve-manager/4.4-1/eb2d6f1e (running kernel: 4.15.18-9-pve)
how did you do this? did you downgrade to the 4.x packages on a 5.x system? if yes, this will not properly work, as
4.x should only be installed on debian jessie, whereas 5.x is based on stretch

it may seem that it works, but i guess there will be some subtle error and failures

the problem you linked in your first post is only a symptom of some other problem (not a bug) so simply changing version will not help at all