Kendo Posted April 4, 2023 Share Posted April 4, 2023 (edited) Unraid Os 6.11.5 I was tinkering yesterday morning with Adguard Home and then Nginx and when I got home my Unraid box seemed to have crashed. I couldn't reach my Unraid server through the ip-webinterface nor putty-terminal. I had set up a virtual docker network and could still see that that was up (and could get into the wubgui of Adguard, Sonarr and Qbit-torrent). Plugging in a monitor and keyboard got no response. So I hard booted the server and it came back up with the Docker network address as it's IP interface. I did some digging and changed the network.cfg from: # Generated network settings USE_DHCP="yes" IPADDR= NETMASK= GATEWAY= BONDING="yes" BRIDGING="yes" to # Generated network settings USE_DHCP="no" IPADDR="192.168.1.238" NETMASK="255.255.255.0" GATEWAY="192.168.1.254" BONDING="yes" BRIDGING="yes" And now I can connect on its original IP (238) but the containers don't talk to each other eg Sonarr, Prowlarr and Qbittorrent), the Myservers is down (I'm getting the API/cant reach mothership error message) and the CA interface is also unreachable. Help, I'm not expert with DNS/routing and its twisting my head somewhat.... (btw and can turn AdGuard Home on and off (and change settings in the router) but that doesn't seem to fix anything. I've also run the unraid-api restart command which doesnt seem to do anything. Many thanks if you can point me in the right direction. tower-diagnostics-20230404-0603.zip Edited April 4, 2023 by Kendo Quote Link to comment
Solution Kendo Posted April 5, 2023 Author Solution Share Posted April 5, 2023 Sorted this last night. Problem closed. Quote Link to comment
Recommended Posts
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.