Failure to connect after suspend

[AndyHenderson]

I'm switching from uTorrent having not received either the software or support I paid for!

I'm appreciating a number of features in QB that uT is missing!

I use QB 4.1.4, Windows 10 9/18 fully patched and the latest version of NordVPN.

I suspend my media centre when I go to bed. It wakes up various times during the night. The plan is for QB to check my showRSS feed and download anything new automatically. That works fine during the day but after resuming from suspend with more than 30m since the last poll of the feed I get:

Failed to download RSS feed at … Reason the remote host name was not found (invalid hostname).

Once in this state, manually updating the feed or waiting 30 minutes always reads the feed correctly.

Most days that's not a big issue because it resolves automatically when I have the media centre on for watching. When I'm away, however, nothing will download because the media centre is never on for long enough for a second retry of the feed. I could change the retries to, say, 1 minute which would probably work but that would be abusing showRSS.

I've tried both running the VPN globally on the media centre, and entering specific proxy server details in QB. I get the same results either way.

It looks like QB is jumping in too quickly and is trying to use the proxy connection before it is ready.

I can solve my own problem by programmatically stopping and restarting QB after a return from suspend. But before I dive into code, does anyone have a better solution?

Andy

[AndyHenderson]

I've added some code to my environment that detects a return from suspend and:

- uses the web API to shut down QB
- waits ten seconds to allow things to settle down
- restarts QB

The feed error that used to display at every resume is still in the log (QB gets in before I can shut it down which means it is jumping in very quickly), but the log also shows QB restarting and the feed is read successfully every time after that.

QB just downloaded its first file unattended since I added the code, so it looks like I solved my problem.

FWIW, I suggest QB detects if the feed hasn't been read for more than, say, 10 seconds sine the last tine it was due (which would indicate the PC has gone into suspend or hibernate) and, if found, resets the time of the next read to, say, 20 seconds in the future. That would be a relatively simple fix and also OS independent. From a Windows perspective, however, explicit detection and reaction to a resume state would be better.

Andy

[AndyHenderson]

An even simpler solution would be to retry, say, 5 times with, say, 10 seconds between each retry when getting an error trying to read the feed. As it stands QB tries just once and gives up.

Andy