TTL Exceeded Error - Valve's Servers Didn't Reply in Time #234
Comments
|
I have the same problem. Don't know if it was caused by today's steam update. |
|
I also encountered the same problem. I tried changing the proxy and a new steam account but still couldn't solve it. |
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 |
hello, did you find a solution? |
|
Same problem, looks like some items can be checked, some items cant :( |
|
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. |
|
@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. |
|
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). |
|
I have been seeing this error as well while inspecting items from trading bots. But whats been bugging me is that requests to my container are taking minutes to complete (at least 3 minutes). I have seen this message alongside some TTL exceeded ones: |
You're likely just getting rate limited -- what is your timeout to receive a response from the GC? I'd wager it isn't 3 minutes and you're just retrying the request repeatedly? |
|
Could be, I will tweak some things around. But I have been running this same container for a long long time and only now it stopped working. And It seems account related (owner of link) |
That's because rate limits were changed around 2 days ago. |
|
@Step7750 I have these three inspection links to start with. Try inspecting them without a connected database. Mine and other public inspectors send 504 status code. I don't know what rate limit you're talking about, but this is something new. It's unlikely that the inspection block will last more than a day. Last time, this increase was a couple of seconds. I watched my inspector all day and he was only able to process a third of the inspection links. Of course, I really hope that this problem will be fixed next Tuesday when the servers are rebooted, but if not, it will greatly affect marketplaces, both the Steam Market and external ones. steam://rungame/730/76561202255233023/+csgo_econ_action_preview%20S76561198389343237A35674997176D9235300529159798806 |
|
@Allyans3 This issue previously existed as well, it just didn't happen as often. At least at CSFloat's scale, we saw "large traders" hit it every week. Unfortunate that it is more common now, perhaps Valve will fix it since it does seem to effect regular users at a more meaningful rate.
Such a low rate of being able to inspect items is more likely due to rate limits than these items that can't be inspected in-game. However, our systems are probably quite a bit different than yours, so perhaps there's something else at play. |
|
@Step7750 These items cannot be inspected in the game either. I thought maybe this only affected bots that request item information 24/7, but that’s not the case. I tried inspecting them using my main in-game account, which has been almost inactive in trading for over a year and was mainly used for gaming and nothing happened in the game. I tested this on several public inspectors and screenshot-generating services, and they all return an error. I don't think that any inspector is significantly different from the others. The only difference is that you have a huge number of bots and some kind of delay configuration, but you also have an enormous flow of inspection requests, which can equalize compared to other inspector services. In any case, you are one of the first to create this kind of inspector, and now it’s hard to imagine how your system works. And some discussion links: |
|
@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. |
Hi,
Recently, I've been frequently encountering the error:
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!
The text was updated successfully, but these errors were encountered: