Pushbullet - Websocket error - call to SSPI failed

[aaazzz123dummy]

Hi,
Push2Run is not able to connect to Pushbullet. It is giving below error messages in the logs.

2019-02-06 12:28:57.978 - Attempting to reconnect to Pushbullet
2019-02-06 12:28:58.244 - Websocket error
2019-02-06 12:28:58.310 - A call to SSPI failed, see inner exception.
2019-02-06 12:28:58.312 - Websocket closed

2019-02-06 12:28:58.333 - Connection with Pushbullet not established


Can anyone suggest how to get Pushbullet working again? It was working about a fortnight ago.
And now suddenly this error.
I am not able to figure out root cause of the issue.

Thanks in advance.

[RobLatour]

some things to look at / consider:

- what other software have you installed upgraded in that time?

- is your firewall blocking the push2run

- if you haven't used pushbullet in over 30 days, please try creating a new account and using a new pushbullet access token

[aaazzz123dummy]

I have been using Push2Run on and off for about a month.

I have not used Pushbullet separately as such.

In terms of software updates, my system had usual Windows software updates. Nothing new.

Not sure what might be causing this? Maybe some certificate issue?
Does Pushbullet provide any certificates?

[RobLatour]

I'm not sure, but if it was a certificate error with pushbullet it wouldn't be working for everyone else - which is not the case, because its still working for me.

If you haven't already, please try rebooting your system.

Also, did you try pausing your firewall for the duration of a test?

[zexor]

I am having the same problem since yesterday. Could it be a windows update?

[unknownguy18]

I'm experiencing the exact same problem right now.If anyone had a fix I'd be happy to know what it is.

[KARY]

For the last 3 months, everything worked great, but this morning a red icon appeared and the message "No connected to Pushbullet".
In the logs exactly the same:

Attempting to reconnect to Pushbullet
Websocket error
A call to SSPI failed, see inner exception.
Websocket closed

Connection with Pushbullet not established

I have not changed anything in recent days, I have not installed new programs or updates.
Can anyone help me restore work of Push2Run?

[WBB]

I am actually having the same issue. I have turned my firewall off and it still persists. Also, it's happening on two machines, one Win7 one Win10, both on the same network. Pushbullet says their outbound port is 443 and I don't think my ISP would block that all of a sudden, but aside from that I or Pushbullet not accepting the connection, I'm not sure what else it could be.

[RobLatour]

Yes, I have been getting the same since 2019-02-23 20:39:03.343 (EST) last night.

I sent the folks at Pushbullet a note thru their web request form here: https://www.pushbullet.com/support

I suspect something at Pushbullet’s end has changed - or their service is somehow down. I tried updating my Pushbullet access token but that did not help.

Also, the same issue is being reported on reddit here: https://www.reddit.com/r/PushBullet/com ... _computer/ but as far as I can see its not related specifically to Push2Run but to the Pushbullet service in general.

Will post back here, if I hear back from them.

Rob

[stormthirst]

OK - glad it's not just me then.