Recent content by dinis

Hi. AT the end, worked the second tutorial. The problem was that the file 00.installer-config.yaml was conflicting. I renamed it to 00.installer-config.yaml.bck and problem vanished.

Hi. I already tried two tutorials and none worked. Network. Can anyone lend a hand? Posting here both paths I tried: 1 - using this tutorial: https://docs.ovh.com/ie/en/public-cloud/configure_a_failover_ip/#step-2-edit-the-configuration-file the commented line is there because I tried both...

solved. In Debian 11 we need to setup /etc/resolv.conf nameserver 8.8.8.8 , etc

This is my current config (img). I tried a few other configss but with no luck. Same way, also tried setting up the VM in the model Intel E1000 as well as VirtIO. Any ideas how I can debug? Thanks in advance

Hi all. Another happy customer :) - just to tell that gineta's solutions worked for me. Thanks. So, for other Sorcerer's apprentices (like I felt I was this time) to know: If you don't have iKVM access - some sort of remote VNC provided by datacenter (if you do, check this thread...

Hi, wolfgang and fabian. You replied when I was posting back. I had no iKVM access => had to use a recovery boot (provided by datacenter). Did not try your solution because I tested the one I mentioned above (https://forum.proxmox.com/threads/locked-out-with-firewall-ve-3-3.20517/) and worked...

thanks for your reply. I was looking at this thread: .... https://forum.proxmox.com/threads/locked-out-with-firewall-ve-3-3.20517/ My question is for the solution you mention and for the solution mentioned by user gineta, I have to have to mount the server after booting in "rescue mode",right...

Hi..Looks like this is my turn. I am in the same situation - but in /etc/systemd/system/multi-user.target.wants, I am not finding the pve-firewall.service. I find: cron.service ipmievd.service lm-sensors.service remote-fs.target rsync.service rsyslog.service smartd.service sshd.service...

Hi all. Solved. At the end it was not the netwrk configuration. Yesterday the IP was victim of a TCP_SYN and the provider blocked a couple of IPs on that range. They sent an email but it was blocked in the spam so I did not know my IP was off. Sorry for disturbing. And thanks for all the help...

Again... I searched for how to convert kvm into lxc and got this https://pve.proxmox.com/wiki/Convert_OpenVZ_to_LXC. However my backup files are this kind: vzdump-qemu-167-2018_03_04-05_00_02.vma.gz (not tar files which maks this method not to work). any ideas?

another idea-might this be because the host is debian 8 while the VM's are debian 9? shouldn't be but.... I would say the problem is located in the host - because the VM backups that worked perfectly now don't work when I recover them. Any one would agree that this might be a possibility?

Hi Rob Thanks for your input. I have these containers and don't want to loose their contents. I already saw that I can migrate kvm to lxc however, it is quite another uncharted area for me.... Now, without network access, my data is "inside"those kvm containers. Are you sure I am that doomed...

Hi. I have other VM and all they work on that subnet just fine (these were instructions by the server provider - well, they were for debian 8 - not sure if they are for debian 9). Anyhow, these servers have worked a few days this config. but then snaped

MIght there be an optional config in the VM that is bypassing the network configuration?

After fixing the interfaces, I have... Destination Gateway Genmask Flags MSSWindow irtt Iface 0.0.0.0 94.23.31.254 0.0.0.0 UG 0 0 0 eth0 94.23.31.254 0.0.0.0 255.255.255.255 UH 0 0 0 eth0 Still, no network.