spamming with html content about hooman

[sayem314]

403 === captcha. Did you check with captchaKey? Also, why are you printing error body, this is why console was spammed.

[andress134]

403 === captcha. Did you check with captchaKey? Also, why are you printing error body, this is why console was spammed.

I know 403 is captcha, but the target url is not capcha, is uam

i think just when im using proxies, i get it, and error

(node:21523) UnhandledPromiseRejectionWarning: TypeError [ERR_INVALID_ARG_TYPE]: The "options.port" property must be one of type number or string. Received null at lookupAndConnect (net.js:995:13) at Socket.connect (net.js:974:5) at Object.connect (net.js:184:17) at HttpsProxyAgent.<anonymous> (/root/node_modules/https-proxy-agent/dist/agent.js:95:40) at Generator.next (<anonymous>) at /root/node_modules/https-proxy-agent/dist/agent.js:8:71 at new Promise (<anonymous>) at __awaiter (/root/node_modules/https-proxy-agent/dist/agent.js:4:12) at HttpsProxyAgent.callback (/root/node_modules/https-proxy-agent/dist/agent.js:85:16) at HttpsProxyAgent.addRequest (/root/node_modules/agent-base/dist/src/index.js:181:38) (Use node --trace-warnings ...to show where the warning was created) (node:21523) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag--unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2) (node:21523) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.