Random disconnects

[BasedOnPixels]

Hello again, there is some issue for me with people getting disconnected after a game is running for around 3 hours.
First game:

Second game:

The issue here is that the bot just starts lagging for a player and then drops them because of "connection error - Connection reset by peer". In the first game I ran a !ping to see if anyone was lagging but that wasn't the case, yet the bot still just dropped them out of nowhere.

Also there is the disconnect from battle.net I was talking about a few days ago, I'm not sure how much it is related though.

[BasedOnPixels]

Went to sleep after disconnect in the second game and woke up to see that another person had been kicked and the bot disconnected from battle.net without ever trying to reconnect.

[marciii]

I also have some connection issues, but they're different:

[TCPSOCKET] error (recv) - ETIMEDOUT
[BNET: Europe] disconnected from battle.net due to socket error
[BNET: Europe] waiting 240 seconds to reconnect
[BNET: Europe] connecting to server [europe.battle.net] on port 6112
[BNET: Europe] using cached server IP address 5.42.181.17
[BNET: Europe] connected
[BNET: Europe] attempting to auth as Warcraft III: The Frozen Throne
[BNET: Europe] logon failed - game version is too old, disconnecting
[BNET: Europe] disconnected from battle.net
[BNET: Europe] connecting to server [europe.battle.net] on port 6112
[BNET: Europe] using cached server IP address 5.42.181.17
[BNET: Europe] connected
[BNET: Europe] attempting to auth as Warcraft III: The Frozen Throne
[BNET: Europe] logon failed - game version is too old, disconnecting
[BNET: Europe] disconnected from battle.net

It always happens when i go to sleep and the bot doesnt send / receive anything anymore, it disconnects. And weird enough: it's trying to reconnect as it's supposed to do. But then it says "game version is too old". And when i restart it manually - it works again :D

[Josko]

Regarding ECONNRESET:

Seems related to #76. I'm pretty sure I'll have to git bisect the socket changes I made recently and test it out. Seems Windows only AFAIK.

Regarding ETIMEDOUT:

This seems a separate issue. Historically ECONNRESETs were the plague of networking in the GHost family, ETIMEDOUT not as much...

[BasedOnPixels]

It's good that you might have find the issue, fixing it is another story of course.

How about the connection reset by peer thing? Could it be related?

I'm not sure if this info will help but I'm running Aura on Windows Server 2016.