[SOLVED] WebUI console xterm.js not working.

liv

New Member
Jun 21, 2021
3
2
3
Greetings!

I just recently bought my first server and have now made my first attempts to install PVE. I have now completed an installation I feel satisfied with, but there is just this one small issue I'd like to sort out.

When I launch the console in the WebUI it shows an error: "Connection Failed (Code: 1006)" and this is what I could find regarding to it:
Code:
TASK ERROR: command '/usr/bin/termproxy 5900 --path /nodes/mymachine --perm Sys.Console -- /bin/login -f root' failed: exit code 1

However, if I click on the little ">_Shell" -dropdown menu, I can choose SPICE and noVNC and both options work fine, except that they don't work "inside" of the WebUI which I would prefer.

I have tested this with:
  • multiple browsers (Brave, Firefox) on multiple (linux) machines (also tried) clearing cache inbetween changed settings etc)
  • tried to change the "Console Viewer" default, but it did not do anything
  • restarting (physical machine and services)
  • reinstalling pve-manager (with --purge)
  • updating (everything is up to date)
My installation itself was somewhat different from the default, since I first installed Debian (netinstall) and did some custom partitioning (for encryption purposes), then installed PVE according to the wiki. Could this issue maybe related to something that has to do with my initial debian setup?

Thanks in advance.
/ Liv
 
Hello,

Have you tried to update the PVE certificates pvecm updatecerts --force? or maybe there is a firewall or proxy?

Could you post the full output of pveversion -v as well
 
Updating the PVE certificates did not do anything, neither did stopping the firewall. I did not configure any proxy either as far as I know.

Here is the output:

Code:
proxmox-ve: 6.4-1 (running kernel: 5.4.119-1-pve)
pve-manager: 6.4-8 (running version: 6.4-8/185e14db)
pve-kernel-5.4: 6.4-3
pve-kernel-helper: 6.4-3
pve-kernel-5.4.119-1-pve: 5.4.119-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.1.2-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
libjs-extjs: 6.0.1-10
libknet1: 1.20-pve1
libproxmox-acme-perl: 1.1.0
libproxmox-backup-qemu0: 1.0.3-1
libpve-access-control: 6.4-3
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 6.4-3
libpve-guest-common-perl: 3.1-5
libpve-http-server-perl: 3.2-3
libpve-storage-perl: 6.4-1
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.6-2
lxcfs: 4.0.6-pve1
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.1.10-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.5-6
pve-cluster: 6.4-1
pve-container: 3.3-5
pve-docs: 6.4-2
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-4
pve-firmware: 3.2-4
pve-ha-manager: 3.1-1
pve-i18n: 2.3-1
pve-qemu-kvm: 5.2.0-6
pve-xtermjs: 4.7.0-3
qemu-server: 6.4-2
smartmontools: 7.2-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 2.0.4-pve1
 
I installed PVE in a VM on my PC and started comparing some configs from the WebUI and found that my /etc/hosts was misconfigured. After fixing it, everything worked like a charm!

/close thread
 
  • Like
Reactions: lexxxel and Moayad
Thank you so much! I ran into the same error. In my hosts file '127.0.0.1 localhost' was missing somehow. Adding that line fixed it for me, too.
 

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!

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!