Container Console Connection Problem

lowegame

Member
Nov 7, 2019
52
1
13
37
Hi, I'm trying to provide a console connection for the CT I created, but the password is correct, but the connection cannot be made.

I change the password and I cannot connect again. I need immediate help to solve it.

Screenshot: https://prnt.sc/ptnxyt

Server settings are as follows: https://prnt.sc/ptowm3

Thank You.
 
Last edited:
hi,

* how did you get the template?

* what is your pveversion -v output
 
  • Like
Reactions: lowegame
hi,

i think you should try to update your system.

run apt update && apt full-upgrade. you might have to reboot once the update is complete. (make sure your repositories are correctly configured[0])

afterwards. try again if you can log-in to your container.

[0]: https://pve.proxmox.com/wiki/Package_Repositories
 
hi,

i think you should try to update your system.

run apt update && apt full-upgrade. you might have to reboot once the update is complete. (make sure your repositories are correctly configured[0])

afterwards. try again if you can log-in to your container.

[0]: https://pve.proxmox.com/wiki/Package_Repositories

I've tried before getting the error in the update. I couldn't figure it out. Thanks again

Do you want to continue? [Y/n] y
W: (pve-apt-hook) !! WARNING !!
W: (pve-apt-hook) You are attempting to remove the meta-package 'proxmox-ve'!
W: (pve-apt-hook)
W: (pve-apt-hook) If you really want to permanently remove 'proxmox-ve' from your system, run the following command
W: (pve-apt-hook) touch '/please-remove-proxmox-ve'
W: (pve-apt-hook) run apt purge proxmox-ve to remove the meta-package
W: (pve-apt-hook) and repeat your apt invocation.
W: (pve-apt-hook)
W: (pve-apt-hook) If you are unsure why 'proxmox-ve' would be removed, please verify
W: (pve-apt-hook) - your APT repository settings
W: (pve-apt-hook) - that you are using 'apt full-upgrade' to upgrade your system
E: Sub-process /usr/share/proxmox-ve/pve-apt-hook returned an error code (1)
E: Failure running script /usr/share/proxmox-ve/pve-apt-hook
 
hmm. this is usually a sign of misconfigured repositories.

can you post your apt source list? (cat /etc/apt/sources.list and cat /etc/apt/sources.list.d/*.)
 
hmm. this is usually a sign of misconfigured repositories.

can you post your apt source list? (cat /etc/apt/sources.list and cat /etc/apt/sources.list.d/*.)


cat /etc/apt/sources.list
deb http://ftp.tr.debian.org/debian buster main contrib

deb http://ftp.tr.debian.org/debian buster-updates main contrib

# security updates
deb http://security.debian.org buster/updates main contrib


or

cat /etc/apt/sources.list.d/*
deb http://download.proxmox.com/debian/ceph-luminous buster main
deb https://enterprise.proxmox.com/debian/pve buster pve-enterprise


Outputs as above
 
comment out or replace the enterprise repository.

EDIT: it looks like the repositories are mixed? (buster & stretch).

you shouldn't use the buster repositories on pve 5 unless you want to update to pve 6. switch the debian repositories also to stretch
 
just like you edited the proxmox list, just change the buster entries to stretch in /etc/apt/sources.list . then run update.
 
just like you edited the proxmox list, just change the buster entries to stretch in /etc/apt/sources.list . then run update.


Do I need to fuck the contents? also I can not find the document on the proxmoxun page.

sorry i was tired
 
hey, please watch your language a bit here.

You're running Proxmox VE 5.4 based on Stretch, so why do you have all the buster repos configured?

If you want to stay on 5.4 be sure to also have those repos setup!
https://pve.proxmox.com/wiki/Package_Repositories#_proxmox_ve_5_x_repositories

If you want to upgrade read: https://pve.proxmox.com/wiki/Upgrade_from_5.x_to_6.0

version was 5.4.13 but not proxmox 6. The system does not update.

https://prnt.sc/ptv04u

The system that is not making pending updates probably broke
 
if you have mixed repositories (buster vs. stretch) it will not update (and cause problems on the way, like this).

probably the easiest way to get this fixed is to use the official ISO to install again (i'd recommend PVE 6 since it's the latest one with all the bugfixes).

if you cannot reinstall, then you will have to fix your repositories and update to the latest version of 5.x, and see if that solves your container problem.
 
if you have mixed repositories (buster vs. stretch) it will not update (and cause problems on the way, like this).

probably the easiest way to get this fixed is to use the official ISO to install again (i'd recommend PVE 6 since it's the latest one with all the bugfixes).

if you cannot reinstall, then you will have to fix your repositories and update to the latest version of 5.x, and see if that solves your container problem.

I'd fix the problem, thank you.
 

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!