TTL Exceeded Error - Valve's Servers Didn't Reply in Time

[wangxingzhen]

Hi,

Recently, I've been frequently encountering the error:

warn: Job Failed! S: xxxxxxxx A: xxxxxx D: xxxxxxxxx M: 0 IP: ::ffff:172.17.0.1, Err: ttl exceeded

I also noticed that CSFloat Checker is experiencing the same issue. The error message suggests that Valve's servers didn't reply in time.

Did Valve update some related code? Has anyone else encountered this issue? It was working fine for me before.

Thanks!

[lh52114]

I have the same problem. Don't know if it was caused by today's steam update.

[hunzzz1]

I also encountered the same problem. I tried changing the proxy and a new steam account but still couldn't solve it.

[hunzzz1]

Hi,

Recently, I've been frequently encountering the error:

warn: Job Failed! S: xxxxxxxx A: xxxxxx D: xxxxxxxxx M: 0 IP: ::ffff:172.17.0.1, Err: ttl exceeded

I also noticed that CSFloat Checker is experiencing the same issue. The error message suggests that Valve's servers didn't reply in time.

Did Valve update some related code? Has anyone else encountered this issue? It was working fine for me before.

Thanks!

hello, did you find a solution?

[wangxingzhen]

Hi,
Recently, I've been frequently encountering the error:

warn: Job Failed! S: xxxxxxxx A: xxxxxx D: xxxxxxxxx M: 0 IP: ::ffff:172.17.0.1, Err: ttl exceeded

I also noticed that CSFloat Checker is experiencing the same issue. The error message suggests that Valve's servers didn't reply in time.
Did Valve update some related code? Has anyone else encountered this issue? It was working fine for me before.
Thanks!

hello, did you find a solution?

So far, no

[hunzzz1]

Hi,
Recently, I've been frequently encountering the error:

warn: Job Failed! S: xxxxxxxx A: xxxxxx D: xxxxxxxxx M: 0 IP: ::ffff:172.17.0.1, Err: ttl exceeded

I also noticed that CSFloat Checker is experiencing the same issue. The error message suggests that Valve's servers didn't reply in time.
Did Valve update some related code? Has anyone else encountered this issue? It was working fine for me before.
Thanks!

hello, did you find a solution?

So far, no

I tried clearing the database cache and using the old item to request the floating point value and everything worked fine. Valve must have changed some code.

If you find a solution, please share it.

Thank you

[hunzzz1]

I have the same problem. Don't know if it was caused by today's steam update.

hello, did you find a solution?

[lastelok]

Same problem, looks like some items can be checked, some items cant :(
Using official site api

[Step7750]

Valve changes rate limits every so often -- you'll probably just need to deal with it.

Creating an issue here won't change that reality. Also, the CSFloat Inspect API that we host is not intended for developers, so we won't be supporting anyone who is using that API -- you may also be getting booted off during times like this.

[wangxingzhen]

Valve changes rate limits every so often -- you'll probably just need to deal with it.

Creating an issue here won't change that reality. Also, the CSFloat Inspect API that we host is not intended for developers, so we won't be supporting anyone who is using that API -- you may also be getting booted off during times like this.

Hi @Step7750 , thanks for your response!

I think there might be a misunderstanding. Even when I try using a different proxy and make only a single request, I still get the ttl exceeded error.

After noticing this issue in the code, I also tested it on your website and found that the inspect link doesn't work there either. It seems that Valve has introduced some TTL restrictions on inspecting items. If the same item has been inspected multiple times, it can no longer be inspected again—including when opening the inspect link in a browser and trying to view it in-game.

Has anyone else noticed this behavior?

[wangxingzhen]

Valve changes rate limits every so often -- you'll probably just need to deal with it.
Creating an issue here won't change that reality. Also, the CSFloat Inspect API that we host is not intended for developers, so we won't be supporting anyone who is using that API -- you may also be getting booted off during times like this.

Hi @Step7750 , thanks for your response!

I think there might be a misunderstanding. Even when I try using a different proxy and make only a single request, I still get the ttl exceeded error.

After noticing this issue in the code, I also tested it on your website and found that the inspect link doesn't work there either. It seems that Valve has introduced some TTL restrictions on inspecting items. If the same item has been inspected multiple times, it can no longer be inspected again—including when opening the inspect link in a browser and trying to view it in-game.

Has anyone else noticed this behavior?

After several hours of testing and verifying the behavior, I suspect that Valve has indeed implemented a TTL restriction on inspecting items. Once an item is inspected multiple times, subsequent inspection requests seem to fail, even when using different proxies or accessing via the browser.

Does anyone have further insights or potential workarounds for this limitation?

Thanks!

[Allyans3]

Valve changes rate limits every so often -- you'll probably just need to deal with it.
Creating an issue here won't change that reality. Also, the CSFloat Inspect API that we host is not intended for developers, so we won't be supporting anyone who is using that API -- you may also be getting booted off during times like this.

Hi @Step7750 , thanks for your response!
I think there might be a misunderstanding. Even when I try using a different proxy and make only a single request, I still get the ttl exceeded error.
After noticing this issue in the code, I also tested it on your website and found that the inspect link doesn't work there either. It seems that Valve has introduced some TTL restrictions on inspecting items. If the same item has been inspected multiple times, it can no longer be inspected again—including when opening the inspect link in a browser and trying to view it in-game.
Has anyone else noticed this behavior?

After several hours of testing and verifying the behavior, I suspect that Valve has indeed implemented a TTL restriction on inspecting items. Once an item is inspected multiple times, subsequent inspection requests seem to fail, even when using different proxies or accessing via the browser.

Does anyone have further insights or potential workarounds for this limitation?

Thanks!

Yes, I also noticed this behavior, that it does not want to respond to certain inspection links, no matter what inspection timeout I set and how many proxies and accounts I changed.

As you wrote above, most likely Valve introduced a limitation on 1 inspection link ~10 inspections from different accounts. But we still need to check if the owner of the item has a limitation.

The only solution is to use a single database like CSFloat. But they are against using their API by other bots, which could help them in collecting data, since I have already noticed that through the extension they cannot respond to all inspection links. Or, as an option, they can sell access to their API with a database of cached inspection links.

[Step7750]

@wangxingzhen @Allyans3 If you can provide some example inspect links that exhibit this issue, that'd be helpful for debugging -- many people say this but are actually rate limited.

Of note, this is something that could happen before as well -- typically to users who traded a lot. However, typically it would fix itself whenever Valve restarted the master GC.

[Step7750]

I did a bit more digging internally and it seems like this is more of an extension of what was mentioned previously where accounts that are trading heavily have inspect links that don't have responses from the GC.

From the examples I've seen, these seem to be trading bots (DMarket, Skinport, etc...). So it seems like the originating bug we used to observe more rarely is starting to become more prominent.

I will say however, there are two aspects to this and the vast majority of people in this issue are likely just getting rate limited (unless their inspect link truly doesn't work in-game on a regular account they use).