Rate limit exceeded issue

Version

0.18.1

What happened?

Hi I know that previous issue was closed but ptoblem is real and its not about spamming steam servers to the point of getting ratelimited (I didnt trade whole day and got this error on first trade confirmation) its some new changes on valve's side which appeared yesterday and several 3rd party trading sites disabled their bots to fix the issue. You can also look at latest tf2automatic patchnotes they addressed and fixed it as well https://github.com/TF2Autobot/tf2autobot/releases/tag/v5.16.2

Steps To Reproduce

No response

Relevant log output

Yes, valve changed their WAF or something a little over a day ago, they are enforcing checks on HTTP request headers. TL;DR; they respond with 429 after awhile if you're not sending the headers that they're looking for.

It was confusing, it is still a rate limit in that without the headers it still works for awhile, but with all the correct headers present in the requests the rate limits seem much higher / normal.

There is some discussion on it here:

https://dev.doctormckay.com/topic/5946-new-request-limits-429-error/

I have this problem too. Can't confirm my trades now. Any workaround?

funny enough but old bud SDA from 2024 ([Version 1.0.15]) works just fine after session refresh

You can also look at latest tf2automatic patchnotes they addressed and fixed it as well

heres link to specific fix TF2Autobot/node-steamcommunity@2ccb559

Ah I see. Thank you, this is very helpful.

New release is going out now. Haven't tested it myself, but let me know if it works.

Thanks for the update but unfortunately I still get the same error

C:\Users\shocK\Desktop\steamguard>steamguard.exe -u *** confirm
INFO reading manifest from C:\Users\shocK\AppData\Roaming\steamguard-cli/maFiles
INFO ***: Checking for confirmations
ERROR Failed to get confirmations: Remote failure: Valve's server responded with a failure and said: Rate limit exceeded
ERROR Remote failure: Valve's server responded with a failure and said: Rate limit exceeded

I'll have to look more closely at it later.

In the meantime, @pullfrog file a PR to add the accept language header for all of the confirmations http requests

Opened #511 to add Accept-Language: en-US,en;q=0.9 to all confirmation HTTP requests (/mobileconf/getlist, /mobileconf/ajaxop, /mobileconf/multiajaxop, and /mobileconf/details/:id). The steamguard library tests and cargo check --features qr both pass.

Task list (4/4 completed)

Explore confirmation HTTP request code
Add accept-language header to all confirmation HTTP requests
Build and test changes
Create PR and push branch

^{｜ View workflow run ｜ via Pullfrog ｜ Using Kimi K2 (free via Pullfrog for OSS) ｜ 𝕏}

I'll have to look more closely at it later.

I was able to get it working with the Accept-Language headers and replacing the steamguard-cli useragent with Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/118.0.0.0 Safari/537.36.

Just the Accept-Language headers still got 429'd.

When I tested it, changing the user agent was not necessary. Only the accept language header

It’s running intermittently on version 0.18.3; sometimes an error pops up, and sometimes it doesn’t. Is it just me?
Maybe UA is necessary?

It’s running intermittently on version 0.18.3; sometimes an error pops up, and sometimes it doesn’t. Is it just me? Maybe UA is necessary?

Yes for me too.

fix: confirmation rate-limit errors (dyc3#510)

I'm not entirely convinced the user agent is necessary. I tried with a few different accounts, and initially it was rejecting my requests with 429. Then it was fine, and now I'm trying and its giving me 429 again. Seems to only apply to the mobile confirmations endpoints though, not the ones that have "public" APIs, but that's me speculating.

@pullfrog can you file a PR to change the user agent (just for the confirmation requests) to the one that is in this thread? plz thank u

Opened #512 to change the User-Agent header for all confirmation HTTP requests to the Chrome 118 / Windows 10 browser user agent from the issue thread. cargo check (including --features qr) and cargo test -p steamguard both pass.

Task list (5/5 completed)

Find the user agent mentioned in the issue thread
Locate confirmation request code and existing user agent handling
Change user agent for confirmation requests
Run tests/build
Create branch and PR

^{｜ View workflow run ｜ via Pullfrog ｜ Using Kimi K2 (free via Pullfrog for OSS) ｜ 𝕏}

change: use Chrome 118 user agent for confirmation requests (#512)

If someone wants to try #512, it's merged. Im on mobile so I can't until I get back to my desk

Still this problem actual

This should be fully fixed in 0.18.4.

Nah, the problem is back it was fine before

Navigation Menu

Repository navigation

Rate limit exceeded issue #509

Version

What happened?

Steps To Reproduce

Relevant log output

1 remaining item

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Rate limit exceeded issue #509

Description

Version

What happened?

Steps To Reproduce

Relevant log output

Activity

SuperRaWR commented on Jul 11, 2026

deREALshocK commented on Jul 11, 2026

microdood commented on Jul 11, 2026

microdood commented on Jul 11, 2026

dyc3 commented on Jul 11, 2026

dyc3 commented on Jul 11, 2026

deREALshocK commented on Jul 11, 2026

dyc3 commented on Jul 11, 2026

pullfrog commented on Jul 11, 2026

idomanteu commented on Jul 11, 2026

1 remaining item

dyc3 commented on Jul 12, 2026

saramaka-creator commented on Jul 12, 2026

deREALshocK commented on Jul 12, 2026

dyc3 commented on Jul 12, 2026

dyc3 commented on Jul 12, 2026

pullfrog commented on Jul 12, 2026

dyc3 commented on Jul 13, 2026

Remakkeo commented on Jul 15, 2026

dyc3 commented on Jul 17, 2026

Remakkeo commented on Jul 22, 2026

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions