Unhandled rejection CloudflareError: 1020

[MasterProgs]

• What version of Cloudscraper are you using? 4.1.2
  • node -p 'require("cloudscraper/package.json").version'
• What version of Node.js are you using? (Please share the process information)
  • node -p process v10.16.3
• When did the problem start occurring? This night.
• How often does the problem occur? Everytime
• What is the URL? https://haapi.ankama.com/json/Ankama/v2/Api/CreateApiKey
• Are there any similar issues? Yeah but doesn't help me.

Code snippet

    var options = {
        uri: 'https://haapi.ankama.com/json/Ankama/v2/Api/CreateApiKey',
        formData: { login: username, password: password, long_life_token: 'false' }
        };
        
        cloudscraper.post(options, function(error, response, body) {
            if (error) {
                console.log("an error has occured");
            } else {
                console.log(body, response);
            }
        });

Thank's.

[MasterProgs]

I'm not blacklist. I tried from my pc and VPS (same thing), even using proxies.

[MasterProgs]

#264

@MasterProgs that's great. Do you mind helping others out by mentioning what specifically worked for you?

As in, if it was a cipher string, which one and what's the OS/CPU?

The unhandled rejection is referring to promise rejection. Cloudscraper returns a promise by default and it must be caught/handled: cloudscraper.post(uri).catch(console.error). If you prefer the callback style, see the requester /docs/examples in this repo. You would need to pass request as the requester.

[MasterProgs]

I use ':!ECDHE+SHA:!AES128-SHA:!AESCCM:!DHE:!ARIA' on WINDOWS.

My bad I have submit my message but the topic was closed (by me) and my message did not send.

[MasterProgs]

@pro-src By the way, when I use this cyphers :!ECDHE+SHA:!AES128-SHA:!AESCCM:!DHE:!ARIA or ECDHE-RSA-AES128-GCM-SHA256 without proxy options it's works.

But with a proxy configuration (post and get) -> CloudflareError (Error 1020).

Do you know why I can't use my own proxies ? Yesterday I've not had any issues.

Cloudflare's fingerprinting/blacklisting. They use deep learning algorithms to detect bot-like patterns and in some cases will even send your IP to their Bandwidth Alliance Partners to have your bot kicked offline. They've promised to start cracking down on bots and the increase in bug reports is mostly likely related to that ongoing effort. Be sure that Cloudflare can determine whether you're using a VPN, residential, or some other cloud service provider.

Have you tried: cloudscraper.defaultParams.agentOptions.ciphers += ':!SHA'?

[MasterProgs]

Yeah I tried but still not working :/

If you search around in the issues, I've provided more elaborate explanations for what the problem is in the majority of cases. Namely, the TLS signature algorithms. You used to be able to just use TLSv1 which doesn't have that TLS extension (insecure btw) but even that isn't working for some sites now. If you can compile Node.js with BoringSSL, that will solve the TLS problems. Electron does that but it's not any easy task. You could compile libcurl with BoringSSL and create a native extension for Node.js. But there's nothing we can really do for a fool proof fix without compiling something.

Have a look at https://www.google.com/search?q=residential+proxy+service

Also, other languages have this problem as well, such as, Python and Go, no good solution there either.

[MasterProgs]

And with python we've got the same issues ?

Thank you for time, I appreciate.

Yup.

[MasterProgs]

Right,
Maybe doesn't matter to use proxies hope so that they don't take our IP (auth) and only IP (world).

I know someone who build a simple script with puppertee (phantomJs). In back his web nav open a web page to bypass that problem. (Not very perf).

nodejs/node#24818