wofferl / proxmox-backup-arm64

Script for building Proxmox Backup Server 3.x (Bookworm) for Armbian64
151 stars 12 forks source link

PBS 2.3-3 Shell Connection failed (Code 1006) #27

Closed Leo-wq closed 1 year ago

Leo-wq commented 1 year ago

Hello, I am now running PBS on a RockPro64 with Linux 5.10.0-21-arm64 #1 SMP Debian 5.10.162-1.

So far everything works fine, except that I can't open the shell. the above error always comes up... any clues where I could start?

wofferl commented 1 year ago

Have you installed the pve-xtermjs packet? (see #25)

Leo-wq commented 1 year ago

yes, all packages listed in the guide were installed, including pve-xtermjs_4.16.0-1_arm64.deb.

wofferl commented 1 year ago

Then it may be a problem with the websocket request.

wss://ip:8007/api2/json/nodes/localhost/vncwebsocket

Can you check your browsers debug console, if the request is blocked or has an error?

Which browser do you use? Do you use a proxy?

Leo-wq commented 1 year ago

this is what appears:

parameter verification errors

parameter 'port': parameter is missing and it is not optional.
parameter 'vncticket': parameter is missing and it is not optional.

i tried with Edge and Brave.

Curiously, PVE's shell works fine.

Dentax commented 1 year ago

Same for me. Fresh Installation on RPi 4 - Kernel: Linux 5.15.84-v8+ #1613 SMP PREEMPT

image

wofferl commented 1 year ago

Does calling termproxy --help on the console work? Is there anything about termproxy in the syslog?

Can you check the browser network log to see if the websocket call is correct? Are the parameters port and vncticket set?

It should look like this:

wss://192.168.0.1:8007/api2/json/nodes/localhost/vncwebsocket?port=44719&vncticket=PBSTERM........

Dentax commented 1 year ago

termproxy --help doesn't work.

image

On browser network log its called:

image image

wofferl commented 1 year ago

The termproxy binary is missing or not in binary path.

Can you look if the pve-xtermjs is installed correctly and the binary is in PATH. dpkg -s pve-xtermjs dpkg -L pve-xtermjs

Leo-wq commented 1 year ago

for me it looks like xterms is installed correctly...

xxxxxxxxx@pbs:~ termproxy --help -bash: termproxy: Kommando nicht gefunden. xxxxxxxx@pbs:~$ dpkg -s pve-xtermjs Package: pve-xtermjs Status: install ok installed Priority: optional Section: admin Installed-Size: 1503 Maintainer: Proxmox Support Team support@proxmox.com Architecture: arm64 Multi-Arch: allowed Source: rust-termproxy Version: 4.16.0-1 Description: HTML/JS Shell client for Proxmox projects This package provides an xterm.js client/proxy for Proxmoxprojects' Hosts, Proxmox VE containers or Proxmox VE VM's serial-terminals. Homepage: https://www.proxmox.com)

xxxxxxxxx@pbs:~ dpkg -L pve-xtermjs /. /usr /usr/share /usr/share/doc /usr/share/doc/pve-xtermjs /usr/share/doc/pve-xtermjs/SOURCE /usr/share/doc/pve-xtermjs/changelog.Debian.gz /usr/share/doc/pve-xtermjs/copyright /usr/share/pve-xtermjs /usr/share/pve-xtermjs/index.html.hbs /usr/share/pve-xtermjs/index.html.tpl /usr/share/pve-xtermjs/main.js /usr/share/pve-xtermjs/style.css /usr/share/pve-xtermjs/util.js /usr/share/pve-xtermjs/xterm-addon-fit.js /usr/share/pve-xtermjs/xterm-addon-fit.js.map /usr/share/pve-xtermjs/xterm.css /usr/share/pve-xtermjs/xterm.js /usr/share/pve-xtermjs/xterm.js.map xxxxxxxxxx@pbs:~$

wofferl commented 1 year ago

The termproxy binary (/usr/bin/termproxy) is missing in your pve-xtermjs package. Can you rebuild it and see if you get any errors during the build?

Leo-wq commented 1 year ago

How can I compile only the xterm package, or do I have to compile them all again?

wofferl commented 1 year ago

You can remove or rename the pve-xtermjs package in the packages folder and start the build.sh again.

or go to source/pve-xtermjs and compile it from there with: make deb

Leo-wq commented 1 year ago

Okay thanks. I'll try it out as soon as the backup has been restored... 4 tb already need more than 23h, from hdd from ssd... Something doesn't fit again 🤦🏼‍♂️ but that's another matter

Leo-wq commented 1 year ago

there are only a few warnings, no errors:

make[1]: Entering directory '/root/proxmox-backup-arm64/sources/pve-xtermjs' dh binary dh_prep dh_auto_install dh_install dh_installdocs dh_installchangelogs dh_perl dh_link dh_strip_nondeterminism dh_compress dh_fixperms dh_missing dh_strip dh_makeshlibs dh_shlibdeps dh_installdeb dh_gencontrol dpkg-gencontrol: warning: Depends field of package pve-xtermjs: substitution variable ${shlibs:Depends} used, but is not defined dpkg-gencontrol: warning: Depends field of package pve-xtermjs: substitution variable ${cargo:Depends} used, but is not defined dpkg-gencontrol: warning: Recommends field of package pve-xtermjs: substitution variable ${cargo:Recommends} used, but is not defined dpkg-gencontrol: warning: Suggests field of package pve-xtermjs: substitution variable ${cargo:Suggests} used, but is not defined dpkg-gencontrol: warning: Provides field of package pve-xtermjs: substitution variable ${cargo:Provides} used, but is not defined dpkg-gencontrol: warning: Built-Using field of package pve-xtermjs: substitution variable ${cargo:Built-Using} used, but is not defined dpkg-gencontrol: warning: package pve-xtermjs: substitution variable ${cargo:X-Cargo-Built-Using} used, but is not defined dh_md5sums dh_builddeb dpkg-deb: building package 'pve-xtermjs' in '../pve-xtermjs_4.16.0-1_arm64.deb'. make[1]: Leaving directory '/root/proxmox-backup-arm64/sources/pve-xtermjs'

wofferl commented 1 year ago

I forgot, you need to do a make clean before make deb.

Leo-wq commented 1 year ago

No difference. Same warnings only.

Dentax commented 1 year ago

Same for me. Did a make clean and then make deb

image

wofferl commented 1 year ago

Ok, there is currently a problem with pve-xtermjs. The build termproxy binary is not packed in, which is easy to solve, but there is also a problem that the binary does not work anyway. It looks like a problem with missing dependencies. I'll take a look at it.