-
Notifications
You must be signed in to change notification settings - Fork 501
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Trying to find the answer this Connection Issue #394
Comments
Spoke with AzuiSleet_ a lot in IRC. It is true that HardwareUtils plays a role. After altering that (String.Random()), I was able to connect without an issue. I think we should update the Comments in that field as I think the rules have maybe changed again? One thing AzuiSleet_ thought was weird is that sometimes, when the rate limit occurs I can Disconnect then reconnect and get 1 more request. If I disconnect and Reconnect again, I get 1 request, then the GC times out. He said it may be a bug. Any insight? Specifically the DotaMatch GC call. |
I'm 99% sure your issue is #305. |
And if you want a solution that doesn't require modifying SK2 code then take a look at https://github.com/JustArchi/ArchiSteamFarm/blob/master/ArchiSteamFarm/Bot.cs#L1383-L1388 and https://github.com/JustArchi/ArchiSteamFarm/blob/master/ArchiSteamFarm/ArchiHandler.cs#L97-L149 |
@JustArchi I removed that all together in a fork and I just do a Random String of 10 Characters each time. Seemed to help with Part A of my issue. Part B is still unknown. |
Does it all work fine if you use v1.8.3 from NuGet, or does the issue persist? |
I believe I was using maybe a bit before 1.8.3. So after many hours, I believe it is in-fact the Hardware Utils. If you run 50 instance of steamkit you wont even be able to connect. If you alter the HardwareId on each, connection is possible. Since SteamKit has a static hardware id on load, over time eventually your hardware id gets banned and you have kill SteamKit to start over. @JustArchi I used your method, but when running a lot of bots, running no HardwareId is the same as running the same one, eventually I was limited. I tried creating a new HardwareId on each Login, but still something in SteamKit must of stayed the same and eventually I was blocked. Not sure how the 1st connection is different from the 2nd connection but there has to be something. Referencing my 1st post as an example, the Ip address is correct in the 2nd connection but wrong in the 1st. |
Was this ever resolved? I seem to recall some further discussion in IRC but it hasn't been documented here. |
Closing due to inactivity. |
First off, let me say my code works fine under the build from around August of last year (2016). I am really not sure what has been added or changed, but every time I attempt to upgrade to the latest version, I have this issue. I would really love to solve it.
So, I run a lot of bots on one machine. From everything I checked, nothing is sent to steam thats hardcoded that would block me (For example Local Ip address or hardware Ids, or Mac Ids). When I make my 1st connection attempt, I get a positive result.
As I continue, I then try to login, but I dont get ANYTHING on the
void OnLoggedOn(SteamUser.LoggedOnCallback callback)
So then I run my Disconnect Method.
This is before the SteamClient.Disconnect.
This is after I call SteamClient.Disconnect. Not much different.
Now, my bot retries again. This time, I cannot even connect to Steam.
Above is the Connect, Debug print out, then the Disconnect is called, then the out printout.
The odd part is you can see "IsConnect" is actually true, but I never got any data on
void OnConnected(SteamClient.ConnectedCallback callback)
Really not sure where to go from here. I am using a lot on one machine, but even if I am getting rate limited, shouldn't SteamKit still give me some type of response?
I can answer any questions.
It has to be related to having multiple connections per machine, but I can't see where, and occasionally it just works but eventually stops again.
The text was updated successfully, but these errors were encountered: