Unable to connect to indexer https://katproxy.top/

Sonarr version (exact version): 2.0.0.4146
Mono version (if Sonarr is not running on Windows): 4.2.3 (Stable 4.2.3.4/832de4b Wed Mar 16 13:19:08 UTC 2016)
OS: Ubuntu Server 16.04
((Debug logs)) (posted to hastebin or similar): http://pastebin.com/QEV1aeeR
Description of issue: I’m trying to add an Indexer using Kickass Torrents with the URL https://katproxy.top/ (which works in a browser) however Sonarr is unable to connect to indexer and refers me to check the logs. I’ve no success with the default URL or any of the others such as RARBG. It’s worth mentioning I’m in the UK so many sites are blocked so I have to use proxies.

Thanks in advance.

It can’t make an SSL connection, Sonarr will fallback to curl if available, but since it didn’t its not available.

Ah that’s a shame. Is there anyway around this problem? I can browse to https://katproxy.top/ from my desktop machine just fine, and the browser indicates it’s a secure connection with a certificate but I’m running Sonarr on a separate server box (ubuntu 16.04, transmissio, plex, and sonarr).

Any suggestions?

EDIT:

I’ve just downloaded Sonarr on my desktop machine and used https://katproxy.top/ and it works fine! So there must be a configuration issue on my server.

Setup curl (curlib I believe) so Sonarr can fallback to using that when it can’t make a connection using mono (because mono’s SSL support is severely lacking). Besides running Sonarr on a Windows system with .net 4.5 installed its the only option.

I have curl installed but is there anything specifically I would have to do to allow it to fallback to using curl?

Thanks,

Sonarr needs to be able to find the correct version of libcurl it needs, if you enable ((trace logging)) and restart Sonarr it will log with the message: Initializing curl failed and the details why it couldn’t be loaded.

I ran sudo apt-get install libcurl4-openssl-dev and that managed to resolve the issue!

Thanks for your help!

1 Like

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.