Jump to content
McKay Development

speicher

Member
  • Posts

    13
  • Joined

  • Last visited

Recent Profile Visitors

302 profile views
  • Pip

speicher's Achievements

  1. if you have no idea what you talking about, then better write nothing. steam itself is ajax looping for many services e.g. for the notifications. based on you logic, 1 call per steam account, which is looping before every 20 seconds (now 60 seconds) - for new mobile confirmations - is a (D)DOS attack? lmao. obv, you have no idea what you talking about. do you even know, how many request a browser is doing when you surf on a website? obv, not. by the way, valve has not "accidentally provided these tools", they was developed by Dr. McKay and seishun. @Dr. McKay thank you. i will use it next time. i have dropped you another paypal donation. keep up the good work!
  2. ok, i have increased the "startConfirmationChecker" interval from 20 to 60 seconds and each bot has now an own ip address through "new SteamCommunity(bla)". looks like it's working now. error: null error: null error: null error: null error: null error: null
  3. looks like rate limiting (error 429). i have tons of failed trades. is there an option to bind each bot on a different ip address? Accepted trade request error: undefined response: Error: HTTP error 429 body: undefined Found 552 CS:GO items in my inventory. Add item: Dual Berettas | Dualing Dragons (Minimal Wear) Found 8 Steam items in my inventory. User clicked ready Confirming Trade Trade completed: pending error: undefined response: Error: HTTP error 429 body: undefined [#XXXXXXXXX] Trade State: 2 Offer accepted error: [object Object] response: null error: [object Object] response: null body: [object Object] Ready for trading. error: [object Object] response: null body: [object Object] error: undefined response: Error: HTTP error 429 body: undefined error: undefined response: Error: HTTP error 429 body: undefined response: Error: HTTP error 429 body: undefined error: undefined response: Error: HTTP error 429 body: undefined error: undefined response: Error: HTTP error 429 body: undefined error: undefined response: Error: HTTP error 429 body: undefined error: undefined response: Error: HTTP error 429 body: undefined error: undefined response: Error: HTTP error 429 body: undefined error: undefined response: Error: HTTP error 429 body: undefined error: undefined response: Error: HTTP error 429 body: undefined error: undefined response: Error: HTTP error 429 body: undefined error: undefined response: Error: HTTP error 429 body: undefined error: undefined response: Error: HTTP error 429 body: undefined error: undefined response: Error: HTTP error 429 body: undefined error: undefined response: Error: HTTP error 429 body: undefined error: undefined response: Error: HTTP error 429 body: undefined error: undefined response: Error: HTTP error 429 body: undefined error: undefined response: Error: HTTP error 429 body: undefined error: undefined response: Error: HTTP error 429 body: undefined error: undefined response: Error: HTTP error 429 body: undefined error: undefined response: Error: HTTP error 429 body: undefined error: undefined response: Error: HTTP error 429 body: undefined error: undefined response: Error: HTTP error 429 body: undefined error: undefined response: Error: HTTP error 429 body: undefined error: undefined response: Error: HTTP error 429 body: undefined error: undefined response: Error: HTTP error 429 body: undefined error: undefined response: Error: HTTP error 429 body: undefined error: undefined response: Error: HTTP error 429 body: undefined We have 65 friends. error: undefined response: Error: HTTP error 429 body: undefined error: undefined response: Error: HTTP error 429 body: undefined error: undefined response: Error: HTTP error 429 body: undefined error: undefined response: Error: HTTP error 429 body: undefined error: undefined response: Error: HTTP error 429 body: undefined error: undefined response: Error: HTTP error 429 body: undefined error: undefined response: Error: HTTP error 429 body: undefined error: undefined response: Error: HTTP error 429 body: undefined error: undefined response: Error: HTTP error 429 body: undefined error: undefined response: Error: HTTP error 429 body: undefined error: undefined response: Error: HTTP error 429 body: undefined error: undefined response: Error: HTTP error 429 body: undefined error: undefined response: Error: HTTP error 429 body: undefined error: undefined response: Error: HTTP error 429 body: undefined error: undefined response: Error: HTTP error 429 body: undefined error: undefined response: Error: HTTP error 429 body: undefined error: undefined response: Error: HTTP error 429 body: undefined error: undefined
  4. i guess, i have found it. confirmations.js after line 195: console.log('error: '+ response); console.log('response: '+ err); console.log('body: '+ body);
  5. i am using startConfirmationChecker with a 20 sec interval and i call manually after every trade checkConfirmations();. this was working very well. is there an debug option, so that i can see the new error message?
  6. at least since 24 hours the mobile confirmations not working anymore. was there an steam update which has destroyed your plugin functionality? or are the steam servers are just broken and steam don't care about it? i found more people with the same problem, who saying it is just showing "Invalid session errors": https://www.reddit.com/r/SteamBot/comments/51x5ty/question_current_trade_status/ the website https://steamstat.us/ is switching the whole day between "normal" and "100.0% Failed Trades" as well.
  7. ok, that should work based on your wiki. community.on('sessionExpired', function(err) { if (err) { console.log('sessionExpired: '+err); } community.stopConfirmationChecker(); if (client.steamID) { client.webLogOn(); } else { client.logOn(logon_details); } });
  8. yes, but the bot is running for hours. making hundred trades. randomly the sessionExpired is fired and then the the bot is crashing with "Cannot log onto steamcommunity.com without first being connected to Steam network". so i have added additionally client.logOn(); and guess what happens now? bot crash with "Already logged on, cannot log on again".
  9. yes, but your plugin (steam-user // downloaded 04 april) was making an auto reconnect on default for almost 2 months without any problems. since i have installed today the newest versions from steam-user, it crashed already 2 times. it should auto-reconnect instead of crashing with an fatal error. in worst case the bots would be offline for hours or even days, until i see it. what should i do now? its enough when i add to the "sessionExpired" event an client.logOn(); or how can fix this problem? thanks
  10. i need to re-open this thread. the fix is not working anymore. it was working for about 2 months flawless. today, i have updated nodejs and all plugins to the newest versions and my bots are crashing frequently with this fatal error below. log: Logged into Steam We have 19 friends. Got web session Got API key sessionExpired: Error: Not Logged In /home/nodejs/node/node_modules/steam-user/components/web.js:9 throw new Error("Cannot log onto steamcommunity.com without first being connected to Steam network"); ^ Error: Cannot log onto steamcommunity.com without first being connected to Steam network at SteamUser.webLogOn (/home/nodejs/node/node_modules/steam-user/components/web.js:9:9) at SteamCommunity.<anonymous> (/home/nodejs/node/csgopoints.js:95:9) at emitOne (events.js:77:13) at SteamCommunity.emit (events.js:169:7) at SteamCommunity._notifySessionExpired (/home/nodejs/node/node_modules/steamcommunity/components/http.js:79:7) at /home/nodejs/node/node_modules/steamcommunity/components/confirmations.js:21:10 at /home/nodejs/node/node_modules/steamcommunity/components/confirmations.js:162:4 at SteamCommunity._checkHttpError (/home/nodejs/node/node_modules/steamcommunity/components/http.js:84:3) at Request._callback (/home/nodejs/node/node_modules/steamcommunity/components/http.js:50:61) at self.callback (/home/nodejs/node/node_modules/steamcommunity/node_modules/request/request.js:200:22) code: community.on('sessionExpired', function(err) { if (err) { console.log('sessionExpired: '+err); } community.stopConfirmationChecker(); client.webLogOn(); });
  11. i am using your plugins in 12 bots and i really appreciate your work and support. so i have send you a paypal donation as "friend" (should be without paypal fees). keep up the good work!
  12. i have updated your plugins to the newest versions few minutes ago, because i have seen you have added a new event called "sessionExpired". so you mean like this? community.on('sessionExpired', function(err) { if (err) { console.log('sessionExpired: '+err); } community.stopConfirmationChecker(); client.webLogOn(); });
  13. i have the problem, that my bots will stop confirming trades (mobile auth) when they are running for a while. it is completed random, the bots can work for hours sometimes even days without problems and then they will stop to confirming the mobile auth trades. when i shutdown the bots and start them again, then they will confirm the open mobile auth confirmations. so it looks like that the steam servers are not answering or answering with an error or something? is there an debug function, so that i can see an error message why they stop confirming the trades? thank you!
×
×
  • Create New...