Sonarr cannot connect to DOGnzb anymore

[EDOM]

Sonarr version (exact version): 2.0.0.4724
OS: Windows 10 Pro
((Debug logs)): https://drive.google.com/file/d/0ByIiqWuqmRevc3U4Znd3VHY4cVE/view?usp=sharing
Description of issue:
Sonarr cannot connect to DOGnzb anymore.
It worked fine, it ran stable for months.
But now it cannot connect anymore.
I tried restarting Sonarr.
I tried removing DOGnzb and adding it again: I can’t because the connection always fails.
I triple checked all APIs and URLs and everything…
What’s wrong?
Please help!
(P.S.: I already tried to solve that issue at the DOGnzb forum (https://dognzb.cr/board/index.php?/topic/3628-sonarr-cannot-connect-to-dognzb-anymore/). They say the problem looks to them like I need to contact Sonarr support.)

[markus101]

Sonarr can’t connect to the site, either something on your system is preventing the connection or something on their end is blocking it.

Can you connect from IE11 and Edge (on the system running Sonarr)?
Can you test from another computer on the same network?
Have you recently installed or updated a Firewall or Anti-Virus software?

[EDOM]

Hmm…
I tried to ping their system and that is what I got:

> C:\Users\svens> ping api.dognzb.cr

> Ping wird ausgeführt für api.dognzb.cr [190.10.14.167] mit 32 Bytes Daten:
> Antwort von 190.10.14.130: Zielnetz nicht erreichbar.
> Antwort von 190.10.14.130: Zielnetz nicht erreichbar.
> Zeitüberschreitung der Anforderung.
> Antwort von 190.10.14.130: Zielnetz nicht erreichbar.

> Ping-Statistik für 190.10.14.167:
>     Pakete: Gesendet = 4, Empfangen = 3, Verloren = 1
>     (25% Verlust),

I tried the same from another pc within my home network: same results.
No, I have not recently installed or updated a Firewall or Anti-Virus software.

So whose fault is it?

[markus101]

A 25% loss isn’t great, though I’m seeing a 100% loss, so ping may not be the best way to test it, though the fact that a ping is failing some of the time indicates there is a problem beyond Sonarr.

Are you using a proxy or VPN with Sonarr?

@EDOM

So whose fault is it?

I’m able to connect to DogNZB from Sonarr without issue, so it seems limited to your setup and the fact that there isn’t a number of people with the same issue coincides.

Are you able to run Sonarr on another system on your network to see if it also has issues? That would help narrow down whether it’s limited to one system or your network.

[EDOM]

Thanks a lot for your input and your patience! Very much appreciated!

Meanwhile I found out tha it might have something to do with the DNS.
I resolved to 90.10.14.167 instead to 190.10.14.168.
I did not hardcode anything, but somewhere it is getting the wrong IP address.
I will dig deeper and try to find where and why.
But for now it helped to just have https://190.10.14.168 instead of api.dognzb.cr:
It works again.

I will report back when I find out where it gets the 167…
Thanks a lot again!