post tteck install ve - problem - can't login to gui and no vm's

mooncaptain

New Member
Mar 31, 2024
7
0
1
my name is idiot.
I ran tteck's post install script on my ve after having good success with a similar one on the backup server.
after the reboot I can't connect to gui.
I can start the vm's using the command line as in: qm start ... but I can't connect to them over the network.

I can ping ip addresses on the internet.

I can ping the server from my workstation but pinging it is slow about 300-500ms sometimes and highly variable speeds. Ping out from proxmox ve is faster, always sub second, but still slower that other systems. Could be hardware problem - or some side effect of the script.

also just before i messed up i setup and tested one backup from the ve to the pbs.

is there a way using vzdump to make a backup to the pbs server?

if that is not possible I just ran vzdump -all (4 small servers) and they got stored somewhere on my system I just need to know where and I can copy them to a usb drive and ask another question once I get a proxmox ve going again.

Alternatively if anybody can help me get this one back online.

Cheers
 
Last edited:
I got lucky - i kept thinking that the network may have gotten reconfigured somehow - in the end i'm sure it didn't. but in interfaces I bypassed the virtual nic and hardwired the physical directly to the ip address. I was able to log in to my gui then but ... the vm's couldn't connect to the network because they use the virtual nic i removed. I reverted the interfaces back. The gui is currently working and my vm's are running. I haven't fully tested yet but I can refresh the gui and it comes back. So I don't know what happened. interfaces looks like this:
Code:
auto lo
iface lo inet loopback

iface enp1s0 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.0.201/24
        gateway 192.168.0.1
        bridge-ports enp1s0
        bridge-stp off
        bridge-fd 0

iface wlo1 inet manual


source /etc/network/interfaces.d/*

I'll finish getting my backup running. and learn out to backup the ve itself too.<G>
 
I took a hard look at the script and it doesn't really do anything other than load up some different packages using deb command and set some flags in settings files.
My problem is that above interfaces file does not work after a reboot. Again I had to modify interfaces and use ifup and ifdown and ifquery to get it so i could use the gui - then I modified it back to more or less above config and got it going again. I changed two items from the above configuration. One on purpose and the other left over from various edit mods as I was flailing around.

1st off i changed the ip address. There were no conflicts on my network for .201 but I changed it to .222 also somehow the iface vmbr0 inet static line got changed to iface vmbr0 inet manual.

after above tweaks I was able to do a hard shutdown and power up and the network configuration held up.

I am not convinced this is the real answer. It is still possible I have a hardware problem that comes and goes.
 
Code:
cat /etc/network/interfaces
auto lo
iface lo inet loopback

iface enp1s0 inet manual

auto vmbr0
iface vmbr0 inet manual
        address 192.168.0.222
        netmask 255.255.255.0
        gateway 192.168.0.1
        bridge-ports enp1s0
        bridge-stp off
        bridge-fd 0

iface wlo1 inet manual

source /etc/network/interfaces.d/*

Code:
cat /etc/hosts
127.0.0.1 localhost.localdomain localhost
192.168.0.222 pve.allthisisthat.net pve

# The following lines are desirable for IPv6 capable hosts

::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
 
iface vmbr0 inet manual
As per docs, change to
iface vmbr0 inet static



Code:
address 192.168.0.222
netmask 255.255.255.0

#---------------------#
#replace with

address 192.168.0.222/24
# leaving out netmask line

Your code generally looks alright, except I notice you have iface wlo1 inet manual
This looks like a WiFi card, and may be causing some mac/addressing/dhcp/router conflict.
If you have no need for the WiFi access in PVE, (which you shouldn't)
Just comment out that line to #iface wlo1 inet manual

So in summary it should look like this:
Code:
nano /etc/network/interfaces
auto lo
iface lo inet loopback

iface enp1s0 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.0.222/24
        gateway 192.168.0.1
        bridge-ports enp1s0
        bridge-stp off
        bridge-fd 0

#iface wlo1 inet manual

source /etc/network/interfaces.d/*
 
Except for commenting out the wireless device I have tried both of the other suggestions. Like you, I don't know why they would make a difference and they should make it better.

The test that I will do involves doing
Code:
shutdown now
then push the power button.
If I can log in then OK otherwise I have to move my box to a place where I can hook up a monitor and keyboard and try to coax it back to working.
I am curious so I'll take the chance of causing more work.
 
Your answer is not clear whether or not you are commenting out the WiFi card. I have given you this advice to help with your problem. Since possibly for some reason your WiFi card is getting an IP address from your router (maybe you used this "box" in the past or something).
 
I implemented your suggestions. Changed to cidr notation. commented out wifi and changed manual to static.

shutdown and restarted twice.

This machine used to have windows on it but I bought it specifically to run proxmox - or vmware - I never have used the wifi. When I installed proxmox the install detected the wife device and set it to manual.
 
You can confirm the Wifi is not being used in PVE, by looking in the (GUI) Node, Network & making sure the device isn't listed. If it does, Remove it.
 

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!