Search results

just a question. Did you guys used an OVH machine to test it? Did you guys tested with Proxmox 7 (upgraded from proxmox 6.4.13)? Debian 10.7 from proxmox repository, the one i am using. Link: http://download.proxmox.com/images/system/debian-10-standard_10.7-1_amd64.tar.gz LXC config arch...

I'm using the default configuration, nothing more. Like i explained, i have Proxmox 6.4 and Proxmox 7 in 2 OVH machines using the same configuration. I did exactly the same steps, when installing the LXC containers, so the problem is for sure something related with Proxmox 7 because in Proxmox...

I really dont know. I cant figure out why i always need to "service restart ssh" everytime i restart my lxc container so i can manage to login as root :(

@fabian Let me explain again... I've an OVH server machine with 1 default ip and 16 failover ips. I installed 1 lxc container with Debian 10.7 template that is present in the proxmox templates repository. Then i tested with default server ip and with failover ips (using the virtual mac...

Currently all my Proxmox 7 problems are solved. This is the only one that i cant manage to solve :( If i host this same container in a failover ip, it works, but using the dedicated server default ip, i can not login as root after restarting the lxc container.

After disabling the firewall, everything started working like expected. Commands to disable: systemctl stop firewalld systemctl disable firewalld @Stoiko Ivanov Thank you ;)

root@test:~# journalctl -b -- Logs begin at Tue 2021-08-03 10:52:06 UTC, end at Tue 2021-08-03 10:56:02 UTC. -- Aug 03 10:52:06 test systemd-journald[51]: Journal started Aug 03 10:52:06 test systemd-journald[51]: Runtime journal (/run/log/journal/bb320c4497504bf4ad044e02a1a Aug 03 10:52:06 test...

@Stoiko Ivanov My resolv.conf is already with: nameserver 8.8.8.8 nameserver 8.8.4.4 So thats not the problem. Any other possible solution?

**Forget the network problem. I managed to configure the network. Currently the only Problem is that i can ping for example "8.8.8.8" but i can not ping for example "google.com" Any possible solution?

root@test:~# journalctl -b -- Logs begin at Mon 2021-08-02 14:44:55 UTC, end at Mon 2021-08-02 14:45:09 UTC. -- Aug 02 14:44:55 test systemd-journald[49]: Journal started Aug 02 14:44:55 test systemd-journald[49]: Runtime journal (/run/log/journal/bb320c4497504bf4ad044e02a1a Aug 02 14:44:55 test...

I've a friend with a soyoustart dedicated machine and proxmox 7 that is facing exactly the same problem, so seems to be a general issue. Can you tell me the correct command to check it?

Hi guys I installed an Centos 8 stream VM, everything is ok. The only problem i face is the network connection. I cant manage to have internet in this VM. I'm using a failover ip (ovh) and i added the Virtual mac address like i see in some tutorials, but network is still not working. Anyone...

It is enabled by default but i can not connect with root. i alway need to access with proxmox panel console and run "service ssh restart" command so i can login with root (really stupid) :(

It is already enabled by default. This is only happening with proxmox 7 (proxmox 6 works with no problems exactly with the same configuration / steps).

I think you didnt read what i described with attention. you're telling me to do what i already had done :rolleyes:

what? I downloaded Debian 10.7 lxc image from proxmox templates and installed (like in proxmox 6). In proxmox 6 you just need to install it, edit the ssh to allow root login and restart ssh service... SSH root connections will always work with no problems even after restarting the container xD

Anyone can help? I already reinstalled Proxmox 7 but this seems to be a general problem and it is still happening the same.

Hello I installed Proxmox 7 and created a LXC container with Debian 10.7. I edited the sshd_config so i can connect with root user and restarted ssh service. SSH is working and i can connect as root. If i restart the container i can not connect with root user anymore. I need to use "service ssh...

up

The grub alteration works to start a centos7 container, but for example, for users using centos web panel, they will not be able to turn the cfd firewall on or it will block the login to the centos web panel. So basically this is not a complete solution.