Proxmox VE 7.4 cannot be installed

[Nuke Bloodaxe]

What do you mean? with the container what do you want to see?

With the container, I would be interested in seeing what language it is set to. The instructions, provided earlier, give the commands to do this, and also give the directions and commands to set the language.

 

[Max_zocker]

Okay, here's the instructions for Debian: https://wiki.debian.org/ChangeLanguage
I'd be most interested in what the container is set to at the moment.

I have now changed the keyboard layout to German and it still doesn't work, I tried to create a user but then the message comes up.

 

[Max_zocker]

With the container, I would be interested in seeing what language it is set to. The instructions, provided earlier, give the commands to do this, and also give the directions and commands to set the language.

Where can I see the setting?

 

[Nuke Bloodaxe]

In the instructions, the command is:

env | grep LANG

 

[Nuke Bloodaxe]

I have now changed the keyboard layout to German and it still doesn't work, I tried to create a user but then the message comes up.

Old picture, take new screenshot with output of useradd command. [or adduser , which is an easier command, but not always available.]

 

[Max_zocker]

In the instructions, the command is:

env | grep LANG

View attachment 49848

 

[Max_zocker]

It works with the user Max, but how can I make it possible to log in as root?

 

[Nuke Bloodaxe]

It works with the user Max, but how can I make it possible to log in as root?

Progress

Okay, now we know it is something explicitly stopping root logins and not another ssh fault.

In the CT:

cat /etc/ssh/sshd_config

Now make sure the following are set (we'll brute-force it, and set it the same as the Proxmox host):

PermitRootLogin yes
ChallengeResponseAuthentication no
UsePAM yes

See how things go

 

[Max_zocker]

Progress

Okay, now we know it is something explicitly stopping root logins and not another ssh fault.

In the CT:

cat /etc/ssh/sshd_config

Now make sure the following are set (we'll brute-force it, and set it the same as the Proxmox host):

PermitRootLogin yes
ChallengeResponseAuthentication no
UsePAM yes

See how things go

And how do I do that, it is set like this by default when creating CT / VM Server?

 

[Nuke Bloodaxe]

And how do I do that, it is set like this by default when creating CT / VM Server?

In your CT we can edit the sshd configuration, we are going to edit that configuration so it has settings the same as a configuration that permits root.

In the CT:

nano /etc/ssh/sshd_config

Change each of the following lines:

PermitRootLogin
ChallengeResponseAuthentication
UsePAM

To:

PermitRootLogin yes
ChallengeResponseAuthentication no
UsePAM yes

Write the file with Ctrl O
Exit the nano editor with Ctrl X

Reboot the container.
Test root login.

 

[Max_zocker]

In your CT we can edit the sshd configuration, we are going to edit that configuration so it has settings the same as a configuration that permits root.

In the CT:

nano /etc/ssh/sshd_config

Change each of the following lines:

PermitRootLogin
ChallengeResponseAuthentication
UsePAM

To:

PermitRootLogin yes
ChallengeResponseAuthentication no
UsePAM yes

Write the file with Ctrl O
Exit the nano editor with Ctrl X

Reboot the container.
Test root login.

works, but how do I do that later, it's supposed to work fully automatically, that he sets it etc.

 

[Nuke Bloodaxe]

That's the thing, I'm not sure it does. In my experience, most systems will prohibit root login over ssh, and it has to be set explicitly.

Note: I've been installing systems with non-root accounts and then setting them up with sudo and ssh keys for login. As a result, I personally don't see the root issue due to making sure it is locked off from ssh access. So, I'm out of the loop as regards root access being automatic; like, more than 10 years.

 

[Max_zocker]

That's the thing, I'm not sure it does. In my experience, most systems will prohibit root login over ssh, and it has to be set explicitly.

Note: I've been installing systems with non-root accounts and then setting them up with sudo and ssh keys for login. As a result, I personally don't see the root issue due to making sure it is locked off from ssh access. So, I'm out of the loop as regards root access being automatic; like, more than 10 years.

How do the server hosters manage that?

 

[Nuke Bloodaxe]

I suspect they customise their installations and the deployment images.

 

[Max_zocker]

I suspect they customise their installations and the deployment images.

and how does it work if i may ask?

 

[Nuke Bloodaxe]

Well, if you are making a custom image, you have total control as the vendor. This means that as part of the installation, you can have your own version of each configuration file, including settings such as allowing root access over ssh.

Another way of thinking of it, someone makes the install iso images. If another person also makes an iso for that distro, they can make all the changes they want before producing the iso [such as software to install, configuration file defaults which may be radically different, all the way to compiling custom versions of software with extra features or features removed.]

For LXC Template images, you can configure a running system, then make a template from it: https://forum.proxmox.com/threads/migrating-a-linux-install-into-a-proxmox-ve-lxc-container.57219/

 

[Max_zocker]

Well, if you are making a custom image, you have total control as the vendor. This means that as part of the installation, you can have your own version of each configuration file, including settings such as allowing root access over ssh.

Another way of thinking of it, someone makes the install iso images. If another person also makes an iso for that distro, they can make all the changes they want before producing the iso [such as software to install, configuration file defaults which may be radically different, all the way to compiling custom versions of software with extra features or features removed.]

For LXC Template images, you can configure a running system, then make a template from it: https://forum.proxmox.com/threads/migrating-a-linux-install-into-a-proxmox-ve-lxc-container.57219/

Somehow I'm too stupid to understand that xD

 

[Max_zocker]

Well, if you are making a custom image, you have total control as the vendor. This means that as part of the installation, you can have your own version of each configuration file, including settings such as allowing root access over ssh.

Another way of thinking of it, someone makes the install iso images. If another person also makes an iso for that distro, they can make all the changes they want before producing the iso [such as software to install, configuration file defaults which may be radically different, all the way to compiling custom versions of software with extra features or features removed.]

For LXC Template images, you can configure a running system, then make a template from it: https://forum.proxmox.com/threads/migrating-a-linux-install-into-a-proxmox-ve-lxc-container.57219/

So I want to make my own template / image (I create a container with Debian 11 and set everything there, and how do I do it now that future containers can choose it?

 

[Nuke Bloodaxe]

Would this be of help?
https://blog.stackattack.net/2022/03/09/custom-proxmox-ve-lxc-images/
And the... ultra simple but questionable way: https://www.sbarjatiya.com/notes_wiki/index.php/Create_custom_container_template_in_proxmox

 

[Max_zocker]

Would this be of help?
https://blog.stackattack.net/2022/03/09/custom-proxmox-ve-lxc-images/
And the... ultra simple but questionable way: https://www.sbarjatiya.com/notes_wiki/index.php/Create_custom_container_template_in_proxmox

Hello, I just tried the one and when I try to install it I get the error (you can see it in the picture)