Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TTL Exceeded (New Valve Restrictions) #131

Closed
SoloMReal opened this issue Apr 19, 2023 · 20 comments
Closed

TTL Exceeded (New Valve Restrictions) #131

SoloMReal opened this issue Apr 19, 2023 · 20 comments

Comments

@SoloMReal
Copy link

warn: Job Failed! S: 76561199401338644 A: 29598639405 D: 14592448071216162737 M: 0 IP: Err: ttl exceeded

@aavvaavvaa
Copy link

same problem, also after that ttl exceeded my ip is on some kind of restrictions on steam, i can't even inspect an item inside the game, ingame inspection works only if i use vpn

@borisenko09
Copy link

The same problem also appeared, it is possible to use a proxy for each account when logging in will help to obtain information.

@aavvaavvaa
Copy link

The same problem also appeared, it is possible to use a proxy for each account when logging in will help to obtain information.

Also I used ipv6 proxies via CMClient before and everything was okay until today. Did you tested it already ? What proxies are you using ipv4 or ipv6 ?

@borisenko09
Copy link

The same problem also appeared, it is possible to use a proxy for each account when logging in will help to obtain information.

Also I used ipv6 proxies via CMClient before and everything was okay until today. Did you tested it already ? What proxies are you using ipv4 or ipv6 ?

I just started with ipv4 a couple of hours ago the update came out, everything worked in the config file 'proxies': [], add the proxy there in the form "http://log:pass@ip:port"

@aavvaavvaa
Copy link

The same problem also appeared, it is possible to use a proxy for each account when logging in will help to obtain information.

Also I used ipv6 proxies via CMClient before and everything was okay until today. Did you tested it already ? What proxies are you using ipv4 or ipv6 ?

I just started with ipv4 a couple of hours ago the update came out, everything worked in the config file 'proxies': [], add the proxy there in the form "http://log:pass@ip:port"

But my proxies are ipv6 so it wouldn't work if i just add an ipv6 proxy to the list, i'm using CMClient but it doesn't work right now and i getting ttl exceeded, so i have no clue how to fix this.

@Tankonyako
Copy link

i got also this today, and cannot figure out, if im add proxies after some time it happen again

@SoloMReal
Copy link
Author

What if there’s no login/username and password in the proxy, for example could I just do:
http://127.0.0.1:8000
^ just an example
Also how many proxies do you think we need?

@Allyans3
Copy link

Allyans3 commented Apr 19, 2023

info: ***************** Log on OK
info: ***************** Initiating GC Connection
debug: Sending GC message ClientHello
debug: Sending hello, setting timer for next attempt to 2000 ms
debug: Got handled GC message ClientWelcome
debug: Unknown SO type 2 with 1 items
debug: Unknown SO type 7 with 1 items
debug: GC connection established
info: ***************** CSGO Client Ready!
debug: Got unhandled GC message 9173
warn: ***************** CSGO unready (2), trying to reconnect!
warn: ***************** Logged off, reconnecting! (3, NoConnection)

Bots can't work with proxy, without is fine. HTTP with log:pass

Upd: the problem was with my proxies

@Step7750 Step7750 changed the title TTL Exceeded TTL Exceeded (New Valve Restrictions) Apr 19, 2023
@Step7750
Copy link
Member

Hey foks,

Yes, Valve has imposed new IP/bot rate limits. The exact limits are unknown at this time, but you likely need to use a host of proxies in the interim,

#132 provides this support in v1.4.3

If you have more valuable findings, feel free to share here.

@Luksch187
Copy link

Can you already say if your Inspect API will be opened for bots again and when? Or should I rather work on self hosting?

@gaelsuv
Copy link

gaelsuv commented Apr 20, 2023

Hey foks,

Yes, Valve has imposed new IP/bot rate limits. The exact limits are unknown at this time, but you likely need to use a host of proxies in the interim,

#132 provides this support in v1.4.3

If you have more valuable findings, feel free to share here.

What if I was using directly the endpoint API to pass in inspect links? Would self hosting do the trick and start making my script work again? Thanks for your help.

@SPr3D
Copy link

SPr3D commented Apr 20, 2023

Hello! I am sending requests through the python to CSGOFloatAPI, but it it gives me an error:
<Response [400]>
{"error":"Bots are temporarily not allowed on CSGOFloat Inspect API due to new rate limits imposed by Valve","code":16,"status":400}
Can I solve this problem somehow?

@Allyans3
Copy link

Valve removed old endpoint for fetching inventory https://steamcommunity.com/profiles/****************/inventory/json/730/2

{
"success": false,
"Error": "Unsupported request"
}

@gaelsuv
Copy link

gaelsuv commented Apr 20, 2023

Valve removed old endpoint for fetching inventory https://steamcommunity.com/profiles/****************/inventory/json/730/2

{
"success": false,
"Error": "Unsupported request"
}

And? Is this the one being called under the hood by Inspect public API?

@Allyans3
Copy link

CSGOFloat Extension use it

@LexaCoronos
Copy link

How can I fix it?
{"error":"Bots are temporarily not allowed on CSGOFloat Inspect API due to new rate limits imposed by Valve","code":16,"status":400}

@AboutSange
Copy link

Hey foks,

Yes, Valve has imposed new IP/bot rate limits. The exact limits are unknown at this time, but you likely need to use a host of proxies in the interim,

#132 provides this support in v1.4.3

If you have more valuable findings, feel free to share here.

Hi, thank you for providing the proxies params in config.js, but after I set proxies in config.js, I get error like this:

error: Error logging in xxx: message=Proxy connection timed out, stack=Error: Proxy connection timed out
    at ClientRequest.<anonymous> (/usr/src/csgofloat/node_modules/steam-user/components/connection_protocols/tcp.js:69:29)
    at ClientRequest.emit (node:events:513:28)
    at Socket.emitRequestTimeout (node:_http_client:848:9)
    at Object.onceWrapper (node:events:627:28)
    at Socket.emit (node:events:525:35)
    at Socket._onTimeout (node:net:570:8)
    at listOnTimeout (node:internal/timers:569:17)
    at process.processTimers (node:internal/timers:512:7)
info: Logging in xxx

and my proxies params like

'proxies': ['http://ip1:port1', 'http://ip2:port2']

and I have tested that all my proxies can access "https://httpbin.org/ip" normally, diff proxy has diff response time when access the website, and the response time is whthin 1-5 seconds, and it's always return 200 response code, so I don't know what the problem is and how I can solve it.

@LexaCoronos
Copy link

LexaCoronos commented Apr 22, 2023

Hi, how to send to your api the special request used proxy for it? I code in Java and don't use any library by csgofloat. May you add support use proxy in http link.
Request example:
https://api.csgofloat.com/?m=6048939083370871310&a=29653911196&d=9406593057029549017&proxy=**.**.**.**:8000

@Step7750
Copy link
Member

Closing since this is not an active issue, you need to spam the GC less and abide by Valve rate limits.

@SoloMReal
Copy link
Author

SoloMReal commented May 1, 2023

Hey foks,
Yes, Valve has imposed new IP/bot rate limits. The exact limits are unknown at this time, but you likely need to use a host of proxies in the interim,
#132 provides this support in v1.4.3
If you have more valuable findings, feel free to share here.

Hi, thank you for providing the proxies params in config.js, but after I set proxies in config.js, I get error like this:

error: Error logging in xxx: message=Proxy connection timed out, stack=Error: Proxy connection timed out
    at ClientRequest.<anonymous> (/usr/src/csgofloat/node_modules/steam-user/components/connection_protocols/tcp.js:69:29)
    at ClientRequest.emit (node:events:513:28)
    at Socket.emitRequestTimeout (node:_http_client:848:9)
    at Object.onceWrapper (node:events:627:28)
    at Socket.emit (node:events:525:35)
    at Socket._onTimeout (node:net:570:8)
    at listOnTimeout (node:internal/timers:569:17)
    at process.processTimers (node:internal/timers:512:7)
info: Logging in xxx

and my proxies params like

'proxies': ['http://ip1:port1', 'http://ip2:port2']

and I have tested that all my proxies can access "https://httpbin.org/ip" normally, diff proxy has diff response time when access the website, and the response time is whthin 1-5 seconds, and it's always return 200 response code, so I don't know what the problem is and how I can solve it.

I have the same issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests