I have been working on getting SickBeard setup on my Synology DS1512+ NAS, and I’ve got pretty much everything worked out. One of the final things I wanted to get working properly was https support with my self signed certificate I setup for my Synology. I know, not really very important since I’ll only ever access it over my lan or via a VPN, but still… I went through the trouble of getting the self signed certificate working on my Synology, I wanted it to work here too. It was a little tricky in a couple of regards.
First, I had to get it to use my certificate and key. I tried linking straight to the existing ones the Synology uses in /usr/syno/etc/ssl sub-directories but SickBeard just refused. I figured it was a permission issue since those certs were owned by root only. I decided the easiest way was to just copy over the 2 files I needed in to SickBeard’s directory and switch their owner:
Andromeda> cd /usr/syno/etc/sslAndromeda> cp ssl.crt/server.crt /usr/local/sickbeard-custom/var/server.crtAndromeda> cp ssl.key/server.key /usr/local/sickbeard-custom/var/server.keyAndromeda> cd /usr/local/sickbeard-custom/varAndromeda> chown sickbeard-custom server.crtAndromeda> chown sickbeard-custom server.key
Then alas I was able to put in server.crt and server.key in SickBeard, restart it and it used my certs! Woot!
I was pretty happy with myself until I clicked the SickBeard shortcut in the Synology menu and was greeted with my second issue:
The client sent a plain HTTP request, but this server only speaks HTTPS on this port.
Oh you son of a…
I’m way too anal about my things all working properly to live with that atrocity, so after a minute of poking around I quickly found the config for it the following file: /usr/local/sickbeard-custom/app/config
Pop that file open in vi and change the protocol line from http to https. Save and quit, then simply reload your Synology web interface, and bam! Your shortcut will work once again, launching Sickbeard via https! Yay!