[SOLVED] Login to VM not anymore possible (Login incorrect)

birdy_one

New Member
Dec 5, 2022
8
1
3
VM is up and running, but login to VM is not anymore possible. I assume It is caused by one of the last updates. i tried to logging, but after entering root -> Login incorrect . No option to enter password.
Also SSH login is not anymore possible. One week ago at least SSH Login has worked.

Code:
root@pmx1:~# pvecm status
Cluster information
-------------------
Name:             ProxmoxCluster
Config Version:   3
Transport:        knet
Secure auth:      on

Quorum information
------------------
Date:             Mon Dec  5 08:13:54 2022
Quorum provider:  corosync_votequorum
Nodes:            3
Node ID:          0x00000001
Ring ID:          1.97
Quorate:          Yes

Votequorum information
----------------------
Expected votes:   3
Highest expected: 3
Total votes:      3
Quorum:           2  
Flags:            Quorate 

Membership information
----------------------
    Nodeid      Votes Name
0x00000001          1 10.10.10.18 (local)
0x00000002          1 10.10.10.19
0x00000003          1 10.10.10.17

Code:
root@pmx1:~# systemctl status pveproxy.service
● pveproxy.service - PVE API Proxy Server
     Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
     Active: active (running) since Mon 2022-12-05 06:59:39 CET; 1h 15min ago
    Process: 1489 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
    Process: 1495 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS)
   Main PID: 1503 (pveproxy)
      Tasks: 4 (limit: 18986)
     Memory: 224.5M
        CPU: 9.829s
     CGroup: /system.slice/pveproxy.service
             ├─1503 pveproxy
             ├─1504 pveproxy worker
             ├─1505 pveproxy worker
             └─1506 pveproxy worker

Dec 05 06:59:37 pmx1 systemd[1]: Starting PVE API Proxy Server...
Dec 05 06:59:39 pmx1 pveproxy[1503]: starting server
Dec 05 06:59:39 pmx1 pveproxy[1503]: starting 3 worker(s)
Dec 05 06:59:39 pmx1 pveproxy[1503]: worker 1504 started
Dec 05 06:59:39 pmx1 pveproxy[1503]: worker 1505 started
Dec 05 06:59:39 pmx1 pveproxy[1503]: worker 1506 started
Dec 05 06:59:39 pmx1 systemd[1]: Started PVE API Proxy Server.
 
So it's just the VM you can't access, ssh to PVE is working?
Did you try restarting the VM?
 
Yes only problems with VM, SSH to PVE is working.

To be precise, VM is not a real VM, it running as CT

I tied the following: Restart CT, restart Node, migrate to other Node, restore, restore to other Node, restore from older Backup.
VM is working fine, Services and Web Interfaces running on CT.

Starting point of my journey: 1. I reinstalled PVE on all Nodes and selected ZFS during install procedure. Because ZFS is needed to activate Replication 2. Installed latest Updates. 3. I restored CT from Backup.
 
You can enter a CT with the command pct enter CTID. That way, you can look for errors.
Please also make sure that the backup is from when the CT still worked.
 
Thx. pct enter 100 works. I’m able to log in CT on the Node console .

Console in PVE Web GUI for CT still not working. Maybe it’s why PVE is also using SSH for this access and it makes no difference if I use Putty or PVE Console on CT level.
 
SSH host keys deleted and regenerated
$ sudo rm -r /etc/ssh/ssh*key $ sudo dpkg-reconfigure openssh-server
Now SSH Access is working again.
 
  • Like
Reactions: datschlatscher

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!