Push2Run 2.1.1 cannot connect to pushbullet
Posted: Sun Feb 24, 2019 7:21 pm
Relevant devices: 2 (PC info below is for both devices)
OS: Windows 10 Pro 1809
Push2Run Ver: 2.1.1 (Verified on both devices)
Pushbullet: installed and up-to-date on all relevant devices (and phone)
Problem description:
Push2Run can no longer connect to pushbullet, and instead gets a websock error, and it's tray icon stays red. Main window says "Not connected to Pushbullet"
Was this working before the update? Yes
Is this problem verified on both devices? Yes
Did you try restarting Push2Run? Yes
Did you try restarting the device? Yes
Is this reproducible? Yes. Update to 2.1.1, and start push2run (reproducible every single time in my setup)
Any workarounds? Haven't found any
Troubleshooting steps tried:
Restart Push2Run
Reinstall Push2Run
Restart Windows
Downgrade to an earlier version (2.1.0, and 1.0.9) Both failed the same way, after upgrading, then downgrading!
Great program... helps me a lot, because I'm disabled. Can't use it now, unless this problem is corrected. Below is a copy of some of the log file, which repeats the same bits endlessly as it tries to connect.
OS: Windows 10 Pro 1809
Push2Run Ver: 2.1.1 (Verified on both devices)
Pushbullet: installed and up-to-date on all relevant devices (and phone)
Problem description:
Push2Run can no longer connect to pushbullet, and instead gets a websock error, and it's tray icon stays red. Main window says "Not connected to Pushbullet"
Was this working before the update? Yes
Is this problem verified on both devices? Yes
Did you try restarting Push2Run? Yes
Did you try restarting the device? Yes
Is this reproducible? Yes. Update to 2.1.1, and start push2run (reproducible every single time in my setup)
Any workarounds? Haven't found any
Troubleshooting steps tried:
Restart Push2Run
Reinstall Push2Run
Restart Windows
Downgrade to an earlier version (2.1.0, and 1.0.9) Both failed the same way, after upgrading, then downgrading!
Great program... helps me a lot, because I'm disabled. Can't use it now, unless this problem is corrected. Below is a copy of some of the log file, which repeats the same bits endlessly as it tries to connect.
Code: Select all
2019-02-24 15:24:00.977 - Started
2019-02-24 15:24:02.089 - Network status is up
2019-02-24 15:24:04.055 - Websocket error
2019-02-24 15:24:04.076 - A call to SSPI failed, see inner exception.
2019-02-24 15:24:04.157 - Websocket closed
2019-02-24 15:24:04.408 - Connection with Pushbullet not established
2019-02-24 15:24:05.410 - Attempting to reconnect to Pushbullet
2019-02-24 15:24:05.489 - Websocket error
2019-02-24 15:24:05.515 - A call to SSPI failed, see inner exception.
2019-02-24 15:24:05.515 - Websocket closed
2019-02-24 15:24:05.515 - Connection with Pushbullet not established