search

Danny-Dasilva / CycleTLS

Spoof TLS/JA3 fingerprints in GO and Javascript
GNU General Public License v3.0
876 stars 167 forks source link

Sometime cycle tls does not perform request #219

Open takefy-dev opened 1 year ago

takefy-dev commented 1 year ago

Description

Hey i don't know why but sometimes cycle does not perform requests and do not even return error. I run once this function const cycleTLS = await initCycleTLS(); and store it to a variable to perform all requests for hours. I don't know if i need to reinit cycle tls on each requests

here is an exemple of how i perform requests

  const response = await this.usersManager.tlsClient.get(`url`, {
                    ja3: '772,4865-4866-4867-49195-49199-49196-49200-52393-52392-49171-49172-156-157-47-53,0-23-65281-10-11-35-16-5-13-18-51-45-43-27-17513,29-23-24,0',
                    userAgent: 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/107.0.0.0 Safari/537.36',
                    headers: this.headers,
                    proxy: this.usersManager.client.proxyManager.proxy,
                });

Issue Type

Bug

Operating System

Linux

Node Version

Node 16.x

Golang Version

None

Relevant Log Output

No response

Danny-Dasilva commented 10 months ago

It could be a proxy timeout or slow server response issue. To answer your question you only need to initialize CycleTLS once. If you have a api example that I can reproduce I'm happy to debug this.