All The Sudden Sonarr/Radarr Cant Be Reached By Overseer

[brisk trail]

No changes on my end EXCEPT a new cable modem a few days ago (however unrelated to issue), and now I have just noticed that I overseer can no longer connect to radarr or sonarr.

2023-05-11 22:12:05.7|Debug|Radarr.Http.Authentication.NoAuthenticationHandler|AuthenticationScheme: None was successfully authenticated.

I get this in my Radarr log, saying 'none' was authenticated, is that typical? Most of the time i see API was authenticated, or SignalR.

In sonarr debug logs, I get

2023-05-11 22:18:12.4|Debug|Api|[GET] /api/v3/command: 200.OK (1 ms)

But all is not ok. These errors are in response to the Test button being used.
For Overseer Logs, i get

2023-05-11 22:22:00 2023-05-12T02:22:00.014Z [error][Download Tracker]: Unable to get queue from Radarr server: Radarr-Rackserver01```

And now after writing all this, I DO remember that I updated Docker Desktop to v4.19.0 a couple days ago, but when overseer started back up properly I didnt think to check any further. Possibly related. I can however communicate WITH overseer via webbrowser, so I dont know if there is some docker networking shenanigans at play. 

When in doubt, blame DNS right? Tried changing my the address from hostname to 127.0.0.1, didnt make a difference.

[abstract widget]

a simple test to rule out dns problems, try and configure communications using IPs instead of names

[brisk trail]

yup, did that no changes. also, overseer can communicate with plex and I can communicate with overseer via web browser using 127.0.0.1:5055 np on the local machine

[brisk trail]

ok wacky. so i tried the actual ethernet ip 192.168.8.166, and it works fine -_-

so something in the docker update must have changed something network related? works with ip address but not local hostname (pc name) or 127.0.0.1 anymore