Sonarr version (exact version): 2.0.0.5252
Mono version (if Sonarr is not running on Windows):
OS: Win10 1803
Debug logs:
Description of issue: “Suddenly” Sonarr won’t connect to NAS using IP addresses, only hostnames
Suddenly 2 days ago, Sonarr started reporting that the connection to my download client was unavailable. The only log msg was “Unable to retrieve queue and history items from Sabnzbd NAS via etc hosts name” and the episode download job just sat in the Activity queue pending. A manual test of the download client connection also timed out.
My sabnzbd client runs on my synology NAS which is on my LAN (same subnet as my Sonarr box) and I could connect to it and download files manually so no problem there. After a LOT of changing settings, re-installing Sonarr and dropping back to a very basic setup I’ve found that entering an IP address in the host field of the download client dialog no longer works and it must be DNS name. I had to create an entry in my Windows hosts file and use that. Having fixed that, I then also discovered that my Remote Path Mapping entry, which also uses an IP address, also had to now be changed to a DNS name.
My system has been working seamlessly for over a year using the IP address entries so I’m at a loss about why it’s suddenly stopped. Has anyone else experienced anything similar and know why this happens?
thnx
Webby