Page 2 of 3
Re: Only some pushes are received by Push2Run
Posted: Sat Mar 09, 2019 7:45 am
by RobLatour
Myself, I am not getting any failures.
Can you please restart your PC, start the program up (if it doesn't autostart), run a few tests with at least one case where it worked and one where it did not. Once done please post your entire session log and I'll take a look.
If you would rather not post it, you can send it to
info@push2run.com
Re: Only some pushes are received by Push2Run
Posted: Sat Mar 09, 2019 8:32 am
by jasoncollege24
Well... i restart about once every other week (sooner, if I see big problems that need it).
Last restart was on the evening of the 4th, which was after the pushbullet issue was resolved. Websocket errors appear in the log as soon as 6 minutes after P2R was launched automatically by Windows. The entire session log is posted below, and should be enough, without a fresh restart, considering errors are as late as 4:18 am Eastern today (websocket)
Only failed push in the log was for one that needed an edit, because the listen for phrase I used needed to be added.
Code: Select all
2019-03-04 19:22:17.540 - Started
2019-03-04 19:22:18.657 - Current network adapter is Ethernet 4
2019-03-04 19:22:19.119 - Network status is up
2019-03-04 19:22:22.926 - Connection with Pushbullet established
2019-03-04 19:25:25.372 - Incoming push ...
2019-03-04 19:25:25.375 - <Title> Push2Run JAY-DESKTOP
2019-03-04 19:25:25.376 - <Body> show work
2019-03-04 19:25:25.971 - action completed
2019-03-04 19:28:21.887 - Websocket error
2019-03-04 19:28:21.888 - Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
2019-03-04 19:28:21.889 - Websocket closed
2019-03-04 19:28:21.987 - Attempting to reconnect to Pushbullet
2019-03-04 19:28:22.423 - Connection with Pushbullet established
2019-03-04 19:30:22.229 - Websocket error
2019-03-04 19:30:22.229 - Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
2019-03-04 19:30:22.229 - Websocket closed
2019-03-04 19:30:22.425 - Attempting to reconnect to Pushbullet
2019-03-04 19:30:22.811 - Connection with Pushbullet established
2019-03-04 19:33:22.651 - Websocket error
2019-03-04 19:33:22.651 - Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
2019-03-04 19:33:22.652 - Websocket closed
2019-03-04 19:33:22.801 - Attempting to reconnect to Pushbullet
2019-03-04 19:33:23.258 - Connection with Pushbullet established
2019-03-05 01:00:23.448 - Websocket error
2019-03-05 01:00:23.449 - Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
2019-03-05 01:00:23.449 - Websocket closed
2019-03-05 01:00:24.255 - Attempting to reconnect to Pushbullet
2019-03-05 01:00:24.652 - Connection with Pushbullet established
2019-03-05 01:12:06.575 - Incoming push ...
2019-03-05 01:12:06.576 - <Title> Push2Run JAY-DESKTOP
2019-03-05 01:12:06.576 - <Body> start streaming
2019-03-05 01:12:06.809 - no matching active phrases
2019-03-05 01:12:21.300 - Incoming push ...
2019-03-05 01:12:21.300 - <Title> Push2Run JAY-DESKTOP
2019-03-05 01:12:21.300 - <Body> show streaming
2019-03-05 01:12:22.006 - action completed
2019-03-05 07:09:36.863 - Incoming push ...
2019-03-05 07:09:36.864 - <Title> Push2Run JAY-DESKTOP
2019-03-05 07:09:36.864 - <Body> lock my pc
2019-03-05 07:09:37.701 - action completed
2019-03-05 07:09:48.282 - Incoming push ...
2019-03-05 07:09:48.282 - <Title> Push2Run JAY-DESKTOP
2019-03-05 07:09:48.282 - <Body> lock my pc
2019-03-05 07:09:48.683 - action completed
2019-03-05 13:15:55.602 - Websocket error
2019-03-05 13:15:55.603 - Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
2019-03-05 13:15:55.603 - Websocket closed
2019-03-05 13:15:56.538 - Attempting to reconnect to Pushbullet
2019-03-05 13:15:57.047 - Connection with Pushbullet established
2019-03-05 15:30:56.992 - Websocket error
2019-03-05 15:30:56.992 - Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
2019-03-05 15:30:56.993 - Websocket closed
2019-03-05 15:30:57.052 - Attempting to reconnect to Pushbullet
2019-03-05 15:30:57.575 - Connection with Pushbullet established
2019-03-05 17:31:18.230 - Incoming push ...
2019-03-05 17:31:18.231 - <Title> Push2Run JAY-DESKTOP
2019-03-05 17:31:18.231 - <Body> show on small
2019-03-05 17:31:18.748 - action completed
2019-03-05 23:19:57.761 - Websocket error
2019-03-05 23:19:57.762 - Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
2019-03-05 23:19:57.762 - Websocket closed
2019-03-05 23:19:58.693 - Attempting to reconnect to Pushbullet
2019-03-05 23:19:59.131 - Connection with Pushbullet established
2019-03-06 01:38:12.682 - Incoming push ...
2019-03-06 01:38:12.683 - <Title> Push2Run JAY-DESKTOP
2019-03-06 01:38:12.683 - <Body> show on streaming
2019-03-06 01:38:13.243 - action completed
2019-03-06 04:06:05.088 - Attempting to reconnect to Pushbullet
2019-03-06 04:06:15.142 - Connection with Pushbullet not established
2019-03-06 04:06:15.154 - Attempting to reconnect to Pushbullet
2019-03-06 04:06:15.162 - Websocket error
2019-03-06 04:06:15.260 - No such host is known
2019-03-06 04:06:15.361 - Websocket closed
2019-03-06 04:06:15.462 - Connection with Pushbullet not established
2019-03-06 04:06:15.583 - Websocket error
2019-03-06 04:06:15.583 - No such host is known
2019-03-06 04:06:15.583 - Websocket closed
2019-03-06 04:06:25.081 - Attempting to reconnect to Pushbullet
2019-03-06 04:06:35.183 - Connection with Pushbullet not established
2019-03-06 04:06:35.186 - Attempting to reconnect to Pushbullet
2019-03-06 04:06:36.120 - Websocket error
2019-03-06 04:06:36.120 - Websocket error
2019-03-06 04:06:36.201 - No such host is known
2019-03-06 04:06:36.201 - No such host is known
2019-03-06 04:06:36.302 - Websocket closed
2019-03-06 04:06:36.302 - Connection with Pushbullet not established
2019-03-06 04:06:36.302 - Websocket closed
2019-03-06 04:06:45.080 - Attempting to reconnect to Pushbullet
2019-03-06 04:06:55.185 - Connection with Pushbullet not established
2019-03-06 04:06:55.189 - Attempting to reconnect to Pushbullet
2019-03-06 04:06:56.120 - Websocket error
2019-03-06 04:06:56.120 - Websocket error
2019-03-06 04:06:56.205 - No such host is known
2019-03-06 04:06:56.205 - No such host is known
2019-03-06 04:06:56.306 - Connection with Pushbullet not established
2019-03-06 04:06:56.306 - Websocket closed
2019-03-06 04:06:56.306 - Websocket closed
2019-03-06 04:07:05.083 - Attempting to reconnect to Pushbullet
2019-03-06 04:07:05.091 - Websocket error
2019-03-06 04:07:05.190 - No such host is known
2019-03-06 04:07:05.291 - Websocket closed
2019-03-06 04:07:05.291 - Connection with Pushbullet not established
2019-03-06 04:07:15.081 - Attempting to reconnect to Pushbullet
2019-03-06 04:07:15.477 - Connection with Pushbullet established
2019-03-06 05:53:15.416 - Websocket error
2019-03-06 05:53:15.417 - Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
2019-03-06 05:53:15.417 - Websocket closed
2019-03-06 05:53:15.477 - Attempting to reconnect to Pushbullet
2019-03-06 05:53:15.878 - Connection with Pushbullet established
2019-03-06 14:31:13.266 - Websocket error
2019-03-06 14:31:13.267 - Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
2019-03-06 14:31:13.267 - Websocket closed
2019-03-06 14:31:13.597 - Attempting to reconnect to Pushbullet
2019-03-06 14:31:14.049 - Connection with Pushbullet established
2019-03-06 18:52:14.056 - Websocket error
2019-03-06 18:52:14.057 - Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
2019-03-06 18:52:14.058 - Websocket closed
2019-03-06 18:52:15.046 - Attempting to reconnect to Pushbullet
2019-03-06 18:52:15.616 - Connection with Pushbullet established
2019-03-06 18:59:15.313 - Websocket error
2019-03-06 18:59:15.314 - Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
2019-03-06 18:59:15.314 - Websocket closed
2019-03-06 18:59:15.607 - Attempting to reconnect to Pushbullet
2019-03-06 18:59:16.042 - Connection with Pushbullet established
2019-03-06 23:04:40.602 - Incoming push ...
2019-03-06 23:04:40.603 - <Title> Push2Run JAY-DESKTOP
2019-03-06 23:04:40.603 - <Body> show streaming
2019-03-06 23:04:41.316 - action completed
2019-03-07 05:48:16.483 - Websocket error
2019-03-07 05:48:16.490 - Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
2019-03-07 05:48:16.491 - Websocket closed
2019-03-07 05:48:16.767 - Attempting to reconnect to Pushbullet
2019-03-07 05:48:17.257 - Connection with Pushbullet established
2019-03-07 11:14:44.852 - Incoming push ...
2019-03-07 11:14:44.854 - <Title> Push2Run JAY-DESKTOP
2019-03-07 11:14:44.854 - <Body> show streaming
2019-03-07 11:14:45.678 - action completed
2019-03-07 11:50:07.478 - Incoming push ...
2019-03-07 11:50:07.479 - <Title> Push2Run JAY-DESKTOP
2019-03-07 11:50:07.479 - <Body> lock my pc
2019-03-07 11:50:07.871 - action completed
2019-03-08 00:09:26.545 - Incoming push ...
2019-03-08 00:09:26.546 - <Title> Push2Run JAY-DESKTOP
2019-03-08 00:09:26.546 - <Body> show streaming
2019-03-08 00:09:26.908 - action completed
2019-03-08 00:33:15.684 - Websocket error
2019-03-08 00:33:15.685 - Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
2019-03-08 00:33:15.685 - Websocket closed
2019-03-08 00:33:16.068 - Attempting to reconnect to Pushbullet
2019-03-08 00:33:16.477 - Connection with Pushbullet established
2019-03-08 04:41:16.576 - Websocket error
2019-03-08 04:41:16.577 - Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
2019-03-08 04:41:16.577 - Websocket closed
2019-03-08 04:41:17.554 - Attempting to reconnect to Pushbullet
2019-03-08 04:41:17.974 - Connection with Pushbullet established
2019-03-08 09:50:54.244 - Incoming push ...
2019-03-08 09:50:54.245 - <Title> Push2Run JAY-DESKTOP
2019-03-08 09:50:54.245 - <Body> lock my pc
2019-03-08 09:50:54.816 - action completed
2019-03-08 13:08:16.079 - Websocket error
2019-03-08 13:08:16.080 - Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
2019-03-08 13:08:16.080 - Websocket closed
2019-03-08 13:08:16.810 - Attempting to reconnect to Pushbullet
2019-03-08 13:08:17.205 - Connection with Pushbullet established
2019-03-08 17:43:17.314 - Websocket error
2019-03-08 17:43:17.315 - Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
2019-03-08 17:43:17.315 - Websocket closed
2019-03-08 17:43:18.219 - Attempting to reconnect to Pushbullet
2019-03-08 17:43:18.633 - Connection with Pushbullet established
2019-03-08 23:23:18.765 - Websocket error
2019-03-08 23:23:18.766 - Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
2019-03-08 23:23:18.766 - Websocket closed
2019-03-08 23:23:19.654 - Attempting to reconnect to Pushbullet
2019-03-08 23:23:20.104 - Connection with Pushbullet established
2019-03-09 04:18:20.235 - Websocket error
2019-03-09 04:18:20.236 - Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
2019-03-09 04:18:20.236 - Websocket closed
2019-03-09 04:18:21.123 - Attempting to reconnect to Pushbullet
2019-03-09 04:18:21.548 - Connection with Pushbullet established
2019-03-09 06:39:25.375 - Incoming push ...
2019-03-09 06:39:25.381 - <Title> Push2Run JAY-DESKTOP
2019-03-09 06:39:25.381 - <Body> show streaming
2019-03-09 06:39:25.839 - action completed
2019-03-09 06:47:51.686 - Incoming push ...
2019-03-09 06:47:51.687 - <Title> Push2Run JAY-DESKTOP
2019-03-09 06:47:51.688 - <Body> clean my desktop
2019-03-09 06:47:52.004 - action completed
2019-03-09 06:50:58.222 - Incoming push ...
2019-03-09 06:50:58.223 - <Title> Push2Run JAY-DESKTOP
2019-03-09 06:50:58.223 - <Body> clean my desktop
2019-03-09 06:50:58.519 - action completed
Re: Only some pushes are received by Push2Run
Posted: Sat Mar 09, 2019 10:37 am
by RobLatour
When push2run detects an issue with the connection to pushbullet it automatically tries to re-connect. According to your log this is working very well, with reconnects happening within a few seconds.
My own log goes back to March 3rd with no loss of connectivity reported, so I am not suspecting an issue with pushbullet.
You might want to look at your network setup, the question to ask is why is it losing the connection so often - if only for a moment. Do you have more than one router / hub involved in your own network; at the times the problems are reported, do you have heavy network activity (for example backing up files to a network drive), etc.
Re: Only some pushes are received by Push2Run
Posted: Sat Mar 09, 2019 11:15 pm
by jasoncollege24
There are 2 routers, and 1 hub between me, and the internet. All of them gigabit, and all wired. there is a modem, my router, then the hub. On the modem, my router has a static IP, and is set as DMZ.
There is not a lot of heavy traffic, and definitely not as often as the drops. Speed tests always range between 700-900Mbps (Megabits) both up and down, with average ping times of 5ms, or less, even when there is heavy traffic on the network, which should be way more than enough.
I am also using Comodo Internet Security (free) for my antivirus, and firewall software.
The first "clean my desktop" push at the bottom is push 1/10 from the test pushes, so these failures happened while P2R claimed it's connection was good. P2R also appears to be the only program/app that has any internet issues.
Re: Only some pushes are received by Push2Run
Posted: Sun Mar 10, 2019 10:19 am
by GordThompson
Have you checked lately to see if there is a firmware update available for your router? It's easy to overlook. (By coincidence, yesterday I discovered that my router firmware had been updated twice since the last time I checked, which was several months ago.)
Re: Only some pushes are received by Push2Run
Posted: Sun Mar 10, 2019 10:29 am
by RobLatour
Here is a link that the folks at Pushbullet sent me saying that people could use to test their connections:
https://stream.pushbullet.com/
Here are the results I am getting (although my download speed is only about half of yours).
Pushbullet Streaming Test Page
websocket connected in 0.48 seconds
streaming connected in 0.47 seconds
What connection speeds are you seeing on your machine running Push2Run?
Re: Only some pushes are received by Push2Run
Posted: Sun Mar 10, 2019 10:28 pm
by jasoncollege24
Based on info given in the first reply, I'm working to track this problem down.
1. I've moved items that do a lot of heavy traffic (security cams), and related network hardware to their physically isolated network
2. Removing all unused hardware (extenders, hubs, etc) from the network
3. Checking remaining items for firmware updates
and more
What made me realize he is right about a network issue is that I have 2 computers with P2R installed, and they're both having the same problem, with each PC having the same websocket error being half a second apart (eg errors shown in the log above happened half a second later on the other machine every time)
I'll take new suggestions and ideas into account, and get back on this once i have the network stability problem resolved.
Edit: the test page show 0.57, and 0.56 respectively.
Re: Only some pushes are received by Push2Run
Posted: Thu Apr 04, 2019 6:29 pm
by jasoncollege24
This problem has been resolved for me. Turns out my router was failing. Replacing the router fixed the problem, and no commands are missed. Thanks for pointing me in the right direction!
Re: Only some pushes are received by Push2Run
Posted: Thu Apr 04, 2019 9:42 pm
by RobLatour
Great, thanks for the feedback. Glad it's working for you!
Re: Only some pushes are received by Push2Run
Posted: Sat Apr 20, 2019 8:44 pm
by jasoncollege24
spoke too soon! Now it still happens, but MUCH more rarely, and this time, there are no disconnects as the culprit. Below is the session log from the last few days, starting from the last time I had to reset my modem. The attached screenshot shows that two pushes were sent. This has literally happened at most, 2-3 times, since replacing my router, and had nothing to do with any disconnects, or service interruptions... VERY rare ocurrence now.
Code: Select all
2019-04-17 01:04:23.141 - Attempting to reconnect to Pushbullet
2019-04-17 01:04:29.925 - Websocket error
2019-04-17 01:04:29.995 - No such host is known
2019-04-17 01:04:30.096 - Connection with Pushbullet not established
2019-04-17 01:04:30.096 - Websocket closed
2019-04-17 01:04:33.140 - Attempting to reconnect to Pushbullet
2019-04-17 01:04:33.776 - Connection with Pushbullet established
2019-04-17 01:22:54.471 - Incoming push ...
2019-04-17 01:22:54.472 - <Title> Push2Run JAY-DESKTOP
2019-04-17 01:22:54.472 - <Body> lock my pc
2019-04-17 01:23:10.027 - action completed
2019-04-20 20:36:50.195 - Incoming push ...
2019-04-20 20:36:50.197 - <Title> Push2Run JAY-DESKTOP
2019-04-20 20:36:50.197 - <Body> lock my pc
2019-04-20 20:36:51.121 - action completed