December 8, 20232 yr Hi all - This is really puzzling me. My freshly installed server's actual static IP differs from what is configured in the GUI under Settings/Network Settings for interface eth0. After installing, I could not reach the server, so I logged in as root on the local console. Here I saw (issue) that the server was actually running .13 while I had configured .15 in the GUI. You will see the same thing in the diagnostic data attached: The static IP in system/ifconfig.txt differs from the one in config/network.cfg. So obviously, the server is only reachable under .13 for now, despite what is configured in the GUI. How can this even happen? I assumed the GUI network settings will overwrite whatever is configured in Linux underneath? And more importantly: How can I fix this without breaking any of the generated settings? shuttle-diagnostics-20231208-0636.zip
December 8, 20232 yr Community Expert This is very strange, probably not the issue, but since I've never seen that before try setting the NIC to .15, not .015 as it is.
December 8, 20232 yr Community Expert Solution 4 minutes ago, JorgeB said: This is very strange, probably not the issue, but since I've never seen that before try setting the NIC to .15, not .015 as it is. The 015 would explain it as the leading 0 means it is treated as octal number and 015 in octal is 13 in decimal
December 8, 20232 yr Author 4 hours ago, itimpi said: The 015 would explain it as the leading 0 means it is treated as octal number and 015 in octal is 13 in decimal That's it, THAT'S IT. Removing the leading zero brings all back to normal. Just by some old habit, I've been using a leading 0 as a lot of broken UIs require you to enter 3 digits, so I don't even think about anymore. You have some serious troubleshooting moves going on there!
February 13, 20242 yr Thanks for reporting! Unraid 6.12.7-rc2 will strip leading zeros from IP addresses to prevent other folks from running into this:
October 23, 2025Oct 23 My Unraid has a static ip set as 192.168.0.10. After a brief power cut yesterday (the unraid is on a UPS, but the switch it is connected to and the router is not) it aquired an ip address of 192.168.0.127!I stopped the docker and went to change the network setting, but they are set as static at the correct .10 address No preceeding zero in my settings and not accessible at .10, but it is accessible at .127. I guess a reboot will fix this, any idea why this would happen? And reboots for me are fraught with unclean shutdown risks, even if I stop everything docker and vms beforehand. \I have troubleshot that issue changing timeouts etc, but no joy. But that is another thread.Thoughts??
October 23, 2025Oct 23 So I realise that the main ethernet is not functional, the ip .127 is on a different port that was set up to be used by homeassistant, which is not running. Will need to reboot!
October 29, 2025Oct 29 Please start a new thread and provide diagnostics, as this thread is about a specific issue that has been resolved
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.