Cannot log in to the web console: Connection closed (Code: 1006)

C

ColinDexter

Member
Jul 3, 2023
44
7
8
On one of my nodes I cannot log in to the console via the web interface. I get the message: Connection closed (Code: 1006) /bin/login: 3: Syntax error: "(" unexpected. I already tried apt install --reinstall proxmox-widget-toolkit. But this was not the solution.
 
  • Like
Reactions: kotovasia
Hi,

May you try to renew the certificate on your cluster using the following command?

Bash: 
pvecm updatecerts --force

If that didn't help, could you please check the syslog looking for any error message?
 
Hi Moayad,
Thanks for the response. pvecm updatecerts --force gave no error messages. Also no error messages in the syslog. But still have the same error message
 
Hi,

Do you have any HTTP proxy? Did you check the firewall? Does the issue happen on different browsers as well?
 
I don't have an HTTP proxy and in another browser I get the same error message. I can open the console of the other hosts. It seems that something is not right on this particular host.
 
When I start the console I get the following error on the syslog


Code: 
May 06 13:47:45 pve01 pvedaemon[2318660]: command '/usr/bin/termproxy 5900 --path /nodes/pve01 --perm Sys.Console -- /bin/login -f root' failed: exit code 1
May 06 13:47:45 pve01 pvedaemon[1309]: <root@pam> end task UPID:pve01:00236144:02736D39:6638C357:vncshell::root@pam: command '/usr/bin/termproxy 5900 --path /nodes/pve01 --perm Sys.Console -- /bin/login -f root' failed: exit code 1
 
When I log in to another node and connect to that node I get the following error message: bash: line 1: /bin/login: cannot execute binary file: Exec format error

It looks like a file is corrupt.
 
I have now also reinstalled pve-manager apt install --reinstall pve-manager But that didn't solve the problem either :-(
 
similarly:

Code: 
ailed waiting for client: timed out
TASK ERROR: command '/usr/bin/termproxy 5901 --path /nodes/proxmox --perm Sys.Console -- /bin/login -f root' failed: exit code 1
 
kotovasia said:
similarly:

Code: 
ailed waiting for client: timed out
TASK ERROR: command '/usr/bin/termproxy 5901 --path /nodes/proxmox --perm Sys.Console -- /bin/login -f root' failed: exit code 1
Click to expand...
It turned out that this was due to one of the two inactive machines in the cluster.
I used a cluster to transfer containers to a more productive machine and now I don’t need the machine from which I made the transfer.
 
Last edited:
That's a shame to read. Then maybe I should look for an alternative.....
I now have two hosts out of 3 having a problem. On one host the web shell does not work and on the other host the VM spontaneously reboots after a while :-(
 
  • Like
Reactions: kotovasia
It seems like the task starts too late when I look at the system log and compare a host with the host that is not working

[not working shell]
Code: 
Jun 03 13:31:16 pve01 pvedaemon[3385481]: starting termproxy UPID:pve01:0033A889:10DD56C0:665DA984:vncshell::root@pam:
Jun 03 13:31:16 pve01 pvedaemon[4152207]: <root@pam> starting task UPID:pve01:0033A889:10DD56C0:665DA984:vncshell::root@pam:
Jun 03 13:31:16 pve01 pvedaemon[4154785]: <root@pam> successful auth for user 'root@pam'
Jun 03 13:31:16 pve01 pvedaemon[4152207]: <root@pam> end task UPID:pve01:0033A889:10DD56C0:665DA984:vncshell::root@pam: OK

[working shell]
Code: 
Jun 03 13:34:05 pve02 pvedaemon[2633029]: <root@pam> starting task UPID:pve02:0030FFB2:1114FB30:665DAA2D:vncshell::root@pam:
Jun 03 13:34:05 pve02 pvedaemon[3211186]: starting termproxy UPID:pve02:0030FFB2:1114FB30:665DAA2D:vncshell::root@pam:
Jun 03 13:34:05 pve02 pvedaemon[2635023]: <root@pam> successful auth for user 'root@pam'
Jun 03 13:34:05 pve02 login[3211189]: pam_unix(login:session): session opened for user root(uid=0) by root(uid=0)
Jun 03 13:34:05 pve02 systemd[1]: Created slice user-0.slice - User Slice of UID 0.
Jun 03 13:34:05 pve02 systemd[1]: Starting user-runtime-dir@0.service - User Runtime Directory /run/user/0...
Jun 03 13:34:05 pve02 systemd-logind[654]: New session 954 of user root.
Jun 03 13:34:05 pve02 systemd[1]: Finished user-runtime-dir@0.service - User Runtime Directory /run/user/0.
Jun 03 13:34:05 pve02 systemd[1]: Starting user@0.service - User Manager for UID 0...
Jun 03 13:34:05 pve02 (systemd)[3211195]: pam_unix(systemd-user:session): session opened for user root(uid=0) by (uid=0)
Jun 03 13:34:05 pve02 systemd[3211195]: Queued start job for default target default.target.
Jun 03 13:34:05 pve02 systemd[3211195]: Created slice app.slice - User Application Slice.
Jun 03 13:34:05 pve02 systemd[3211195]: Reached target paths.target - Paths.
Jun 03 13:34:05 pve02 systemd[3211195]: Reached target timers.target - Timers.
Jun 03 13:34:05 pve02 systemd[3211195]: Listening on dirmngr.socket - GnuPG network certificate management daemon.
Jun 03 13:34:05 pve02 systemd[3211195]: Listening on gpg-agent-browser.socket - GnuPG cryptographic agent and passphrase cache (access for web browsers).
Jun 03 13:34:05 pve02 systemd[3211195]: Listening on gpg-agent-extra.socket - GnuPG cryptographic agent and passphrase cache (restricted).
Jun 03 13:34:05 pve02 systemd[3211195]: Listening on gpg-agent-ssh.socket - GnuPG cryptographic agent (ssh-agent emulation).
Jun 03 13:34:05 pve02 systemd[3211195]: Listening on gpg-agent.socket - GnuPG cryptographic agent and passphrase cache.
Jun 03 13:34:05 pve02 systemd[3211195]: Reached target sockets.target - Sockets.
Jun 03 13:34:05 pve02 systemd[3211195]: Reached target basic.target - Basic System.
Jun 03 13:34:05 pve02 systemd[3211195]: Reached target default.target - Main User Target.
Jun 03 13:34:05 pve02 systemd[3211195]: Startup finished in 161ms.
Jun 03 13:34:05 pve02 systemd[1]: Started user@0.service - User Manager for UID 0.
Jun 03 13:34:05 pve02 systemd[1]: Started session-954.scope - Session 954 of User root.
Jun 03 13:34:05 pve02 login[3211216]: ROOT LOGIN  on '/dev/pts/0'
 
You must log in or register to reply here.
Top Bottom