segressio Posted January 27 Report Share Posted January 27 Hello, confirmation of exchanges and mail change requests no longer works, I tried to use VPN - it did not help. The script gives such an error as in the screenshot, but the code itself - https://pastebin.com/e2DGu5et Quote Link to comment Share on other sites More sharing options...
Dr. McKay Posted January 28 Report Share Posted January 28 npm update Quote Link to comment Share on other sites More sharing options...
Nickers Posted January 31 Report Share Posted January 31 (edited) @Dr. McKay Hello! Mine acceptAllConfirmations started to throw "Invalid authenticator" on my windows machine. I ran "npm update" it didn't help. It still works on linux server. Internet said it can be a problem with system time but it's synced and I haven't changed timezones, so not sure what to do. What can cause this error? Edited January 31 by Nickers Quote Link to comment Share on other sites More sharing options...
Nickers Posted February 8 Report Share Posted February 8 (edited) Quote "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." My identity secret is the same on server setup, local machine and my SDA app, so it must be the time, but I have the same time and time zone on my local machine as on the server. Edited February 8 by Nickers Quote Link to comment Share on other sites More sharing options...
Nickers Posted February 14 Report Share Posted February 14 (edited) People report that they get this error when their phones language isn't set to English. I have a non-English Windows, not sure if that can be changed without re-installation. Does TOTP uses locales somewhere under the hood? Edited February 14 by Nickers Quote Link to comment Share on other sites More sharing options...
Nickers Posted February 14 Report Share Posted February 14 I downloaded laguage package and changed Windows Interface Language and Region (locale) to English(US), re-synced time and rebooted PC, still same error. Quote Link to comment Share on other sites More sharing options...
Nickers Posted April 15 Report Share Posted April 15 (edited) I still haven't figured this one out, maybe it's something obvious but I don't know... Time and timezone is the same on both linux and windows, it's wrong TZ for linux even so it works there, but not on windows. The internet says that this error can be fixed on mobile Steam authenticator by changing the language to English, but the only way to truly change the Windows language is with a clean reinstall. 🫠 Edited April 15 by Nickers Quote Link to comment Share on other sites More sharing options...
Dr. McKay Posted April 15 Report Share Posted April 15 If you're fetching your time offset and it's 1, then your clock is correct. If you're still being told that your authenticator is invalid, then the secret must be wrong. Quote Link to comment Share on other sites More sharing options...
Nickers Posted April 16 Report Share Posted April 16 But it works on a linux server (in a different country) with the same time, identity_secret and code. Quote Link to comment Share on other sites More sharing options...
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.