Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About brawny

  • Rank
  • Birthday September 5


  • Gender
  • Location
    London, Ontario, Canada

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Problem resolved. I had not restarted Unraid, but we had a thunderstorm last night, and the power went out. I don't have my server on a UPS yet, so it power cycled. The root cause was a misconfiguration in the proxy port for Sonarr. I had it set for 8181 instead of 8118. Comparing the configuration data between Sonarr and Radarr helped me find it. I think there was an issue with pihole initially, and restarting Unraid would have resolved the issue, but because I removed/reinstalled/reconfigured Sonarr - and didn't have the proxy port set correctly, restarting Unraid didn't resolve the issue. I'm good to go now - all dockers are working properly. Thanks for your help with this! Brawny
  2. Hoping this is the right place to post this. I'm new to Unraid and Docker, as well as Sonarr. I am using Sickbeard on an older server still, and in the process of migrating to a new Unraid server. The story to date: I've successfully installed Unraid 6.7.0, and configured it successfully, using Spaceinvader One's videos when needed. I've installed Community Apps, and the following Dockers in this order: binhex-krusader LogitechMediaServer binhex-sabnzbdvpn binhex-radarr binhex-sonarr binhex-lidarr binhex-plex musicbrainz pihole Everything worked properly until some time shortly after deploying pihole. I'm now getting an error - but only from sonarr about connectivity: System.Net.WebException: Error: ConnectFailure (Connection refused): 'http://services.sonarr.tv/v1/update/master/changes?version=' ---> System.Net.WebException: Error: ConnectFailure (Connection refused) ---> System.Net.Sockets.SocketException: Connection refused at System.Net.Sockets.SocketAsyncResult.CheckIfThrowDelayedException () [0x0003b] in /build/mono/src/mono/mcs/class/System/System.Net.Sockets/SocketAsyncResult.cs:134 at System.Net.Sockets.Socket.EndConnect (System.IAsyncResult asyncResult) [0x0002c] in /build/mono/src/mono/mcs/class/System/System.Net.Sockets/Socket.cs:1150 at System.Net.Sockets.SocketTaskExtensions+<>c.<ConnectAsync>b__2_1 (System.IAsyncResult asyncResult) [0x00000] in /build/mono/src/mono/mcs/class/System/System.Net.Sockets/SocketTaskExtensions.cs:35 at System.Threading.Tasks.TaskFactory`1[TResult].FromAsyncCoreLogic (System.IAsyncResult iar, System.Func`2[T,TResult] endFunction, System.Action`1[T] endAction, System.Threading.Tasks.Task`1[TResult] promise, System.Boolean requiresSynchronization) [0x00019] in /build/mono/src/mono/external/corert/src/System.Private.CoreLib/src/System/Threading/Tasks/FutureFactory.cs:538 --- End of stack trace from previous location where exception was thrown --- Screenshot of most recent System/Status/Logs tab: I suspect that something network-related is misconfigured either in sonarr, or pi-hole, but I'm not sure what that could be. Steps I've taken so far: Remove pihole as my DNS server on my router (Unifi USG). No change. Restart sonarr. No change. Remove sonarr and re-install. No change. Pihole seems to be working properly, as do sabnzbdvpn, radarr and plex, and all other devices on my lan. Any suggestions on troubleshooting would be really appreciated. Thanks! Brawny