I’m adding this entry here, but please let me know if I need to start a new thread. I looked for ‘NamedResolutionFailure’ in the debug log, but didn’t see any occurrences of it, so I think it’s a different issue? It should be noted that this error started yesterday when I upgraded Sonarr (Updating Sonarr from version 2.0.0.4472 to version 2.0.0.4855). Any insight would be greatly appreciated! It should be noted, I have someone’s personal indexer which doesn’t throw this issue, however I get this error both for oznzb.com and nzbgeek.info; these indexers all work in CouchPotato.
If it turns out this a bug in the latest Sonarr version, is it possible to go back a version until it’s resolved?
The second post in that thread links to a reddit post (with a solution). After going to that reddit post (https://www.reddit.com/r/sonarr/comments/6b3ifc/sonarrs_crashing_because_of_something_to_do_with/), the very top EDIT commend says that the latest version of Sonarr resolves this issue? I will test using this switch in sonarr.service and see if it makes a difference. I’ll report back shortly.
EDIT:
Ok, so appears that this may be a slightly different bug, as latest version of Sonarr does not resolve the issue, however MONO_TLS_PROVIDER=legacy does resolve the issue. Thanks markus101!
This is what I did for CentOS v7.x
Edit /usr/lib/systemd/system/sonarr.service
And add under [Service] the following line: Environment=MONO_TLS_PROVIDER=legacy
Save and exit
systemctl daemon-reload
service sonarr restart
Test Indexer and it now works