Invalid authenticator error

[ghost]

I'm using steamguard cli to confirm trades from tf2autobot because SDA isnt being supported.
Send a trade to my bot, but he can't confirm it:

then I tried to confirm it manually with steamguard confirm

yeah there is said that its not steamguard CLI bug, but im waiting for 3-4 days, it worked well earlier, like week ago, I didn't configure anything in steamguard CLI, do you have some ideas how to solve it?

[dyc3]

Unfortunately, no I don't have a clue what's wrong here. It's possible you're getting rate limited. The mobile confirmations API does not work like most steam apis, so it doesn't necessarily elaborate on why the failure occurred. You could try running steamguard cli with -v debug or -v trace (trace may show sensitive info) to peek inside to see what's happening.

[KaloyanAleksiev4]

Dear steamguard-cli devs,

I have a similar issue. I have tried running stemaguard-cli on multiple machines (windows and linux, local and vps) but the issue seems to be persistent.

I ran it with -v debug as you suggested:

INFO [REDACTED_USERNAME]: Checking for confirmations DEBUG Confirmations response: {"success":true,"conf":[ {"type_name":"Trade Offer","id":"[REDACTED]","summary":["REDACTED"]}, {"type_name":"Trade Offer","id":"[REDACTED]","summary":["REDACTED"]} ]} INFO accepting all confirmations DEBUG send_multi_confirmation_ajax() response status code: 200 OK DEBUG send_multi_confirmation_ajax() response body: "{\"success\":false}" WARN submit confirmation result: Remote failure: Valve's server responded with a failure and did not elaborate any further.

Here is the same command ran with -v trace as you suggested:

`
INFO [REDACTED_USERNAME]: Checking for confirmations
TRACE Request body: CTwoFactor_Time_Request { sender_time: None, ... }
DEBUG Response HTTP status: 200 OK
TRACE Response body (decoded): CTwoFactor_Time_Response {
server_time: Some(1752916849),
skew_tolerance_seconds: Some(60),
...
}
DEBUG Confirmations response:
{
"success": true,
"conf": [
{
"type_name": "Trade Offer",
"id": "[REDACTED_ID]",
"summary": ["redacted"]
},
{
"type_name": "Trade Offer",
"id": "[REDACTED_ID]",
"summary": ["redacted"]
}
]
}
INFO accepting all confirmations

TRACE send_multi_confirmation_ajax() response:
Response {
status: 200,
url: https://steamcommunity.com/mobileconf/multiajaxop,
...
}
DEBUG send_multi_confirmation_ajax() response body:
{"success":false}
WARN submit confirmation result:
Remote failure: Valve's server responded with a failure and did not elaborate any further.

INFO retrying in 3 seconds (attempt 1)
...
(retries 2 and 3 omitted for brevity — same result)
...
ERROR Failed to respond to some confirmations.
`

The above outputs were derived from Ubuntu in VirtualBox and using steamguard-cli v0.17.1.

I've confirmed:

• The .maFile is valid.
• Steam Guard is active and synced.
• The trade offers are visible on the mobile app.
• Same issue With different network (no proxy) (different proxy also)
• Retrying results in the same issue.

Could this be related to:

• Steam's confirmation API throttling?
• Nonce mismatch or time drift (QueryTime responses look okay)?
• Something recently changed in Steam's backend?

None of my bots are able to send offers because of this issue.
Any insights as to how to deal with this are greatly appreciated 🙏

Thank you in advance.
Kind regards,
Kaloyan

[dyc3]

There was a recent steam update that requires you to go into the trade offer UI and accept a prompt. After you do that, confirmations should work again.

[KokoAlexiev]

omg im so dumb

[KokoAlexiev]

thank you

[ghost]

@KokoAlexiev happy for you, could you describe what did you do exactly?

[KokoAlexiev]

i did exactly as @dyc3 proposed. I have a large number of bots and II operate them 100% headless, so i never actually went into steam after the trade reverse update.

You just have to go into https://steamcommunity.com/id/{steam_id}/tradeoffers/ and acknowledge the new update. If you dont do that you wont be able to confirm any offer

[ghost]

doing it manually it raises an error too

[dyc3]

You are probably getting rate limited. The confirmations API doesn't provide enough info to know the true cause of the error.

[ghost]

Well, im still having the issue like in original post, pressed OK on new update, but nothing happened

[dyc3]

Yeah. I'm saying that there is nothing to be done about it except wait, and don't hit the endpoint in the meantime.

[ghost]

@dyc3 I solved it, you will never guess what was the problem
one of tf2autobot json files was corrupted, but it wasn't saying about json