[SOLVED] Error : 401 401 authentication failure when join a cluster

[team-rcv]

Hello,

I created a cluster with proxmox and when I run the command : pvecm add 192.168.0.25

on the node wich will join the cluster


I have this output on the command line :

Please enter superuser (root) password for '192.168.0.25': ****************************************
Establishing API connection with host '192.168.0.25'
The authenticity of host '192.168.0.25' can't be established.
X509 SHA256 key fingerprint is AA:A7:12:A3:16:FC:0A:B8:50:D5:84:8D:A7:66:E5:16:52:2B:AC:B0:AC:8F:98:E4:C3:4E:56:87:0D:18:D7:69.
Are you sure you want to continue connecting (yes/no)? yes
401 401 authentication failure

I have verified the time synchronisation, the same version...
And there is the same error with GUI interface.

Can you help me ?
Thanks for your future help

 

[Moayad]

Hi,

Please delete know hosts rm ~/.ssh/known_hosts then try again.

 

[kwinz]

I have the same problem. Freshly installed Proxmox 6.2-6 machines.
Subscription + fully updated.

Joining second machine to first machine's cluster via GUI gives error message:

Establishing API connection with host '192.168.194.11'
TASK ERROR: 401 401 authentication failure

I double checked the join information string. Removing known_hosts did not help as it does not exist on either pve1 or pve2 @Moayad

root@pve2:~# rm ~/.ssh/known_hosts
rm: cannot remove '/root/.ssh/known_hosts': No such file or directory
root@pve2:~# ls -la /root/.ssh/
total 20
drwxr-xr-x 2 root root 4096 Jun 22 14:09 .
drwx------ 4 root root 4096 Jun 22 15:53 ..
lrwxrwxrwx 1 root root 29 Jun 22 14:09 authorized_keys -> /etc/pve/priv/authorized_keys
-rw-r----- 1 root root 117 Jun 22 14:09 config
-rw------- 1 root root 1811 Jun 22 14:09 id_rsa
-rw-r--r-- 1 root root 391 Jun 22 14:09 id_rsa.pub

The relevant section in the logfile is just:

Jun 22 16:03:01 pve1 systemd[1]: Started Proxmox VE replication runner.
Jun 22 16:03:01 pve1 systemd[1]: Starting Cleanup of Temporary Directories...
Jun 22 16:03:01 pve1 systemd[1]: systemd-tmpfiles-clean.service: Succeeded.
Jun 22 16:03:01 pve1 systemd[1]: Started Cleanup of Temporary Directories.
Jun 22 16:03:06 pve1 pvedaemon[1297]: <root@pam> successful auth for user 'root@pam'
Jun 22 16:03:29 pve1 IPCC.xs[1298]: pam_unix(common-auth:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= user=root
Jun 22 16:03:31 pve1 pvedaemon[1298]: authentication failure; rhost=192.168.194.12 user=root@pam msg=Authentication failure
Jun 22 16:04:00 pve1 systemd[1]: Starting Proxmox VE replication runner...
Jun 22 16:04:01 pve1 systemd[1]: pvesr.service: Succeeded.
Jun 22 16:04:01 pve1 systemd[1]: Started Proxmox VE replication runner.
Jun 22 16:04:03 pve1 pvedaemon[1297]: <root@pam> successful auth for user 'root@pam'

and

Jun 22 16:02:01 pve2 systemd[1]: Started Proxmox VE replication runner.
Jun 22 16:02:55 pve2 pvedaemon[1285]: <root@pam> successful auth for user 'root@pam'
Jun 22 16:03:00 pve2 systemd[1]: Starting Proxmox VE replication runner...
Jun 22 16:03:01 pve2 systemd[1]: pvesr.service: Succeeded.
Jun 22 16:03:01 pve2 systemd[1]: Started Proxmox VE replication runner.
Jun 22 16:03:29 pve2 pvedaemon[1287]: <root@pam> starting task UPID: ve2:00000D2D:<removed>:<removed>:clusterjoin::root@pam:
Jun 22 16:03:29 pve2 systemd[1]: Starting Cleanup of Temporary Directories...
Jun 22 16:03:29 pve2 systemd[1]: systemd-tmpfiles-clean.service: Succeeded.
Jun 22 16:03:29 pve2 systemd[1]: Started Cleanup of Temporary Directories.
Jun 22 16:03:32 pve2 pvedaemon[3373]: 401 401 authentication failure
Jun 22 16:03:32 pve2 pvedaemon[1287]: <root@pam> end task UPID: ve2:00000D2D:<removed>:<removed>:clusterjoin::root@pam: 401 401 authentication failure
Jun 22 16:04:00 pve2 systemd[1]: Starting Proxmox VE replication runner...
Jun 22 16:04:01 pve2 systemd[1]: pvesr.service: Succeeded.

 

[kwinz]

I have the same problem. Freshly installed Proxmox 6.2-6 machines.
Subscription + fully updated.

Joining second machine to first machine's cluster via GUI gives error message:

Establishing API connection with host '192.168.194.11'
TASK ERROR: 401 401 authentication failure
[...]

Problem solved: Lastpass filled in the local machine's root password, and I assumed it was decoded from the join string, that's why I didn't notice that the remote machine's root password was wrong. Source: https://forum.proxmox.com/threads/cant-join-cluster-through-gui.68201/#post-321486

 

[team-rcv]

Hi,

Please delete know hosts rm ~/.ssh/known_hosts then try again.

I try this option but it does not work, it just makes an untimely disconnection and makes the error 401: No ticket

 

[gregzuro]

Problem solved: Lastpass filled in the local machine's root password, and I assumed it was decoded from the join string, that's why I didn't notice that the remote machine's root password was wrong. Source: https://forum.proxmox.com/threads/cant-join-cluster-through-gui.68201/#post-321486

This one got me, too. Thanks!

 

[kwinz]

This one got me, too. Thanks!

@Moayad @proxmox staff

Since this keeps tripping up admins can we please mark the foreign root account password as autocomplete=new-password so it doesn't get autofilled. Or maybe just renaming the field id is already enough.

Original suggestion: https://forum.proxmox.com/threads/cant-join-cluster-through-gui.68201/#post-306120
More information: https://bugzilla.mozilla.org/show_bug.cgi?id=1119063

If the admin wants to autofill the password from the remote server, if it incidentally happens to be the same as the local password, they can still copy paste it manually from the password manager.