jensej Posted September 2, 2017 Report Posted September 2, 2017 HI.This error below is a steam error or in my script?Thanks PollFailure (Bot 123): Error: Descriptions: ETIMEDOUT Quote
Dr. McKay Posted September 2, 2017 Report Posted September 2, 2017 It timed out while contacting Steam. That happens sometimes. Either Steam is having trouble or your network is having trouble. Quote
jensej Posted September 3, 2017 Author Report Posted September 3, 2017 (edited) It timed out while contacting Steam. That happens sometimes. Either Steam is having trouble or your network is having trouble.Is any possible that steam is bloking IP address form OVH? Because every few min display this error.Moreover I have 3 different VPS and few steam account, and all of this have this error. Any Idea how I can solve this? Edited September 3, 2017 by jensej Quote
Hajagha Posted September 3, 2017 Report Posted September 3, 2017 i know who you confirms trades ? Quote
jensej Posted September 4, 2017 Author Report Posted September 4, 2017 (edited) Is there any option to speed up receiving information about the offer? Because now is around 5-25 seconds. Edited September 4, 2017 by jensej Quote
Hajagha Posted September 4, 2017 Report Posted September 4, 2017 (edited) i have Error: Descriptions: ETIMEDOUT change many VPS i confirm offer , after offer send if (stat = pendding) {confirm offer ....} ETIMEDOUT error in confirm offer after sending offer you must set confirm offer with community.startConfirmationChecker(15000, IDENTI); Edited September 4, 2017 by Hajagha Quote
jensej Posted September 4, 2017 Author Report Posted September 4, 2017 i have Error: Descriptions: ETIMEDOUT change many VPS i confirm offer , after offer send if (stat = pendding) {confirm offer ....} ETIMEDOUT error in confirm offer after sending offer you must set confirm offer with community.startConfirmationChecker(15000, IDENTI);bot.community.startConfirmationChecker(30 * 1000, bot.identitySecret); // Check confirmations about every ~30 sec Quote
Verize Posted October 26, 2017 Report Posted October 26, 2017 If you haven't figured it out by now: The confirmation checker is probably getting you rate-limited. That happens if you are sending many requests in a relatively short period of time. That's why the confirmation checker is deprecated - because it does exactly this. Accept all incoming and outgoing offers manually with the method acceptConfirmationForObject() Dr. McKay 1 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.