Console not working for VM and LXC

wilkob

New Member
Sep 22, 2019
3
0
1
38
Hi,
I'm running PVE 6.0.7 on a NUC6CAY. I can open the PVE Shell but not the console on a VM or a LXC. I see a black window with a white rectangle and that's it. Sometimes after waiting 5 minutes It asks for the login but access will be always denied. After that no console is working, even when waiting a long time.
I am trying to access from a Win10 desktop via chrome and Firefox. I also tried with disabled firewall.
Do you have any hint for me?
Thank you very much.
edit: I do not have a VM running.
 
Last edited:

dcsapak

Proxmox Staff Member
Staff member
Feb 1, 2016
4,911
488
103
32
Vienna
did you try to press enter on the console when the cursor is visible?
also what kind of container is it? (which template did you use)
 

wilkob

New Member
Sep 22, 2019
3
0
1
38
I have to correct myself. Now hitting enter does not work anymore. The cursor just jumps to the next line. I am using this template.
debian-10.0-standard_10.0-1_amd64.tar.gz
A restart of the container solves that.
 

olma

Member
Apr 21, 2011
20
0
21
Hi, guys!

I need to bring this one up again.
I have the same problem but the solution of wilkob doesnt work for me.
I have the white cursor on a black screen. Hitting enter, moves the cursor down by one line. Nothing more. Tried the other consoles, but no luck.
The template I've used is the same as wilkob did: debian-10.0-standard_10.0-1_amd64.tar.gz .

Maybe someone has a solution for this....

Thank you very much.
 

erict206

Member
Dec 1, 2017
7
1
8
56
I'm having a very similar issue. PVE version: 6.2. I used the Turnkey Linux Debian-10.0-standard_10.0-1_amd64.tar.gz to create a container guest.

After starting the container, it pings, and the Proxmox GUI shows it's running (with extremely low resource usage). However, console window is blank. Hitting the enter key in the console moves the cursor down one line. After about five+ minutes, the normal prompt appears for login. I get similar results using Putty.

I have a Windows VM and a doku-wiki container and neither behaves this way. Both open in console instantly.

Once the console finally became responsive, I checked the start time of the SSH service and found it started 5+ mins after boot. A little more Googling and I found there's a known issue in the Debian build that causes this problem, and it's been an issue for over a year. Someone suggested installing haveged to fix the issue. My fix is to switch to Ubuntu.
 

jacha

New Member
Oct 3, 2020
1
0
1
28
Is there a fix for debian 10 template? Im having the same problem here
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE 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 your own in 60 seconds.

Buy now!