Technical

Proxmox VE Lost TTY Shell: Restart the Getty, Not the Whole Node

Proxmox VE Lost TTY Shell: Restart the Getty, Not the Whole Node

Lost your Proxmox VE TTY shell? It’s usually just the getty that died, not the whole node. Restart it with systemctl and you’re back in.

A young barista processes a transaction using a wireless terminal in a cozy cafe setting.

Which Console Layer Actually Died

Proxmox has three separate console layers: the local getty on the physical TTY, the xterm.js web console, and a serial console if you set one up. They fail independently. If you can still reach the web UI, the node is fine — it’s the getty that’s gone.

The Fix: Restart Getty

SSH into the node and run:

systemctl restart getty@tty1

That restarts the login prompt on the physical console. If you need it to survive a reboot, enable it:

systemctl enable getty@tty1

Check status with systemctl status getty@tty1. If it’s inactive or failed, that’s your answer.

Close-up view of a computer displaying cybersecurity and data protection interfaces in green tones.

When the Web Console Is Also Dead

If the web console is unreachable, the node’s network or pveproxy might be down. Try SSH first. If SSH works, restart pveproxy:

systemctl restart pveproxy

If SSH doesn’t work either, you’re down to physical access or a serial console. This is where a persistent journal and netconsole save your butt — you can see what happened before the crash.

Why Getty Exits in the First Place

Getty can exit if it hits too many failed login attempts, if the TTY device disappears, or after a kernel update that changes the console setup. It’s not a Proxmox bug usually — it’s systemd doing its thing. The fix is the same: restart the service.

Don’t reboot the whole node for a dead getty. That’s like replacing the engine because the dashboard light is out. Restart the service, check the logs, move on.

Leave a comment

Comments are reviewed before they appear. Your email is never published.