Trying to add an indexer

Yonder · March 13, 2015, 7:27pm

15-3-13 15:17:38.9|Debug|Newznab|Downloading Feed https://www.althub.co.za/api?t=tvsearch&cat=5030,5040,5070&extended=1&apikey=&offset=0&limit=100
15-3-13 15:17:38.9|Trace|HttpClient|Req: [GET] https://www.althub.co.za/api?t=tvsearch&cat=5030,5040,5070&extended=1&apikey=&offset=0&limit=100
15-3-13 15:17:39.0|Warn|Newznab|Unable to connect to indexer: Error: SendFailure (Error writing headers)

nmatrix migrated. Trying to add the new url.

CBers · March 13, 2015, 8:02pm

Did you test whilst adding it?

I did exactly the same earlier and it added OK.

Also, there’s no API key in the url above, unless you’ve removed it on purpose.

markus101 · March 13, 2015, 10:06pm

This is a known issue, they’re using CloudFlare for SSL, which at the free level doesn’t work for Sonarr. At best we’d only ever be able to get it working on Vista (server 2008)+ and not on *nix since they don’t support the TLS version that CloudFlare uses.

neo · March 17, 2015, 7:25pm

altHUB admin here.
Just wanted to let you guys know I’ve made some changes to our security setup, my tests with Sonarr have proved successful Please let me know if it’s working.

@markus101 New around these parts, nice looking forums you have! Excuse my ignorance around .NET, but will Sonarr look at using a more modern SSL cipher for handshakes?

Yonder · March 17, 2015, 7:44pm

Still not working for me. Maybe give it time for my DNS to purge?

markus101 · March 17, 2015, 10:20pm

Its a bit of a confusing mess to be honest.

There are a couple issues that have held us back from better support, one affecting Windows users and the other affecting non-Windows (Linux/Unix/OS X).

The first is solved by upgrading Sonarr to use .net 4.5, but thats a breaking change for anyone running Windows XP (.net 4.5 is not supported) or didn’t install .net 4.5, this is something we want to do for v3 of Sonarr (sticking to breaking changes in major updates only), but this only solves the problem for Windows users.

For non-Windows the issue is more complicated, its limited by mono (and the lack of TLS 1.1/1.2 support), sounds like they have made progress on it, but its not available yet: http://mono.1490590.n4.nabble.com/Open-source-Net-and-TLS-1-1-amp-1-2-td4664941.html

neo · March 18, 2015, 10:09am

Please try again, some further tweaks where made earlier. DNS should also have fully resolved now.

neo · March 18, 2015, 10:10am

markus101:

Its a bit of a confusing mess to be honest.

There are a couple issues that have held us back from better support, one affecting Windows users and the other affecting non-Windows (Linux/Unix/OS X).

The first is solved by upgrading Sonarr to use .net 4.5, but thats a breaking change for anyone running Windows XP (.net 4.5 is not supported) or didn’t install .net 4.5, this is something we want to do for v3 of Sonarr (sticking to breaking changes in major updates only), but this only solves the problem for Windows users.

For non-Windows the issue is more complicated, its limited by mono (and the lack of TLS 1.1/1.2 support), sounds like they have made progress on it, but its not available yet: http://mono.1490590.n4.nabble.com/Open-source-Net-and-TLS-1-1-amp-1-2-td4664941.html

I figured it was all a bit messy. From what I looked into, .NET and SSL is proper confusing. I’m no .NET Dev though Anyway, our setup should be compliant again. Looking forward to the changes on v3!