June 29, 20224 yr Kinda at a loss with this issue. I recently installed 2 new drives and had a cable seating problem causing one of the drives to get corrupted, after fixing the cable and rebuild this new issue popped up. So far I've tried rebooting, setting the IP to static (which allowed me to access the docker apps by ip again), and updating to the latest UnRAID, I've also tried accessing it from different devices and browsers. It's clearly not a routing issue so I can only assume some issue with unRAID. ping mediatower Pinging MediaTower.local [192.168.1.139] with 32 bytes of data: Reply from 192.168.1.139: bytes=32 time<1ms TTL=64 Reply from 192.168.1.139: bytes=32 time<1ms TTL=64 Reply from 192.168.1.139: bytes=32 time<1ms TTL=64 Ping statistics for 192.168.1.139: Packets: Sent = 3, Received = 3, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms ping 192.168.1.139 Pinging 192.168.1.139 with 32 bytes of data: Reply from 192.168.1.139: bytes=32 time<1ms TTL=64 Reply from 192.168.1.139: bytes=32 time<1ms TTL=64 Reply from 192.168.1.139: bytes=32 time<1ms TTL=64 Reply from 192.168.1.139: bytes=32 time<1ms TTL=64 Ping statistics for 192.168.1.139: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms mediatower-diagnostics-20220629-0846.zip
June 29, 20224 yr Solution According to the diagnostics, the server's IP is 192.168.1.138, not 192.168.1.139 You don't have SSL setup, so the urls would be: http://192.168.1.138 http://MediaTower.local
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.