[SOLVED] Setuped a cluster with 3 nodes - Spice-Remoteviewer works only on one node. xterm.js only on ipv4

for that i sent a different patch (simultaneously with the spiceterm patch; both of which got applied) : https://pve.proxmox.com/pipermail/pve-devel/2019-March/036160.html
Tested, but not work. Here is the error message:
Code:
Authentication failed: '500 Can't connect to 127.0.0.1:85'
TASK ERROR: command '/usr/bin/termproxy 5900 --path /vms/124 --perm VM.Console -- /usr/bin/ssh -e none -t 2001:470:2e0e:552:ec4:7afe:fcea:c825 -- /usr/bin/dtach -A /var/run/dtach/vzctlconsole124 -r winch -z lxc-console -n 124 -e -1' failed: exit code 22
 
Not weird, because it can't work with this entry. There is an 127.0.0.1 available if you use ipv6 only. And if you do an ping you get this back:

i belive you misunderstood me:

you had the line '127.0.0.1 localhost' in your etc hosts so 'localhost' resolves to '127.0.0.1' which you also had in your 'ip addr' output

now a process listens on 'localhost' (spiceterm in that case with my new patch) which really means now '127.0.0.1',
spiceproxy connects to 'localhost' which again resolves to 127.0.0.1, so this should have worked

Tested, but not work. Here is the error message:
weird, i tested with ipv4 only, ipv4+ipv6 and ipv6 only setups, all worked with my patches

can you try to do the following:

listen on 'localhost' with netcat on any port
Code:
nc -l -p 7000 -s localhost

and connect from a different terminal on the same host to that via localhost

Code:
nc localhost 7000

after that any input written on either terminal should appear on the other

this should always work when localhost resolves to an ip that the host has (eg. 127.0.0.1 or ::1)

(that is basically what we do with spiceterm and xtermjs, but through the api/pveproxy/spiceproxy/websocket etc)
 
Thanks a lot for the Info and the patches :):cool: It works now. My fault, i setuped the patch only on one host for testing, on the targethost. But it is important on the sourcehost too. Here my own howto in German. When can one expect the implementation of the patches?
 
. My fault, i setuped the patch only on one host for testing, on the targethost
yeah in that case it was necessary to install it on the source node (since there happens the connection magic)

When can one expect the implementation of the patches?
they are already applied and should be delivered with the next rounds of updates
 
  • Like
Reactions: fireon