Closed VladimirKorzh closed 11 years ago
Well, try to log in with Steam as the bot and see what's going on. It's probably the new Steam Guard feature malfunctioning.
Closing since it's a Steam issue.
Wow.... =( Thank you. That is exactly what is causing the issue. Is there any way I could get a valid sentry file from my desktop? I can use steam and trade just fine if I log in using the windows browser, but not under bot on my linux box server. Waiting 15 days is plain stupid.
You could give it a try. It's the file named "ssfnXXX" in your Steam directory - use its SHA-1 hash. Let me know if that works.
Once I will be able to test it, I will tell you the result.
Is this possible getting the sentry file from steam?
I am using this with node-steam-trade and it was working just fine for quite some time. Today my users reported that bot is not trading with them. After some investigation I've figured out that the bot is not able to send trade requests. I've read the documentation, that you have provided and thought that I have to refresh my cookies more frequently, however that is not the case. Here is the message that my users see, when they try to invite the bot to trade with them.
"ICL.bot is not available to trade. More information will be shown to ICL.bot if they invite you to trade."
I can provide any additional information that you might need. The strange thing is - it was working for a couple of days just fine.
Here is a link to my source code if you need it: https://github.com/VladimirKorzh/ICL/blob/master/betting/jankbot.js