African Posted May 21, 2017 Report Posted May 21, 2017 Hello, I used the following code to log into my account, yet when I run the script, I'm still prompted for a Steam Guard Code in terminal.This wouldn't be an issue except the bot doesn't log in until I input the code, yet it's supposed to auto generate it itself so not to have to deal with this.I know my shared_secret is correct because it is in the exact same format as the example one. var SteamTotp = require('steam-totp'); client.logOn({ accountName: Config.username, password: Config.password, twoFactorCode: SteamTotp.generateAuthCode(Config.shared_secret) }); Any ideas what I need to change? Thanks for your help Quote
SunriseM Posted May 22, 2017 Report Posted May 22, 2017 Check if your time is offset from steam. Quote
African Posted May 22, 2017 Author Report Posted May 22, 2017 Check if your time is offset from steam. How can I do that? Quote
SunriseM Posted May 22, 2017 Report Posted May 22, 2017 Please read the whole documentations. https://github.com/DoctorMcKay/node-steam-totp#gettimeoffsetcallback . You will have to add the callback time, to getAuthCode timeOffset property. Quote
African Posted May 23, 2017 Author Report Posted May 23, 2017 (edited) Please read the whole documentations. https://github.com/DoctorMcKay/node-steam-totp#gettimeoffsetcallback . You will have to add the callback time, to getAuthCode timeOffset property.I tried this, it worked and logged in but then gave me the following error. EDIT: Nevermind, I was using the wrong value for my identity_secret. I changed it and it worked var timeOffset; //getting offset for log in SteamTotp.getTimeOffset(function(error, offset, latentcy){ timeOffset=offset; }); client.logOn({ accountName: Config.username, password: Config.password, twoFactorCode: SteamTotp.getAuthCode(Config.shared_secret, timeOffset) }); 5:19:46 PM - error: Unable to accept offer 2137947588: It looks like your Steam Guard Mobile Authenticator is providing incorrect Steam Guard codes.This could be caused by an inaccurate clock or bad timezone settings on your device.If your time settings are correct, it could be that a different device has been set up to provide the Steam Guard codes for your account, which means the authenticator on this device is no longer valid. Edited May 23, 2017 by African Quote
Dr. McKay Posted May 23, 2017 Report Posted May 23, 2017 That offset-retrieval code won't work. You need to wait for the callback before you try to do anything with that offset. 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.