Indexer issues synolgy

#1

Havent seen anything recent to these issues but im running synolgy (latest version)

Sonarr has been great till a few days ago when i moved house (box been offline for a week)

here is error log

18-6-5 00:20:47.1|Warn|Newznab|Unable to connect to indexer

[v2.0.0.5085] System.Net.WebException: DNS Name Resolution Failure: ‘api.nzbgeek.info’
at NzbDrone.Common.Http.Dispatchers.ManagedHttpDispatcher.GetResponse (NzbDrone.Common.Http.HttpRequest request, System.Net.CookieContainer cookies) [0x0015e] in <28afedda32c5499dab128da6b50bbb86>:0
at NzbDrone.Common.Http.Dispatchers.FallbackHttpDispatcher.GetResponse (NzbDrone.Common.Http.HttpRequest request, System.Net.CookieContainer cookies) [0x0003c] in <28afedda32c5499dab128da6b50bbb86>:0
at NzbDrone.Common.Http.HttpClient.ExecuteRequest (NzbDrone.Common.Http.HttpRequest request) [0x0007e] in <28afedda32c5499dab128da6b50bbb86>:0
at NzbDrone.Common.Http.HttpClient.Execute (NzbDrone.Common.Http.HttpRequest request) [0x00000] in <28afedda32c5499dab128da6b50bbb86>:0
at NzbDrone.Common.Http.HttpClient.Get (NzbDrone.Common.Http.HttpRequest request) [0x00007] in <28afedda32c5499dab128da6b50bbb86>:0
at NzbDrone.Core.Indexers.Newznab.NewznabCapabilitiesProvider.FetchCapabilities (NzbDrone.Core.Indexers.Newznab.NewznabSettings indexerSettings) [0x0009a] in :0
at NzbDrone.Core.Indexers.Newznab.NewznabCapabilitiesProvider+<>c__DisplayClass4_0.b__0 () [0x00000] in :0
at NzbDrone.Common.Cache.Cached1[T].Get (System.String key, System.Func1[TResult] function, System.Nullable1[T] lifeTime) [0x0006a] in <28afedda32c5499dab128da6b50bbb86>:0 at NzbDrone.Core.Indexers.Newznab.NewznabCapabilitiesProvider.GetCapabilities (NzbDrone.Core.Indexers.Newznab.NewznabSettings indexerSettings) [0x00046] in <ab54b7a85b364e7591653180d377c256>:0 at NzbDrone.Core.Indexers.Newznab.Newznab.get_PageSize () [0x0000c] in <ab54b7a85b364e7591653180d377c256>:0 at NzbDrone.Core.Indexers.Newznab.Newznab.GetRequestGenerator () [0x0000b] in <ab54b7a85b364e7591653180d377c256>:0 at NzbDrone.Core.Indexers.HttpIndexerBase1[TSettings].TestConnection () [0x00007] in :0

#2

DNS issues, make sure any static DNS servers are set correctly or set them to dynamic.

#3

In my new router (new place so new router) TP-Link vr600 I’ve set up dynamic dns to tp-link set up my domain name ect.

I’m just rebooting nas while we speak should that fix it?

#4

That’s dynamic DNS setup so you can use a domain to reach your router from outside your network, not internal services needing DNS to connect to websites/services.

Not if only what you said above was changed (you shouldn’t need to reboot to fix DNS at all), make sure the DNS servers your NAS is setup to use are correct for your router and/or ISP. Synology forums/documentation is probably the best to go to figure out what to do.

#5

Cheers mate got it working.

We had an extremely busy network at old place.

Found setting in Synology set it to auto but also as it still hag 192.168.2.1 greyed our needed to manually set it to 192.169.1.1

1 Like