I am having difficulties getting nzbToMedia talk properly to my SSL enabled nzbdrone port… It says it has trouble connecting to it. I SUSPECT it may be because nzbdrone appears to attempt to do a certificate level authentication process… or perhaps because the python SSL code doesn’t trust my StartCom SSL key… I tried modifying the code to not verify the SSL cert, but that doesn’t seem to help… and testing with curl (w/ -k to ignore the untrusted cert) seems to throw a connection failure message too.
I’m running latest of everything, AFAIK:
nzbdrone 184.108.40.2064 (on linux)
nzbToMedia commit c7d4160a06333aa99ebbefeacc0780dc7c84ec99 (latest one)
Curl test output from the local machine, and servername.removed.com resolves to the eth0 IP address, which nzbdrone is listening on:
[code]curl -v https://servername.removed.com:9898
- Rebuilt URL to: https://servername.removed.com:9898/
- Hostname was NOT found in DNS cache
- Trying 192.168.1.101…
- Connected to servername.removed.com (192.168.1.101) port 9898 (#0)
- successfully set certificate verify locations:
- CAfile: none
- SSLv3, TLS handshake, Client hello (1):
- SSLv3, TLS alert, Client hello (1):
- Unknown SSL protocol error in connection to servername.removed.com:9898
- Closing connection 0
curl: (35) Unknown SSL protocol error in connection to servername.removed.com:9898 [/code]
However, when I load up https://servername.removed.com:9898 in Chrome, it happily connects but prompts me with a “Select a certificate” pop up. I typically hit cancel at that screen and then it prompts me for HTTP basic authentication. Then I login and it works fine.
If I switch nzbToMedia in NZBGET to NOT utilize SSL for nzbdrone (and switch to the other non-ssl port), then the post processing script seems to work.
So, my long winded question is, what is causing the failure, and how can I use SSL w/o errors? And a side question of how I can either utilize or silence the certificate authentication pop up of nzbDrone.