mbc0 Posted March 3, 2023 Share Posted March 3, 2023 I am having problems on "first" boot where my docker contairs cannot talk to each other (i.e. radarr to sabnzbd)  Test was aborted due to an error: Unable to connect to SABnzbd, Error: ConnectFailure (No route to host): 'http://192.168.0.53:8080/api?mode=get_config&apikey=**intentionally deleted**&output=json'  This happens EVERY time I reboot the server until I reboot again and then everything is great until I need to reboot again.   Can anyone please help?   unraid1-diagnostics-20230303-0913.zip Quote Link to comment
Squid Posted March 3, 2023 Share Posted March 3, 2023 So if you restart Radarr it does work? Change the startup order in the docker tab and have Sab starting first and add in a delay after it starts (all advanced view) Quote Link to comment
mbc0 Posted March 3, 2023 Author Share Posted March 3, 2023 49 minutes ago, Squid said: So if you restart Radarr it does work? Change the startup order in the docker tab and have Sab starting first and add in a delay after it starts (all advanced view)  If I restart Radarr and Sabnzbd I still have the communication problem, the only way I have found to resolve is to reboot again. Quote Link to comment
mbc0 Posted March 3, 2023 Author Share Posted March 3, 2023 @Squid Leaving Sab running I can restart Radarr, Sonarr, Lidarr and still none of them can connect to Sab, the only way I have found to get them communicating again is to reboot the server for a 2nd time. Quote Link to comment
mbc0 Posted March 3, 2023 Author Share Posted March 3, 2023 @Squid  I can confirm just by stopping and starting the array everything is now working rather than a full reboot. I imagine that if I had stopped and started the docker engine I would have had the same result? I have been putting up with this for a good 6 months+ but thought I would ask about it today, any ideas? Quote Link to comment
itimpi Posted March 3, 2023 Share Posted March 3, 2023 Have you tried changing the start order in the docker tab and where appropriate adding delays between docker starts to allow any dependencies to complete initialising before whatever tries to use them? 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.