Archives 2014

Getting the “Pushbullet Notification Failed” error from your SickBeard notifications?  Well, the fix is simple, and here is what you have to do:

1) Find pushbullet.py in your SickBeard install directory.  For me, this file was located in:

/volume1/@appstore/sickbeard-custom/var/SickBeard/sickbeard/notifiers

2) Open that file in your editor of choice, for me that is vi, and make the following change:

Find:

if method == ‘POST’:
uri = ‘/api/pushes’
else:
uri = ‘/api/devices’

And change to:

if method == ‘POST’:
uri = ‘/v2/pushes’
else:
uri = ‘/api/devices’

Note that the devices uri doesn’t change, you just need to update the pushes uri.  I could dig in to the in’s and out’s of the Pushbullet API if I really felt like figuring out why this changed, but I don’t really care that much.  I just wanted to get my notifications working again.

3) Write and Quit the changes and then restart SickBeard.  This will recompile your changes in the python code and then hop in to your notifications and send a test message to make sure that worked.

That fixed it for me! Happy Pushbulleting 🙂

UPDATE 9/14/2014: Well, Something broke again.  I couldn’t figure out what (I think it has to do with the JSON body but I didn’t feel like rewriting something that’s been fixed elsewhere), so I snagged the latest pushbullet.py from the troubled SickRage project and used that instead.  Note, I had to switch the devices uri back to the /api/devices value because the /v2/devices value doesn’t work for me for some reason.  Hopefully this doesn’t break again :-\

Time flies when you’re a new Dad. Making time for old hobbies takes a quick back seat when you have a kid. To people without children, it may be seen as “your life is over” or you don’t want to hang out with them any more or some other similar nonsense. Why nonsense? Because that’s what it is. Life is far from over, and in a sense it is just beginning. Your hobbies might get put on hold for a bit, but it’s not really that big a deal because when you have a child, your child comes first because that’s what you want. It’s hard to explain, but you just know that you would do anything for your little one, and if that means putting hobbies or other things on hold for a while, so be it. If that means spending money on things you don’t want or spend time doing things you’d rather not, that’s fine as long as it’s for your child.  And you’re OK with that. Amelia is 21 months old… And it is wild how the past 2 years have flown, and how much she has changed, as well as I have changed. What I have found though is that the little one will be far more satisfying than any hobby out there. The first time they call you Dada (or Mama) is just amazing.

It’s scary when you’re getting ready to have your first child. “I don’t know what I’m doing!” and “What do I do when this happens??” type of thoughts easily fill your mind. All I can say is that it all comes one day at a time, and there will always be people willing to help you. It may seem overwhelming to think about it, but in reality, it’s not because it all is just one day at a time. You’re not having a 6 year old to take care of. You’re having a baby. Your home doesn’t even need baby-proofed yet (but it will soon). If you need a night out, someone in your family is surely ready to spend some alone time with the squirt. If you have a question, ask your parents, your friends with kids, or even just ring up your doctor.

It’s not all easy, as there are plenty of frustrating or scary times, but getting through those is part of the challenge of parenthood and what makes it far more rewarding than any other hobby. When I was younger I never really saw myself with kids as I just didn’t think much about it. But now that I have daughter, she is easily one of the best things to ever happen to me and I can’t imagine life without her.

I have friends in just about all stages of parenthood it seems. Some have kids, some getting ready to have kids, some who will have kids in the future, and some with no plans to have kids at all. You’re all my friends and I wish I had time to hang out with all of you every weekend, but the little ones soak up the free time. Would I rather be out riding, grabbing a beer, or playing with my daughter? I’ll pick daughter any day. At least until she hits those teen years where she hates me. Not looking forward to those, but one day at a time. Right?

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/ssl

Andromeda> cp ssl.crt/server.crt /usr/local/sickbeard-custom/var/server.crt

Andromeda> cp ssl.key/server.key /usr/local/sickbeard-custom/var/server.key

Andromeda> cd /usr/local/sickbeard-custom/var

Andromeda> chown sickbeard-custom server.crt

Andromeda> 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!