Error trying to update from within Reaper

[Gerry P]

Reaper usually notifies me (as set in Preferences) on startup.

However, I have been on 5.91 and saw there was an update to 5.93 at KVR.

When I choose "Check for new versions of Reaper" in Help,

I get:

"There was an error checking for the latest version
is an internet connection present?!"

I tried to run Reaper in Admin mode and same error.

First time this issue has occurred.

I was able to download the 5.93 version from the Reaper site and updated from this.

Any idea what may be happening?

[karbomusic]

It's possible your AV or windows is denying the connection. The first time reaper checks (ever) Windows Firewall may have popped up a window asking to allow it, if for some reason that was missed or "no" was chosen, any update attempts that occur in the future may fail like this. To test you could go into the Windows Defender Firewall and add a new outgoing rule for TCP / Reaper.exe / Allow

[Glennbo]

Another possibility is your DNS might be messed up.

You might try opening a command prompt window, and issue the command,

ipconfig /release

followed by,

ipconfig /renew

which will dump your connection and then rebind it, resetting your normal DNS.

[karbomusic]

Originally Posted by Glennbo

Another possibility is your DNS might be messed up.
S.

Then he couldn't get here or check via browser. However, if it were the DNS cache then ipconfig /flushdns is the command to force it to do a new DNS lookup. I suppose it's possible he could have the wrong DNS servers, but that would be really, really odd with basic DHCP.

[Glennbo]

Originally Posted by karbomusic

Then he couldn't get here or check via browser. However, if it were the DNS cache then ipconfig /flushdns is the command to force it to do a new DNS lookup. I suppose it's possible he could have the wrong DNS servers, but that would be really, really odd with basic DHCP.

I've seen more than a few times where DNS is only partly hosed, and I could get to *almost* all sites, but not all of them. A release/renew fixed it almost every time.

My gut feeling is that some server in the sky, or possibly a whole farm of them hosted by AWS, become unreachable due to either some kind of memory corruption, or possibly a hijack from some web page.

When I've seen it, I can type something like cnn.com into my browser and it goes there, but then some other site will time out and give me an error. Doing a release/renew almost always corrects the problem, but at least once or twice I've had to dump my modem's connection and let it get it's DNS reestablished.

Here's a link to a possible reason a /release /renew would work.

https://serverfault.com/questions/48...s-client-issue

[Gerry P]

Thank you both for the suggestions.

It took a while, but I tried all of the suggestions with no change.

As it seems it is just my PC, I will continue to monitor. I have only really noticed this with Reaper and it is easy enough to do a manual update check every week or so.