Quantumleapr

After 24 hours of complete frustration, I shut the whole thing down for a day and didn't touch it. When I booted it back up, I moved from eth0 to eth1, and let DHCP assign it an address. It's been working since. I'm still not sure exactly where the issue was, but it could always happen again. Fingers crossed it won't. Thanks to all who offered advice!

Alright. I swapped the cat5e cable between the switch and server. I changed the switch port it was flowing into. I swapped from eth0 to eth1 and assigned it a static ip of 10.0.0.132. The ConsoleGUI is slightly more responsive. However, from I cannot go to even google.com from the ConsoleGUI. Under Main tab, I cannot start the array..." Cannot contact key-server". Dashboard shows Avg. CPU load at 0-1% memory usage: 16% Network: eth1 connected 1000Mb/s, full duplex, mtu 1500 I'm not sure where this tab is. I STILL cannot connect to tower.local from my mac or pc. Another note: If I plug the ethernet cable back into eth0 on the server, the ConsoleUI no long responds, it just sits at 'Waiting for localhost...' I'm really not sure what else to try here..

Thanks for the replies! I checked the Modems remembered devices and the MAC address of the port associated with 10.0.0.131 is d0:50:99:c2:8b:cb. Inside the Modems WebUI, under connected devices, there is the option to edit to the device to have it assigned a DHCP address, or give it a reserved address. I've tried both of these options, though, to no avail. I attached a screencap. Outside of that, I'll have to check the rest when I get home from work. Would it be worth swapping to eth1 and trying that? As for components, this machine is less than a month old ( I still have 10 days on my trial license), parts you requested are: ASRock C236 WSI Mini ITX Server Motherboard LGA 1151 Intel C236 Intel Xeon E3-1245 V5 SkyLake 3.5 GHz 8MB L3 Cache LGA 1151 80W BX80662E31245V5 Server Processor Kingston ValueRAM 8GB 288-Pin DDR4 SDRAM ECC Unbuffered DDR4 2133 (PC4 17000) Server Memory Model KVR21E15D8/8

Rebooted everything. I can ping every device on my network except for the server. I attached a monitor to the server and rebooted, and was able to pull a diagnostics. I've attached it to post. I've also booted into 'Unraid GUI Mode' and launched the webGUI from there. I believe from within the server the address bar reads 'LocalHost'. Strangely enough, it works, but takes on anywhere between 5-20 minutes to load each page. tower-diagnostics-20170808-2238.zip

Hi! Sorry if this has been resolved a million times before. I rebooted my router/modem combo (Arris TG3482G), and when it came back up I was no longer able to access my server. http://tower.local wasn't working, I receive this message: I couldn't access it from CLI, either. Verified on the modems admin page that is in in fact shown as connected from the "Connected Device" list. I rebooted the server and logged into GUI Mode, and from there was able to access the webUI when you launch the browser (localhost). I checked my ip-address and dhcp settings, and then rebooted. Now, I can't even access the localhost WebUI from the GUI Mode, it sits and hangs indefinitely trying to bring up the WebUI. Pinging the servers IP returns this: PING 10.0.0.131 (10.0.0.131): 56 data bytes Request timeout for icmp_seq 0 Request timeout for icmp_seq 1 Request timeout for icmp_seq 2 Request timeout for icmp_seq 3 Network config file looks like this: USE_DHCP=no IPADDR=10.0.0.131 NETMASK=255.255.255.0 GATEWAY=10.0.0.1 DNS_SERVER1=10.0.0.1 DNS_SERVER2= DNS_SERVER3= However, there is a few more lines uptop the file with BOND information, are these necessary? IPv4 Route Table =========================================================================== Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 10.0.0.1 10.0.0.220 266 10.0.0.0 255.255.255.0 On-link 10.0.0.220 266 10.0.0.220 255.255.255.255 On-link 10.0.0.220 266 10.0.0.255 255.255.255.255 On-link 10.0.0.220 266 127.0.0.0 255.0.0.0 On-link 127.0.0.1 306 127.0.0.1 255.255.255.255 On-link 127.0.0.1 306 127.255.255.255 255.255.255.255 On-link 127.0.0.1 306 224.0.0.0 240.0.0.0 On-link 127.0.0.1 306 224.0.0.0 240.0.0.0 On-link 10.0.0.220 266 255.255.255.255 255.255.255.255 On-link 127.0.0.1 306 255.255.255.255 255.255.255.255 On-link 10.0.0.220 266 =========================================================================== Persistent Routes: Network Address Netmask Gateway Address Metric 0.0.0.0 0.0.0.0 10.0.0.1 Default =========================================================================== IPv6 Route Table =========================================================================== Active Routes: If Metric Network Destination Gateway 10 266 ::/0 fe80::1256:11ff:fe88:9474 1 306 ::1/128 On-link 11 58 2001::/32 On-link 11 306 2001:0:9d38:953c:10fe:b93:e7eb:6c0c/128 On-link 10 18 2601:1c2:1302:4536::/64 On-link 10 266 2601:1c2:1302:4536::b09a/128 On-link 10 266 2601:1c2:1302:4536:40a3:cf73:27b8:37bf/128 On-link 10 266 2601:1c2:1302:4536:c484:36de:43e9:e6fa/128 On-link 10 266 fe80::/64 On-link 11 306 fe80::/64 On-link 11 306 fe80::10fe:b93:e7eb:6c0c/128 On-link 10 266 fe80::c484:36de:43e9:e6fa/128 On-link 1 306 ff00::/8 On-link 11 306 ff00::/8 On-link 10 266 ff00::/8 On-link =========================================================================== Persistent Routes: None NSLookup for tower 10.0.0.131 returns "DNS request timed-out". ifconfig eth0 shows the address as 10.0.0.131 with submask 255.255.255.0, and gateway of 10.0.0.1 At this point I don't really know where to go. I'm not really sure how rebooting my modem could have caused this much of a mess.