[SOLVED] Proxmox network issue not connecting to internet

M

miker710

New Member
Dec 29, 2022
10
1
3
I have a r710 server that is connect through LAN to my unify router. My server was working fine for a couple weeks then one day went offline, looking at my unifi network I saw that the server was offline. I have restarted them, tried different ports and cables (both were not the issue) but the server is not showing as online and is not connecting to the internet. I have tried to ping and obviously that didn’t work either. I then took my Hard drive out and put it in another sever.. this also wasn’t shown on the network. Then testing tvs and laptops they did show on the network. Has anyone seen this or have any ideas why the servers are not being seen on the network, I am running proxmox. (I have tried my Vlan and the default network so it’s not a firewall issue). I have changed my etc/network/interfaces and the hosts... the server has the correct default gateway. what am i missing? i know its not the NIC failing.

The following commands
in interfaces
auto lo
iface lo inet loopback
iface enol inet manual
bridge-ports eno1
bridge-stp off
bridge-fd 0
iface eno2 inet manual
iface eno3 inet manual
iface eno4 inet manual
auto vmbr0
iface vmbr0 inet static
address 192.168.2.121/24
gateway 192.168.2.1
bridge-ports none
bridge-stp off
bridge-fd 0
bridge-vlan-aware yes
bridge-vids 2-4094

root@# ifreload -a
warning: eno1: bridge.bridge object at 0x7f8943c1be0>: error getting dependent interfaces (misconfiguration of bridge attribute(s) on existing non-bridge interface (eno1))

ip -br -c -a
lo UNKNOWN 127.0.0.1/8 : : 1/128
eno1 down
eno2 down
eno3 down
eno4 down
vmbr0 down 192.168.2.121/24

cat var/log/pveproxy/access.log

ffff: 192.168.2.187- -[29/12/2022:09:22:54 - - 10001 "GET / HTTP/1.1" 200 2241

ffff: 192.168.2.121 - - [29/12/2022:08:06:09 -1000] "GET / HTTP/1.1" 200 2241


root@# systemcti status pveproxy.service

• pveproxy.service - PVE API Proxy Server
Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2022-12-29 07:43:10 HST; 22min ago
Process: 947 ExecStartPre=/us/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS
Process: 949 Execstart=/usr/bin/peproxy start (code=exited, status=0/SUCCESS)
Main PID: 953 (pveproxy)
Tasks: 4 (limit: 14216)
Memory: 135.3M
CPU: 2.9025
CGroup: /system.slice/pveproxy.service
  • 953 pveproxy
  • 954 pveproxy worker
  • 955 pveproxy worker
  • 956 pveproxy worker
Dec 29 07:43:07 pve-MikeServer systemd [1]: Starting PVE API Proxy Server..
Dec 29 07:43:10 pve-MikeServer pveproxy [953]: starting server
Dec 29 07:43:10 pve-MikeServer pveproxy [953]: starting 3 worker(s)
Dec 29 07:43:10 pve-MikeServer pveproxy [953]: worker 954 started Dec 29 07:43:10 pve-MikeServer pveproxy [953]: worker 955 started Dec 29 07:43:10 pve-MikeServer pveproxy [953]: worker 956 started

Dec 29 07:43:10 pve-MikeServer systemd[1]: Started PVE API Proxy Server.

root@# cur1 -k https://192.168.2.121:8006/ | grep title

% Total % Received % X ferd AverageDload Speed Time Time Time Current
Upload Total Spent Left Speed

100 2241 100 2241 0 0 7727 0----:=- __:--:-- __:--:-- __:--:-- 7754
 
miker710 said:
iface enol inet manual
bridge-ports eno1
bridge-stp off
bridge-fd 0
Click to expand...
That should be "eno1" and not "enol". And that...
Code: 
bridge-ports eno1
bridge-stp off
bridge-fd 0
...doesn't belong there. Thats your NIC, not a bridge.

iface vmbr0 inet static
address 192.168.2.121/24
gateway 192.168.2.1
bridge-ports none
bridge-stp off
bridge-fd 0
bridge-vlan-aware yes
bridge-vids 2-4094
Click to expand...
And your actual bridge isn't connected to a NIC. "bridge-ports none" should be something like "bridge-ports eno1" or whatever NIC you want to use.
 
Dunuin said:
That should be "eno1" and not "enol". And that...
Code: 
bridge-ports eno1
bridge-stp off
bridge-fd 0
...doesn't belong there. Thats your NIC, not a bridge.


And your actual bridge isn't connected to a NIC. "bridge-ports none" should be something like "bridge-ports eno1" or whatever NIC you want to use.
Click to expand...
The etho1 was just a error on my end posting it, and on the last note should I just delete the?

bridge-ports none
bridge-stp off
bridge-fd 0
bridge-vlan-aware yes
bridge-vids 2-4094

Or just change to bridge-ports etho1? Is this the reason I’m having issues?

Thanks!
 
Your config should look something like this for untagged vlan:
Code: 
auto lo
iface lo inet loopback

iface eno1 inet manual
iface eno2 inet manual
iface eno3 inet manual
iface eno4 inet manual

auto vmbr0
iface vmbr0 inet static
    address 192.168.2.121/24
    gateway 192.168.2.1
    bridge-ports eno1
    bridge-stp off
    bridge-fd 0
    bridge-vlan-aware yes
    bridge-vids 2-4094

Or something like this in case you want PVE to be in tagged VLAN 100:
Code: 
auto lo
iface lo inet loopback

iface eno1 inet manual
iface eno2 inet manual
iface eno3 inet manual
iface eno4 inet manual

auto vmbr0
iface vmbr0 inet manual
    bridge-ports eno1
    bridge-stp off
    bridge-fd 0
    bridge-vlan-aware yes
    bridge-vids 2-4094

auto vmbr0.100
iface vmbr0.100 inet static
    address 192.168.2.121/24
    gateway 192.168.2.1
 
Last edited:
Dunuin said:
Your config should look something like this for untagged vlan:
Code: 
auto lo
iface lo inet loopback

iface eno1 inet manual
iface eno2 inet manual
iface eno3 inet manual
iface eno4 inet manual

auto vmbr0
iface vmbr0 inet static
    address 192.168.2.121/24
    gateway 192.168.2.1
    bridge-ports eno1
    bridge-stp off
    bridge-fd 0
    bridge-vlan-aware yes
    bridge-vids 2-4094

Or something like this in case you want PVE to be in tagged VLAN 100:
Code: 
auto lo
iface lo inet loopback

iface eno1 inet manual
iface eno2 inet manual
iface eno3 inet manual
iface eno4 inet manual

auto vmbr0
iface vmbr0 inet manual
    bridge-ports eno1
    bridge-stp off
    bridge-fd 0
    bridge-vlan-aware yes
    bridge-vids 2-4094

auto vmbr0.100
iface vmbr0.100 inet static
    address 192.168.2.121/24
    gateway 192.168.2.1
Click to expand...
so i changed it to your first suggestion and then ifredload -a which returned

"error: netlink: etho1 enslave link etho1 to vmbro: operation failed with 'No such device' (19)
error: vmbr0: bridge port etho1 does not exist
 
miker710 said:
so i changed it to your first suggestion and then ifredload -a which returned

"error: netlink: etho1 enslave link etho1 to vmbro: operation failed with 'No such device' (19)
error: vmbr0: bridge port etho1 does not exist
Click to expand...

You should really take more care what gets written.

Your NIC in question is named: eno1 and not: enol, nor: etho1.
Also is the bridge named: vmbr0 and not: vmbro.
 
Neobin said:
You should really take more care what gets written.

Your NIC in question is named: eno1 and not: enol, nor: etho1.
Also is the bridge named: vmbr0 and not: vmbro.
Click to expand...
sorry some of the errors were because i used a tool to convert text from a screenshot to text for this, but you 100% solved the issue! thank you so much!
 
  • Like
Reactions: Neobin
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back