client.fetchInvite throwing errors every single time
aaronmansfield5 opened this issue · comments
Aaron Mansfield commented
Which package has the bugs?
The core library
Issue description
HTTPError [TypeError]: Reached maximum redirect of 20 for URL: http://discord.com:443/dashboard/
at RequestHandler.execute (D:\Downloads\JoinServer\node_modules\discord.js-selfbot-v13\src\rest\RequestHandler.js:213:15)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async RequestHandler.push (D:\Downloads\JoinServer\node_modules\discord.js-selfbot-v13\src\rest\RequestHandler.js:63:14)
at async Client.fetchInvite (D:\Downloads\JoinServer\node_modules\discord.js-selfbot-v13\src\client\Client.js:339:18)
at async Client.<anonymous> (D:\Downloads\JoinServer\app.js:77:21) {
code: 500,
method: 'get',
path: '/invites/powerfulstudio?with_counts=true&with_expiration=true',
requestData: { json: undefined, files: [], headers: undefined }
}
Code sample
const client = new Client({
captchaSolver: function (captcha, UA) {
console.log(`${colours.white}[${colours.blue}INFO${colours.white}]: Attempting to solve hCaptcha ${colours.reset}`);
return solver
.hcaptcha(captcha.captcha_sitekey, 'discord.com', {
invisible: 1,
userAgent: UA,
data: captcha.captcha_rqdata,
})
.then((res) => res.data);
},
checkUpdate: false,
http: {
headers: {
"x-super-properties": "xxxx" //removed for privacy
},
agent: httpsAgent
},
captchaWithProxy: true,
proxy: process.env.PROXY_ACCESS,
restRequestTimeout: 60 * 1000,
interactionTimeout: 60 * 1000,
restWsBridgeTimeout: 5 * 1000
});
await client.fetchInvite(link).then(async (invite) => {
Package version
3.1.3 & 3.1.4
Node.js version
v 21.1.0
Operating system
Windows
Priority this issue should have
Medium (should be fixed soon)
Checklist
- I have searched the open issues for duplicates.
- I have shared the entire traceback.
- I am using a user token (and it isn't visible in the code).
Additional Information
Yeah it was working fine, I understand Discord's rate-limits but it's been limited for a few days now and it throws even on new tokens when I'm using random UAs, different X-Super-Properties and dynamic proxies, so this really shouldn't be an issue, it doesn't work in my Docker environment either.