Maximo101

I had the same issue. Did you have a hardware change or upgrade the Unraid to newer version? (mine but a mix of both)
Is your server seen on your router dchp table list? (i assume it does since you can ping it)
 
Try logging into terminal and a few commands to see whats happening:
lshw -class network     (if your network is UNCLAIMED, you may need new drivers)
ifconfig -a
ethtool eth0   (where eth0 is your lan adapter shown in previous command) - Link detection needs to be Yes, if no it could be a faulty ethernet cable or switch port.
lspci -nnk | grep -A3 Ethernet
route -n
 
here is my thread with solution which worked for me
 
 

This is how i solved this issue of no network, ip address not set on boot (minor docker issue still to resolve)
Worked this out with Claude AI in a few steps, compared to two days troubleshooting with ChatGPT and CoPilot (uses chatgpt 4o). Claude has a much better understanding of coding (take a photo with phone, upload it and it reads the data from the image without having to re type the results)
 
I used a usb ethernet adapter, flushed the route/ip to get it online. Downloaded the RTL8125 drivers/plugin from the Apps.
I removed the usb ethernet adapter (since i now have the Realtek RTL8125 drivers/plugin installed). Connected the ethernet cable to the on board port.
So now with: lshw -class network    it is no longer unclaimed.
I manually added the mac address for the motherboard to my router to set it a static IP address. It now shows up on the router (but still didnt connect to web gui)
ethtool eth0    , this shows link detected: yes
I edited the /boot/config/network.cfg    Not sure if this part helped at all as it doesnt seem to stick each boot.
to set DCHP="NO"
IPADDR="my static ip"
BONDING="No"     (not sure if this did anything as later in the gui later it shows Bonding as yes)
 
This is what i do to get it working, but need to be done on each boot. (ill create a startup script and add it to the next post)
 
Server boots up with no ip set.
ethtool eth0    , confirms shows link detected: yes
First, remove the interface from the bond:
ip link set eth0 nomaster
Then reconfigure it:
ip link set eth0 down
ip link set eth0 up
ip addr flush dev eth0
ip addr add 192.168.1.100/24 dev eth0
ip route add default via 192.168.1.1 dev eth0
 
Note:
192.168.1.100 is the static IP my router assigned the server, which i use for my web gui access
192.168.1.1 is the router (gateway) ip address from your network
 
I have now rebooted, no ip set each time and using these these commands each time restores network connection and access to the GUI so i can replicate getting the server back online.
Next ill add this into a startup script to do it automatically on boot.
 
Hope this helps others as there seems to be a few with the same/similiar issue of the virtual nic / bonding / eth0 not getting ip.
rossiserver-diagnostics-20250212-1055.zip