System.Net.WebException: The operation has timed out at System.Net.HttpWebRequest.GetResponse() at NzbDrone.Common.Http.Dispatchers.ManagedHttpDispatcher.GetResponse(HttpRequest request, CookieContainer cookies) in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Common\Http\Dispatchers\ManagedHttpDispatcher.cs:line 95 at NzbDrone.Common.Http.Dispatchers.FallbackHttpDispatcher.GetResponse(HttpRequest request, CookieContainer cookies) in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Common\Http\Dispatchers\FallbackHttpDispatcher.cs:line 53 at NzbDrone.Common.Http.HttpClient.ExecuteRequest(HttpRequest request) in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Common\Http\HttpClient.cs:line 119 at NzbDrone.Common.Http.HttpClient.Execute(HttpRequest request) in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Common\Http\HttpClient.cs:line 55 at NzbDrone.Common.Http.HttpClient.Get[T](HttpRequest request) in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Common\Http\HttpClient.cs:line 225 at NzbDrone.Core.MetadataSource.SkyHook.SkyHookProxy.GetSeriesInfo(Int32 tvdbSeriesId) in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Core\MetadataSource\SkyHook\SkyHookProxy.cs:line 40 at NzbDrone.Core.Tv.RefreshSeriesService.RefreshSeriesInfo(Series series) in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Core\Tv\RefreshSeriesService.cs:line 57 at NzbDrone.Core.Tv.RefreshSeriesService.Execute(RefreshSeriesCommand message) in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Core\Tv\RefreshSeriesService.cs:line 166
Sonarr version (exact version): Mono version (if Sonarr is not running on Windows): OS: ((Debug logs)): (Make sure debug logging is enabled in settings and post the full log to hastebin/pastebin/dropbox/google drive or something similar, do not post them directly here)
The ((debug logs)) will show the exact URL Sonarr is trying to load and more details on the failure. If you’re running Sonarr on Windows checking that URL in Edge/IE11 is the closest you can get to testing it through the same proxy (if set) that Sonarr would be using.
This would be Running on Windows 10 running Master 4949 (Current)
This was working fine as far as i am aware up for a good few months ago,
I cannot Add Shows, Update from Disk,
Stuff that gets Auto Downloaded Appears to be working fine and dropping into the Correct folders, however, the Usual Tasks are failing,
If you could kindly give me an insight into what is going on, that would be great.
Firewall is not blocking the Connections as i can Ping to that Host and get a response, and i have Allowed Sonarr full Access through the Firewall.
Sonarr is also not Running as “Service” in this case either.
I have checked the Folder Permissions and it appears that the “Logged on User” Can Access the Local Disk’s connected to the Machine perfectly fine.
Ping and web connections use different protocols, it’s possible for one to be blocked, but not the other (unlikely in this case).
Get the URL from the debug logs, does that URL work in IE11 and Edge?
This doesn’t have anything to do with local disk permissions, something network related either on your system (proxy, firewall, etc) or possibly with your ISP/Cloudflare.
Yes, this could be the case! anything is possible.
Looking through the Logs, i cannot seem to find a testable URL, Could you Guide me through how to Acquire this from the Logs somewhere or Provide a TEST URL?
SNIPPET: {“tvdbId”:311787,“title”:“24: Legacy”,“overview”:“Story follows a military hero’s”
Of course, a ton more Data, now, i may know of a Reason, does Sonarr for any reason use the Local Machines Web Browser for anything in relation to the above?
As for some strange reason, i can Access this URL from my Tablet (Connecting to it from work)
But the NAS its on, IE/Edge seem buggered and wont load any web pages, Does Sonarr rely on these for any given reason?
Its strange as stuff can Download via Usenet and the like.
It doesn’t use the browser exactly, but the .net framework (which Sonarr is built on), uses a very similar path to retrieve web requests that IE11 does (and presumably Edge as well).
If you’re having issues with those browsers as well, it could be something simple like a bad proxy configuration (you can edit that in Internet Options in IE) or something else. Probably easiest to start with getting the browser working and Sonarr should fall in line afterwards.
Seems we are fully Resolved this end, it may of been a few factors. but IE/Edge was able to load Random Websites at which point, Sonarr was also able to Index/Scan and the like.
Very odd issue, but now since resolved.
Just wish to thank you for your time & help! seems Sonarr has a Great support Team! Keep up the good work.
If you need anyone with Technical Background in 2nd/3rd Line Support let me know!