Ethernet went off after successfully boot to PROXMOX VE

C

cahsobo

New Member
Feb 28, 2023
21
1
3
This is weird. My server is always getting disconnected from the LAN (the network card indicator LED is both turned off completely).
I'm sure there's something wrong with the proxmox or proxmox config. Because when I install windows on the SSD. The Ethernet acts normally.

- It has no problem when I login to windows
- it has no problem when I goto BIOS Setting

The ethernet only dies when the system successfully booted to PROXMOX.

I dunno what to do. Please help
 
Hi,

can you please provide the output of pveversion -v, lspci -tv and journalctl -b (as attachment please) and of the system when running Proxmox VE?

This sounds like some driver issue, esp. the (kernel) log might help diagnose this further.
 
cheiss said:
Hi,

can you please provide the output of pveversion -v, lspci -tv and journalctl -b (as attachment please) and of the system when running Proxmox VE?

This sounds like some driver issue, esp. the (kernel) log might help diagnose this further.
Click to expand...
Hello,
It seems like the server won't work without connecting to the internet. Does usually proxmox ve check for license online first before user can access it?
Now I can only access the server through SSH. Web UI doesn't work.
here's the lspci and journalctl output:

Code: 
lspci -tv
-+-[0000:ff]-+-0b.0  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R3 QPI Link 0/1
 |           +-0b.1  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R3 QPI Link 0/1
 |           +-0b.2  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R3 QPI Link 0/1
 |           +-0b.3  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R3 QPI Link Debug
 |           +-0c.0  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent
 |           +-0c.1  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent
 |           +-0c.2  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent
 |           +-0c.3  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent
 |           +-0c.4  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent
 |           +-0c.5  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent
 |           +-0c.6  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent
 |           +-0c.7  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent
 |           +-0d.0  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent
 |           +-0d.1  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent
 |           +-0d.2  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent
 |           +-0d.3  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent
 |           +-0f.0  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent
 |           +-0f.1  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent
 |           +-0f.2  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent
 |           +-0f.3  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent
 |           +-0f.4  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent
 |           +-0f.5  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent
 |           +-0f.6  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent
 |           +-10.0  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R2PCIe Agent
 |           +-10.1  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R2PCIe Agent
 |           +-10.5  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Ubox
 |           +-10.6  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Ubox
 |           +-10.7  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Ubox
 |           +-12.0  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Home Agent 0
 |           +-12.1  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Home Agent 0
 |           +-12.4  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Home Agent 1
 |           +-12.5  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Home Agent 1
 |           +-13.0  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Target Address/Thermal/RAS
 |           +-13.1  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Target Address/Thermal/RAS
 |           +-13.2  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel Target Address Decoder
 |           +-13.3  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel Target Address Decoder
 |           +-13.6  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 0/1 Broadcast
 |           +-13.7  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Global Broadcast
 |           +-14.0  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 0 Thermal Control
 |           +-14.1  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 1 Thermal Control
 |           +-14.2  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 0 Error
 |           +-14.3  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 1 Error
 |           +-14.4  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 0/1 Interface
 |           +-14.5  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 0/1 Interface
 |           +-14.6  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 0/1 Interface
 |           +-14.7  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 0/1 Interface
 |           +-16.0  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Target Address/Thermal/RAS
 |           +-16.1  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Target Address/Thermal/RAS
 |           +-16.2  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Channel Target Address Decoder
 |           +-16.3  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Channel Target Address Decoder
 |           +-16.6  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 2/3 Broadcast
 |           +-16.7  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Global Broadcast
 |           +-17.0  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 1 - Channel 0 Thermal Control
 |           +-17.1  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 1 - Channel 1 Thermal Control
 |           +-17.2  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 1 - Channel 0 Error
 |           +-17.3  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 1 - Channel 1 Error
 |           +-17.4  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 2/3 Interface
 |           +-17.5  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 2/3 Interface
 |           +-17.6  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 2/3 Interface
 |           +-17.7  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 2/3 Interface
 |           +-1e.0  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit
 |           +-1e.1  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit
 |           +-1e.2  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit
 |           +-1e.3  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit
 |           +-1e.4  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit
 |           +-1f.0  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit
 |           \-1f.2  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit
 \-[0000:00]-+-00.0  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DMI2
             +-01.0-[01]--
             +-01.1-[02]----00.0  Silicon Motion, Inc. SM2263EN/SM2263XT SSD Controller
             +-02.0-[03]--+-00.0  Broadcom Inc. and subsidiaries NetXtreme BCM5719 Gigabit Ethernet PCIe
             |            +-00.1  Broadcom Inc. and subsidiaries NetXtreme BCM5719 Gigabit Ethernet PCIe
             |            +-00.2  Broadcom Inc. and subsidiaries NetXtreme BCM5719 Gigabit Ethernet PCIe
             |            \-00.3  Broadcom Inc. and subsidiaries NetXtreme BCM5719 Gigabit Ethernet PCIe
             +-03.0-[04]--
             +-03.2-[05]--+-00.0  Broadcom Inc. and subsidiaries NetXtreme BCM5719 Gigabit Ethernet PCIe
             |            +-00.1  Broadcom Inc. and subsidiaries NetXtreme BCM5719 Gigabit Ethernet PCIe
             |            +-00.2  Broadcom Inc. and subsidiaries NetXtreme BCM5719 Gigabit Ethernet PCIe
             |            \-00.3  Broadcom Inc. and subsidiaries NetXtreme BCM5719 Gigabit Ethernet PCIe
             +-05.0  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Map/VTd_Misc/System Management
             +-05.1  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D IIO Hot Plug
             +-05.2  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D IIO RAS/Control Status/Global Errors
             +-05.4  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D I/O APIC
             +-14.0  Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI
             +-1a.0  Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2
             +-1b.0  Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller
             +-1c.0-[06]--
             +-1c.2-[07]----00.0  Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
             +-1c.5-[08]--+-00.0  Broadcom Inc. and subsidiaries NetXtreme BCM5719 Gigabit Ethernet PCIe
             |            +-00.1  Broadcom Inc. and subsidiaries NetXtreme BCM5719 Gigabit Ethernet PCIe
             |            +-00.2  Broadcom Inc. and subsidiaries NetXtreme BCM5719 Gigabit Ethernet PCIe
             |            \-00.3  Broadcom Inc. and subsidiaries NetXtreme BCM5719 Gigabit Ethernet PCIe
             +-1d.0  Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1
             +-1f.0  Intel Corporation B85 Express LPC Controller
             \-1f.3  Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller

Code: 
journalctl -b
-- Journal begins at Tue 2023-03-14 19:40:22 WIB, ends at Thu 2023-03-16 14:06:13 WIB. --
Mar 16 13:57:20 sl1 kernel: Linux version 5.15.74-1-pve (build@proxmox) (gcc (Debian 10.2.1-6) 10.2.1 2021011>
Mar 16 13:57:20 sl1 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.15.74-1-pve root=/dev/mapper/pve-root ro>
Mar 16 13:57:20 sl1 kernel: KERNEL supported cpus:
Mar 16 13:57:20 sl1 kernel:   Intel GenuineIntel
Mar 16 13:57:20 sl1 kernel:   AMD AuthenticAMD
Mar 16 13:57:20 sl1 kernel:   Hygon HygonGenuine
Mar 16 13:57:20 sl1 kernel:   Centaur CentaurHauls
Mar 16 13:57:20 sl1 kernel:   zhaoxin   Shanghai
Mar 16 13:57:20 sl1 kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Mar 16 13:57:20 sl1 kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Mar 16 13:57:20 sl1 kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Mar 16 13:57:20 sl1 kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
Mar 16 13:57:20 sl1 kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard'>
Mar 16 13:57:20 sl1 kernel: signal: max sigframe size: 1776
Mar 16 13:57:20 sl1 kernel: BIOS-provided physical RAM map:
Mar 16 13:57:20 sl1 kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable
Mar 16 13:57:20 sl1 kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000754ebfff] usable
Mar 16 13:57:20 sl1 kernel: BIOS-e820: [mem 0x00000000754ec000-0x0000000076247fff] reserved
Mar 16 13:57:20 sl1 kernel: BIOS-e820: [mem 0x0000000076248000-0x0000000076503fff] usable
Mar 16 13:57:20 sl1 kernel: BIOS-e820: [mem 0x0000000076504000-0x00000000770bafff] ACPI NVS
Mar 16 13:57:20 sl1 kernel: BIOS-e820: [mem 0x00000000770bb000-0x0000000077556fff] reserved
Mar 16 13:57:20 sl1 kernel: BIOS-e820: [mem 0x0000000077557000-0x00000000775a4fff] type 20
 
Last edited:
Here are the screenshots:

ssh.png

web ui.png

refused.png
 
Last edited:
cahsobo said:
It seems like the server won't work without connecting to the internet. Does usually proxmox ve check for license online first before user can access it?
Click to expand...
No, it does not.
cahsobo said:
Now I can only access the server through SSH. Web UI doesn't work.
Click to expand...
So Ethernet is working.

And looking at your screenshots: The Web UI runs on port 8006, not the standard HTTPS port.
So in your web browser, navigate to https://192.168.0.100:8006 - note the :8006 at the end.
 
cheiss said:
No, it does not.

So Ethernet is working.

And looking at your screenshots: The Web UI runs on port 8006, not the standard HTTPS port.
So in your web browser, navigate to https://192.168.0.100:8006 - note the :8006 at the end.
Click to expand...
OMG!!! I was so stupid!!
THANK YOU SOOO MUCH!!!
Just one question tho, do I have to access the Web UI by Ethernet only? Because WLAN doesn't work at all. I can't even ping the server
 
cahsobo said:
Just one question tho, do I have to access the Web UI by Ethernet only? Because WLAN doesn't work at all. I can't even ping the server
Click to expand...
This should work normally, so I guess there's something up with your network configuration.

Is your WiFi network in the (sub-)network as your PVE server? Are there other devices you could ping, in the same (physical) network as the PVE server, to see if it works?

What network address does your WiFi run in? (So network address and -mask)
 
  • Like
Reactions: cahsobo
cheiss said:
This should work normally, so I guess there's something up with your network configuration.

Is your WiFi network in the (sub-)network as your PVE server? Are there other devices you could ping, in the same (physical) network as the PVE server, to see if it works?

What network address does your WiFi run in? (So network address and -mask)
Click to expand...
update: it's done and worked normally. i dunno why tho..
 
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