container incorrect login (no login)

[Zaman]

Hello,
I create container but still get incorrect login each time by using username as root
with different passwords but still the same.
#cat lxc-monitord.log

lxc-monitord 20191002161236.771 INFO     monitor - monitor.c:lxc_monitor_sock_name:212 - Using monitor socket name "lxc/ad055575fe28ddd5//var/lib/lxc" (length of socket name 33 must be <= 105)
lxc-monitord 20191002161236.772 NOTICE   lxc_monitord - cmd/lxc_monitord.c:main:472 - lxc-monitord with pid 923 is now monitoring lxcpath /var/lib/lxc
lxc-monitord 20191002162921.917 INFO     monitor - monitor.c:lxc_monitor_sock_name:212 - Using monitor socket name "lxc/ad055575fe28ddd5//var/lib/lxc" (length of socket name 33 must be <= 105)
lxc-monitord 20191002162921.962 NOTICE   lxc_monitord - cmd/lxc_monitord.c:main:472 - lxc-monitord with pid 936 is now monitoring lxcpath /var/lib/lxc
lxc-monitord 20191002171546.120 INFO     monitor - monitor.c:lxc_monitor_sock_name:212 - Using monitor socket name "lxc/ad055575fe28ddd5//var/lib/lxc" (length of socket name 33 must be <= 105)
lxc-monitord 20191002171546.125 NOTICE   lxc_monitord - cmd/lxc_monitord.c:main:472 - lxc-monitord with pid 938 is now monitoring lxcpath /var/lib/lxc
lxc-monitord 20191009074011.606 INFO     monitor - monitor.c:lxc_monitor_sock_name:212 - Using monitor socket name "lxc/ad055575fe28ddd5//var/lib/lxc" (length of socket name 33 must be <= 105)
lxc-monitord 20191009074011.116 NOTICE   lxc_monitord - cmd/lxc_monitord.c:main:472 - lxc-monitord with pid 1119 is now monitoring lxcpath /var/lib/lxc
lxc-monitord 20191009122223.221 INFO     monitor - monitor.c:lxc_monitor_sock_name:212 - Using monitor socket name "lxc/ad055575fe28ddd5//var/lib/lxc" (length of socket name 33 must be <= 105)
lxc-monitord 20191009122223.243 NOTICE   lxc_monitord - cmd/lxc_monitord.c:main:472 - lxc-monitord with pid 1080 is now monitoring lxcpath /var/lib/lxc

# pveversion -v

proxmox-ve: 6.0-2 (running kernel: 5.0.15-1-pve)
pve-manager: 6.0-4 (running version: 6.0-4/2a719255)
pve-kernel-5.0: 6.0-5
pve-kernel-helper: 6.0-5
pve-kernel-5.0.15-1-pve: 5.0.15-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.2-pve2
criu: 3.11-3
glusterfs-client: 5.5-3
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.10-pve1
libpve-access-control: 6.0-2
libpve-apiclient-perl: 3.0-2
libpve-common-perl: 6.0-2
libpve-guest-common-perl: 3.0-1
libpve-http-server-perl: 3.0-2
libpve-storage-perl: 6.0-5
libqb0: 1.0.5-1
lvm2: 2.03.02-pve3
lxc-pve: 3.1.0-61
lxcfs: 3.0.3-pve60
novnc-pve: 1.0.0-60
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.0-5
pve-cluster: 6.0-4
pve-container: 3.0-3
pve-docs: 6.0-4
pve-edk2-firmware: 2.20190614-1
pve-firewall: 4.0-5
pve-firmware: 3.0-2
pve-ha-manager: 3.0-2
pve-i18n: 2.0-2
pve-qemu-kvm: 4.0.0-3
pve-xtermjs: 3.13.2-1
qemu-server: 6.0-5
smartmontools: 7.0-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.1-pve1

Best Regards

 

[tim]

Make sure your root login with password is allowed for your template.
You can provide a ssh key when creating the container, this should make things easier.

 

[KatyComputer]

I am having the same issue with template debian-10.0-standard_10.0-1_amd64.tar.gz

How do we know if root login with password is allowed?

 

[LnxBil]

How do we know if root login with password is allowed?

It's allowed on the local console but not via SSH. IIRC it is the default since Debian Jessie or Stretch and has nothing to do with PVE.
If you need to change that, just do this inside of your guest:

echo -e "\n# allow root to login with password\nPermitRootLogin yes" >> /etc/ssh/sshd_config

and restart your system (or just the ssh service)