Dr. McKay

I'm not able to reproduce this using your code. Error reading file machineAuthToken.somelogin.txt: ENOENT: no such file or directory, open 'C:\Users\-\AppData\Local\doctormckay\node-steamuser\machineAuthToken.somelogin.txt' API GET request to https://api.steampowered.com/ISteamDirectory/GetCMListForConnect/v0001/?format=vdf&cellid=12: 200 Randomly chose websockets server ext2-atl3.steamserver.net:27023 (load = 31, wtd_load = 22.909419059753418) [W1] Connecting to WebSocket CM ext2-atl3.steamserver.net:27023 [W1] WebSocket connection success; now logging in Logging on with account name and password; fetching a new refresh token Sending message: ClientHello Sending message: Authentication.GetPasswordRSAPublicKey#1 [W1#1] Handled message: Authentication.GetPasswordRSAPublicKey#1_Response Sending message: Authentication.BeginAuthSessionViaCredentials#1 [W1] WebSocket disconnected with code 1000 and reason: [W1] Connection closed, but message queue is active. Enqueueing __CLOSE__ [W1#2] Handled message: Authentication.BeginAuthSessionViaCredentials#1_Response [W1] Handling connection close steam-session startWithCredentials exception Error: InvalidPassword at eresultError (D:\Libraries\Repos\Node Modules\Steam Handlers\steam-user\node_modules\steam-session\dist\helpers.js:14:15) at AuthenticationClient.sendRequest (D:\Libraries\Repos\Node Modules\Steam Handlers\steam-user\node_modules\steam-session\dist\AuthenticationClient.js:242:46) at async AuthenticationClient.startSessionWithCredentials (D:\Libraries\Repos\Node Modules\Steam Handlers\steam-user\node_modules\steam-session\dist\AuthenticationClient.js:77:22) at async LoginSession.startWithCredentials (D:\Libraries\Repos\Node Modules\Steam Handlers\steam-user\node_modules\steam-session\dist\LoginSession.js:361:38) at async D:\Libraries\Repos\Node Modules\Steam Handlers\steam-user\components\09-logon.js:439:26 { eresult: 5 } Handle logon response (InvalidPassword) Disconnecting without sending logoff [W1] We wanted to end connection, but it's not connected or connecting error: InvalidPassword

No publicly-known method.

You're probably getting IP rate limited.

You can't, neither of these work anymore.

Sounds like your proxies aren't standards-compliant HTTP proxies.

The GC just isn't sending any data for those values.

That's probably a bug in your code. steam-user does not attempt to login again if the error event is emitted.

If steam-user emits the error event, it's no longer attempting login. You can consider the error event to indicate a fatal error that has resulted in steam-user ceasing all operations unless you call logOn again.

Either listen for steamcommunity's sessionExpired event and then call webLogOn(), or set up a timer to call webLogOn() periodically. Hourly works good for me. webSession is the correct way to listen for new cookies. The Steam backend doesn't proactively send you new cookies when your session expires; it's up to you to request new ones.

I'd need to see the actual error message to help you, but my suspicion is that you need to update node.

You can do this with steam-session (see example), but not with steam-user only.

Sorry, I don't have any proxy providers I can personally recommend.

From what I can tell, that proxy provider is intended to MITM your traffic and solve/bypass captchas and other anti-bot tools for you. In order to do that, it needs to present its own (untrusted) HTTPS certificate. I wouldn't recommend using that provider for this purpose, but if you really wanted to, you'd need to disable TLS certificate checking in Node. This is very much not recommended, but you can do so by setting the environment variable NODE_TLS_REJECT_UNAUTHORIZED to 0.

Machine auth tokens and machine IDs are two separate things. There isn't a direct way to prevent machineAuthToken files from being saved, but you could implement a custom storage engine if you wanted, and suppress saving them that way.

What's generating "allAssetIds"? You should never see the same ID more than once.

Machine auths are not issued for accounts that are using mobile 2FA. If you want to log on to such an account without providing a code, you'll need to use a refresh token.

I need you to be more specific.

https://github.com/DoctorMcKay/node-steam-user/issues/467 You don't need to post this in two places.

They last somewhere around 200 days. It's a JWT; you can decode it and check the exp property to see when it expires.

Pretty much. You can also use node-steam-user to get notifications when your count of pending trade offers changes, which you can use to trigger a poll. steam-tradeoffer-manager works this way.

No, this isn't designed for that use-case.

Electron is a browser. steam-user is not verified to work in node-enabled Electron windows, only in the main process.

steam-user does not work in the browser.

No, nothing will work in the browser. Same-origin policy will block you. Although, in theory you could perform a CM login in the browser since that's all websocket based.

What version of steam-store?