Then I copied server.pvk back onto the Linux machine and ran mono’s $ httpcfg -list That essentially turned a base64 key into a binary key… I don’t think the original one had a password on it. On a windows box: pvk -in server.key -topvk -nocrypt -out server.pvk Thanks for the suggestions… I’ve done the following, and unfortunately, no change occurred. Running that same openssl command on another port on my box that uses the same SSL cert, and the output is MUCH different… streaming the certificate, and cert description, TLSv1.2, etc… Something is wonky with nzbdrone… Perhaps TLSv1 isn’t supported anymore… SSL handshake has read 7 bytes and written 0 bytes This was interesting output… 9898 is my nzbdrone SSL port now… I swapped it… 8989 is non-ssl… This is what openssl has to say about it, even though Chrome can access it just fine… though it does pop up a cert auth box… # openssl s_client -host -port 9898ġ39875413264032:error:140790E5:SSL routines:SSL23_WRITE:ssl handshake failure:s23_lib.c:177: 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. 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. I typically hit cancel at that screen and then it prompts me for HTTP basic authentication. However, when I load up in Chrome, it happily connects but prompts me with a “Select a certificate” pop up. ![]()
0 Comments
Leave a Reply. |