Push2Run 2.1.2 Not Connecting to Pushbullet

[dubs100]

Hello, I'm trying to set up push2run for the first time and having trouble connecting to Pushbullet. My session log can be found at the end. I'm running windows 7. I'd appreciate any help. This SW is exactly what I've been looking for!

• I've deleted and created a new pushbullet account

• I've recreated the access token several times (side question, the pushbullet access token always starts with "o.". When you click the token it only highlights the characters after the "o.". Should that be included in the token or not?
  I've tried it both ways several times.

• I can access this: https://stream.pushbullet.com/

• I verified I'm running 2.1.2

• I installed version 4.6.2 of Microsoft's dot net framework

• I've restarted several times

Session log:
2019-03-27 17:40:54.381 - Started

2019-03-27 17:40:54.551 - Current network adapter is Local Area Connection 3

2019-03-27 17:40:54.621 - Network status is up

2019-03-27 17:40:55.231 - Websocket error
2019-03-27 17:40:55.261 - A call to SSPI failed, see inner exception.
2019-03-27 17:40:55.281 - Websocket closed

2019-03-27 17:40:55.281 - Connection with Pushbullet not established

2019-03-27 17:40:56.291 - Attempting to reconnect to Pushbullet
2019-03-27 17:40:56.361 - Websocket error
2019-03-27 17:40:56.391 - A call to SSPI failed, see inner exception.
2019-03-27 17:40:56.391 - Websocket closed
2019-03-27 17:40:56.391 - Connection with Pushbullet not established


2019-03-27 17:41:06.296 - Attempting to reconnect to Pushbullet
2019-03-27 17:41:06.366 - Websocket error
2019-03-27 17:41:06.396 - A call to SSPI failed, see inner exception.

[RobLatour]

Regarding the "o." - yes its part of the access token and needs to be included.

Not sure why you are getting these errors. PushBullet was having problems earlier today, or at my logs were showing problems, starting about 10:43 am (est) and going for about 5 minute - but after that it has been fine.

Perhaps you can try turning off your antivirus / firewall for the period of time to do a quick test to see if that has anything to do with it?

Also, do you have a Windows 10 machine on the same network you can test with?

[Tannon]

Just chiming in that I still have the exact same issues as the original poster here. Also running Windows 7. This problem started right around when PushBullet made their changes that required the update to 2.1.2. Something there must be the issue.

[RobLatour]

Try following these instructions to enable TLS 1.2 on Windows 7
https://manage.accuwebhosting.com/knowl ... ows-7.html

Please let me know if this helps

(and btw there is a new version of Push2Run now available v2.2 - which corrects the restart looping issue when UAC is turned off on Windows 7)

[Tannon]

Unfortunately that did not seem to help. I modified the registry as suggested, shown here:

https://i.imgur.com/bwaDJTf.png

I still get the exact same log from Push2Run after restarting.

[RobLatour]

I found this article
https://support.microsoft.com/en-ca/hel ... cols-in-wi
which also says:

To apply this update, you must install Service Pack 1 for Windows 7 or Windows Server 2008 R2.

Here is an article that describes Service Packs
https://www.lifewire.com/latest-windows ... es-2624595
and includes links for them.

If you don't already have the SP 2 installed, can you install it, reboot, and let me know if that helps.

[rwe]

Hi,
I have updated to v2.2
I'm running windows 7 sp1
I've add TLS 1.2/Client/DisabledByDefault 0
stream.pushbullet.com says both connected

Push2run does not keep restarting. (Hooray)

But it is still getting the websocket error (Boo)

Has anyone running Windows 7 been able to get push2run working ?

I'm assuming this still has to do with TLS 1.2, but I don't know how to verify it.
Anyone come up with a fix ?

[RobLatour]

Well it worked for me in testing.

Here is something you might want to look at:
https://manage.accuwebhosting.com/knowl ... ows-7.html

[rwe]

Yes, thats the page I used to change the registry.
I also went to this page, https://support.microsoft.com/en-us/hel ... cols-in-wi to install the patch using method 2, just to double check.

Going here https://stream.pushbullet.com/ tells me websocket and streaming are connected
Is this connecting with TLS 1.2 ?

Still getting this in the log
2019-05-16 09:04:26.453 - Attempting to reconnect to Pushbullet
2019-05-16 09:04:26.618 - Websocket error
2019-05-16 09:04:26.659 - A call to SSPI failed, see inner exception.
2019-05-16 09:04:26.759 - Websocket closed
2019-05-16 09:04:26.759 - Connection with Pushbullet not established

Can you tell me what ports are being used ?
What does the websocket error mean ?
Is it not reaching the address or is it failing on the protocol ?
Are you able to get that detail or is this error already saying TLS 1.2 is not the protocol ?

Can you think of anything else I can check?
Thanks for the help

[RobLatour]

Push2Run uses the following component to connect thru the websocket

https://archive.codeplex.com/?p=websocket4net (latest stable 0.15.2)

using it the port is not specified.

Have you tried to turn off your antivirus/firewall for the purpose of a quick test?