inspect: TTL Exceeded Error - Valve's Servers Didn't Reply in Time
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!
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 21 (10 by maintainers)
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?
@Allyans3 Yeah, it seems to affect a decent amount of items – in my own inventory there may be a hit rate of 50% for older items. We aren’t experiencing this as heavily at CSFloat due to the existing cache.
This is something that Valve would need to fix regardless – which seems like it’d reasonably happen since this is affecting regular users.
I’m going to close out this issue since there isn’t anything to do on our end here.
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!