Bug Fix: Phantom Characters in SSL Certificate Hash

Hey Guys -

This isn’t exactly a feature request, but didn’t see a section for bugs - sorry if I missed it.

This issue has been around for a while so wanted to add it. If the bug can’t easily be fixed, I understand. Just wanted to bring it up, though. I made a small addition to the NZBDrone SSL Wiki page and notes for it are below, too.

I had a ton of trouble getting SSL to work with NZBDrone after a recent OS re-install. I dug deep into troubleshooting and spent at least 3 hours on it. I knew my certificate (3rd party) was good - but still couldn’t figure it out. Even though I followed the steps on the Wiki exactly, it failed each time!

Bug Characteristics

  • When following steps on the NZBDrone Wiki to add SSL, SSL wouldn’t work as each time the app started, it would still only work in HTTP - not HTTPS
  • In the log file, the “netsh” command which tries to add the site has a “?” character in front of the cert hash
  • The “config.xml” file (plain text) still shows the key as being correct - without a “?” preceding the cert hash

The Cause / Reproducing Issue
When following the wiki steps, I highlighted the certificate’s hash, copied, then pasted into NZBDrone. After failing the first time, I went back and removed spaces which still didn’t work.

The Resolution / Fix
I followed the below steps:

  1. Opened NZBDrone in browser and went to Settings / General
  2. I turned SSL Off, saved, then went to System and clicked Turn Off icon in upper right
  3. Started NZBDrone again and went back to Settings / General
  4. Enabled SSL, then deleted all characters from the certificate has field
  5. I manually typed the certificate has (no spaces) instead of pasting it
  6. I saved, then went to System and clicked Turn Off icon in upper right
  7. I started NZBDrone as Admin via the Start Menu

It worked!

I just made a small edit to the Wiki which added a note in between steps suggesting it be manually typed instead of copy/paste as I’ve found out there are many who have run into this before. Hope that’s ok

Thanks for all your hard work!

This issue was already fixed in develop, I mentioned that in my last post in your other thread and I updated the WIKI to match the change.