Pushbullet - Websocket error - call to SSPI failed

[KARY]

but Pushbullet + IFTTT still not working

[RobLatour]

Ran a check this morning (6:30 est) and Pushbullet (and with it Push2Run) are working normally again.

[bigboss97]

It's working perfectly now

I was an unlucky one, it fails on my first trial. I also made one mistake, I googled "push2run websocket error" and I didn't land here. I found some other sources and tried reboot etc. At the end I was frustrated. Until the next day, I went back to push2run website and looked carefully. So I found this forum.

Anyway, great software and forum. I love it and super thanks to the creator!

[zexor]

Is anyone still having problem? It was working again yesterday, then there was a pushbullet update. Now it stopped working again.

[thewizkid95]

Just set up Push2Run and created a new pushbullet account all for the first time, but I seem to be having this issue still. Opened Windows firewall and rebooted as well but nothing seems to work. Are others still having the SSL issue?

[aurelbdx]

Pushbullet doesn't work again with the same error

[jasoncollege24]

pushbullet itself seems to be working fine. I'm getting all of it's notifications, but that doesn't mean that this problem isn't on their end, because I was getting all of it's notifications when this problem started the first time.

[pauk]

Still getting the same issue as listed in the original topic start as well

[RobLatour]

Yes, as of last night, the problem experienced over the weekend has re-materialized.

More specifically Push2Run, using the Pushbullet API, cannot connect - as with the last time it gets a websocket error.

I've notified Pushbullet by e-mail, and posted to their Reddit forum.

[jasoncollege24]

i left a message on their reddit. They say that they're requiring TLS 1.2 for all websocket connections as of yesterday. If push2run is setup to use an older version, then an update to 1.2 is required to make everything work smoothly again. Hope this helps