I shutdown my server (Via shutdown in webUI) to show a friend the hardware setup of the server. Plugged everything back in and now I’m getting a timeout when accessing 192.168.1.100? Through iKVM I can access command line and it shows the ipv4 address as the one listed above. Anyone have any ideas? I can also login and use commands normally. I’m relatively new to UnRaid though so I’m not really sure what to do from here. I did run a top command to see if anything was using a bunch of resources and all usage was very low. Basic SuperMicro Xeon setup with a Nvidia Telsa P4, 32gb RAM. Any help would be greatly appreciated!

Edited August 15, 20232 yr by smelly-six-pack7702

If you are using a static IP rename /boot/config/network.cfg and reboot to go back to default DHCP, see if it gets an IP, if it doesn't or if the GUI is still not accessible using the DHCP IP post the diagnostics.

On 8/15/2023 at 1:53 PM, JorgeB said:

If you are using a static IP rename /boot/config/network.cfg and reboot to go back to default DHCP, see if it gets an IP, if it doesn't or if the GUI is still not accessible using the DHCP IP post the diagnostics.

Sorry super late reply I was just thinking about this and didnt realize someone responded. What is the best way to rename this? I don't have network access to the drives like I normally manage files due to the IP issue.

You can do it directly on the flash drive.

I also find the the issue, and help to get solved. After shutting down my server via the Unraid WebUI and restarting it, I started getting an ERR_CONNECTION_TIMED_OUT when trying to access it at 192.168.1.100. I was still able to access the server through iKVM, and the IP address showed correctly. To resolve this, I confirmed the network was active and then restarted the web interface using:

 

 /etc/rc.d/rc.nginx restart  

Also check that the Ethernet cable is securely plugged in and the network port LEDs are active. If that doesn’t help, try a full reboot from the terminal. Let me know what you find!