Dr. McKay

Steam's reboot about five minutes ago seems to have fixed this.

That's no different from how steam-user does it.

I'm not sure I would bother. It's starting to look to me as if webLogOn just won't work at all.

You could try using this: https://github.com/DoctorMcKay/node-steamcommunity/wiki/SteamCommunity#marketsearchoptions-callback

https://steamerrors.com/26

Your screenshot showed your API key, so I removed it. It doesn't look like you're sending a trade offer at all in your screenshot.

console.log('Offer ' + offer.id +' sent, but requires confirmation'); console.log('Offer '+ offer.id +' sent successfully'); Neither of these are running?

It's starting to appear webLogOn will fail if you already have a valid web session. I'm unsure as to whether this is a time-based limit or not, but I can reliably get 403s if I call webLogOn 1 second after webSession gets emitted. Relogging the CM session will work more often than not (all the time? unsure).

I've been investigating this for the past hour and a half or so, and it appears that Valve did indeed break something with client-based web logons last night. The API is giving quite a lot of 403s with the same error message that you get if you use a bad nonce. Therefore, my suspicion is that there's some kind of miscommunication between the CM (the server which most likely generates the nonce and issues it to you), and whichever server consumes those nonces to turn them into cookies. I've tried adding some delays just in case the communication between those servers is slow, but that doesn't appear to have helped anything. Re-logging your client seems to solve the problem, at least temporarily. You may want to try doing that if you don't get a web session within a reasonable amount of time after requesting one. I've alerted Valve, but there's no telling if or when they'll take action.

acceptConfirmationForObject takes care of finding the correct confirmation for a given offer ID. @maraya: What's your output?

Best I can tell, web logons became finnicky ever since the Steam maintenance last night.

You have to use startConfirmationChecker before you use checkConfirmations, but I don't generally recommend that anymore due to Steam load concerns.

Are you up to date?

I'm sorry, but I can't reproduce this. It works fine on my end.

Yes, you do need to actually log into the account first. Please show your code.

client.changeEmail({"password": password, "newEmail": myemail})

You can use acceptConfirmationForObject.

That's not the correct signature.

Yes, those codes will work anywhere you sign into Steam.

Déjà vu.

https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/TradeOffer#properties itemsToReceive

My mistake. I've updated those release notes. Get rid of the curly braces inside your SteamUser constructor: new SteamUser(steamclient). If you do it properly, all communication SteamUser does with Steam goes over the proxy.

The user event will be emitted anytime someone's persona data changes (e.g. they go online/offline or start/quit a game). Also, at any time the users property contains the current persona data for everyone we know about.

It's setHttpProxy, not setHttpSocket.

Your IP got temporarily banned, yes. That's what 429 means.