webgui tab "Network" error after upgrade from PVE 3.4 to 4.1

miha_r

New Member
May 1, 2014
20
0
1
webgui tab "Network" error after upgrade from PVE 3.4 to 4.1

Clipboard03.jpg

root@proxmox:/etc# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback


# network interface settings

iface eth0 inet manual

iface eth1 inet manual

auto vmbr0
iface vmbr0 inet static
address 192.168.59.190
netmask 255.255.255.0
gateway 192.168.59.191
bridge_ports eth0
bridge_stp off
bridge_fd 0
up ifconfig eth0 mtu 4000 || true
post-up echo 0 >/sys/devices/virtual/net/$IFACE/bridge/multicast_snooping

auto vmbr1
iface vmbr1 inet manual
bridge_ports eth1
bridge_stp off
bridge_fd 0
post-up echo 0 >/sys/devices/virtual/net/$IFACE/bridge/multicast_snooping



So what's going on???
 
only
Feb 22 19:51:18 proxmox pve-firewall[1439]: status update error: iptables_restore_cmdlist: Try `ip6tables-restore -h' or 'ip6table
s-restore --help' for more information.
 
in first check your host and interfaces and check this url

http://wiki.hetzner.de/index.php/Proxmox_VE/en

and decide you use Routed or Bridged

and reconfig the interface

and you should have 1 bridge in server web pannel at lest to create ct or vm

ver 4 not like ver 3 I faced this problem from a few days

hope to solve your problem .
 
Edit interfaces to
root@proxmox:/etc/network# cat /etc/network/interfaces
auto lo
iface lo inet loopback

iface eth0 inet manual

iface eth1 inet manual

do it without reboot. but still in webgui Error: failed to open socket (500)

PS: old vm's, created on pve3.4 with
root@proxmox:/etc/network# cat /etc/pve/qemu-server/100.conf | grep vmbr
net0: virtio=5E:CB:CD:E7:95:43,bridge=vmbr0
net1: virtio=BE:1A:8C:5B:0D:DC,bridge=vmbr1
working well, but if i try to create new one bridge not avaliable:

Clipboard04.jpg
 
Last edited:
are you use on ip with subnet or use malti ip's to send to you best choose
and it's fast way to create bridge do this
first take aback up from your interfaces and

auto lo
iface lo inet loopback

# device: eth0
auto eth0
iface eth0 inet static
address <main ip>
netmask 255.255.255.224
pointopoint <gateway >
gateway <gateway >
bridge_ports none
bridge_stp off
bridge_fd 0

and from your node --> newwork --> create -- > linux bridge and just click create let it empty ( for test first have anothr problem or not ) and click create


now try to create new vm or ct and run it and tell us what happend

note :: this way your vps don't have internet
 
root@proxmox:/etc/network# cat /etc/network/interfaces
# network interface settings
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
address 192.168.59.190
netmask 255.255.255.0
gateway 192.168.59.191

after reboot - Error: failed to open socket (500)

it is not in /etc/network/interfaces i guess.
 
Usually after an update/upgrade the browser cache (and maybe history) need to be cleaned/erased, or some bizarre behaviour shows up. Have you tried it?
 
Usually after an update/upgrade the browser cache (and maybe history) need to be cleaned/erased, or some bizarre behaviour shows up. Have you tried it?
"but if i try to create new one bridge not avaliable:"
its not cached.
 
Solved!
This was due
GRUB_CMDLINE_LINUX_DEFAULT="ipv6.disable=1 quiet"
in /etc/default/grub
BUG?
 
Last edited:

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!