Pushover connection problems

[pho08]

Hi

ever since a couple of days ago Push2Run will sporadically lose connection to the Pushover servers, resulting in commands not reaching push2run.

what's worse is that push2run doesn't seem to notice right away when the connection is lost, so when it comes back after a while it will execute all the commands in queue at the same time ---> chaos

did pushover change anything or why do i always lose connection? (i bought a license there btw). i am on the latest version of push2run

Cheers

[RobLatour]

I had several connection issues with Pushover earlier in the week myself, but only one today. Just notice another post also speaking about Pushover issues. PushBullet and Dropbox don't seem to have been problematic at all.

If it continues you could potentially switch to either Pushbullet or Dropbox as the service that drives Push2Run. Also, with the latest version of Push2Run there is some extra logic in the program to prevent queueing up of older commands not processed when using Dropbox.

[pho08]

thanks for the reply Rob

To be honest it would be a shame having to switch services as so far i was perfectly happy with pushover. So i wrote an email to their support. But then I discovered this on their blog

April 15-16 DDoS Attack
April 16, 2020 by joshua stein
On April 15th at approximately 23:30 CDT, Pushover's API servers came under a DNS amplification Distributed Denial of Service (DDoS) attack which caused them to be unreachable by their IPv4 addresses, though they were still reachable over IPv6.

This attack persisted through the morning of the 16th. At 01:55 we began rerouting traffic for api.pushover.net through a 3rd party DDoS mitigation company and we are once again receiving API requests (IPv4 and IPv6).

Unfortunately at this time, we are unable to receive e-mail notifications through our E-Mail Gateway for legacy USERKEY@api.pushover.net addresses, though our @pomail.net addresses are working.

At no point during this attack were any servers compromised or any data exposed. This was purely a resource exhaustion attack intended to take our service offline.

We are continuing to monitor the attack and are taking steps to mitigate its effect on our service. We will update this post with any further news.

Update 2020-04-16 16:30 CDT: The attack is still persisting, but as we are routing our API and dashboard through our 3rd party DDoS mitigation service, we are continuing to receive notification requests and send them out mostly without incident. We will continue to provide more updates here as needed.

so maybe that has something to do with it
https://blog.pushover.net/

[pho08]

hi

back again with the pushover connection problems

i can manually re-authenticate and push2run returns "success" but the service still isn't connected (red icon/ status "not connected to pushover").
If i log on pushover.net manually and send a message to Computer/smartphone things seem a bit slow today but it does work eventually. So i am not sure who's the culprit here.


is anybody else experiencing "not connected to pushover" at the moment or is this a problem at my end?


short excerpt from the log

Code: Select all

2020-06-09 18:41:24.961 - Connection with Pushover not established

2020-06-09 18:41:24.961 - Attempting to reconnect to Pushover
2020-06-09 18:41:25.272 - Pushover websocket error
2020-06-09 18:41:25.277 - HTTP/1.1 504 Gateway Time-out
2020-06-09 18:41:25.379 - Pushover websocket closed

2020-06-09 18:41:31.952 - Pushover websocket closed

2020-06-09 18:41:35.032 - Connection with Pushover not established

2020-06-09 18:41:35.032 - Attempting to reconnect to Pushover
2020-06-09 18:41:45.107 - Connection with Pushover not established

2020-06-09 18:41:45.117 - Attempting to reconnect to Pushover
2020-06-09 18:41:45.382 - Pushover websocket error
2020-06-09 18:41:45.444 - HTTP/1.1 504 Gateway Time-out
2020-06-09 18:41:45.553 - Pushover websocket closed

2020-06-09 18:41:55.219 - Connection with Pushover not established

2020-06-09 18:41:55.235 - Attempting to reconnect to Pushover
2020-06-09 18:41:56.421 - Pushover websocket closed

2020-06-09 18:42:05.332 - Connection with Pushover not established

2020-06-09 18:42:05.348 - Attempting to reconnect to Pushover
2020-06-09 18:42:05.504 - Pushover websocket error
2020-06-09 18:42:05.567 - HTTP/1.1 504 Gateway Time-out
2020-06-09 18:42:05.676 - Pushover websocket closed

2020-06-09 18:42:15.425 - Connection with Pushover not established

2020-06-09 18:42:15.441 - Attempting to reconnect to Pushover
2020-06-09 18:42:25.522 - Connection with Pushover not established

2020-06-09 18:42:25.522 - Attempting to reconnect to Pushover
2020-06-09 18:42:35.626 - Connection with Pushover not established

2020-06-09 18:42:35.626 - Attempting to reconnect to Pushover
2020-06-09 18:42:35.751 - Pushover websocket error
2020-06-09 18:42:35.860 - HTTP/1.1 504 Gateway Time-out
2020-06-09 18:42:35.969 - Pushover websocket closed

2020-06-09 18:42:40.699 - Pushover websocket closed

2020-06-09 18:42:42.240 - Pushover websocket closed

2020-06-09 18:42:42.708 - Attempting to reconnect to Pushover
2020-06-09 18:42:45.960 - Pushover websocket error
2020-06-09 18:42:46.010 - HTTP/1.1 504 Gateway Time-out
2020-06-09 18:42:46.111 - Pushover websocket closed

2020-06-09 18:42:52.763 - Connection with Pushover not established

2020-06-09 18:42:52.767 - Connection with Pushover not established

2020-06-09 18:42:52.772 - Attempting to reconnect to Pushover
2020-06-09 18:43:02.791 - Connection with Pushover not established

2020-06-09 18:43:02.798 - Attempting to reconnect to Pushover
2020-06-09 18:43:12.851 - Connection with Pushover not established

2020-06-09 18:43:12.856 - Attempting to reconnect to Pushover
2020-06-09 18:43:17.959 - Pushover websocket closed

2020-06-09 18:43:21.794 - Pushover websocket closed

2020-06-09 18:43:22.969 - Connection with Pushover not established

2020-06-09 18:43:22.969 - Attempting to reconnect to Pushover
2020-06-09 18:43:32.750 - Attempting to reconnect to Pushover
2020-06-09 18:43:42.825 - Connection with Pushover not established

2020-06-09 18:43:42.825 - Connection with Pushover not established

2020-06-09 18:43:42.841 - Attempting to reconnect to Pushover
2020-06-09 18:43:43.452 - Pushover websocket error
2020-06-09 18:43:43.499 - HTTP/1.1 504 Gateway Time-out
2020-06-09 18:43:43.499 - Pushover websocket closed

2020-06-09 18:43:49.654 - Pushover websocket closed
2020-06-09 18:43:49.669 - Pushover websocket closed


2020-06-09 18:43:51.215 - Pushover websocket closed

2020-06-09 18:43:52.946 - Connection with Pushover not established

2020-06-09 18:43:52.946 - Attempting to reconnect to Pushover

[RobLatour]

it was down for a while today for me too - back up again now