Discord Ban mega-thread! (Discord bot / Something took too long to do)

Hey Cori!

There are people currently relying on the bot, and I would like if you could fix it ASAP. Also, I added the console error thing, but didn’t get any response.

1 Like

I just recently got this error on my bot, too. I added a catch to login, and all that comes up is [Function: bound consoleCall].
Project name is leaf-bot.

EDIT: My bad, I did add the catch, but instead of doing just console.error I had console.log(console.error) due to previous attempts to try and catch out the error. The error message is:

Error: Something took too long to do.

    at timeout.client.setTimeout (/app/node_modules/discord.js/src/client/ClientManager.js:40:57)

    at Timeout.setTimeout [as _onTimeout] (/app/node_modules/discord.js/src/client/Client.js:433:7)

    at ontimeout (timers.js:466:11)

    at tryOnTimeout (timers.js:304:5)

    at Timer.listOnTimeout (timers.js:267:5)

Same issue. Project name is bermuda-fn. My other bots are working fine its just this one

Error: Something took too long to do.

at timeout.client.setTimeout (/rbd/pnpm-volume/0eee7f8a-59cf-4bee-83a9-d7c867095478/node_modules/.registry.npmjs.org/discord.js/11.4.2/node_modules/discord.js/src/client/ClientManager.js:40:57)

at Timeout.setTimeout [as _onTimeout] (/rbd/pnpm-volume/0eee7f8a-59cf-4bee-83a9-d7c867095478/node_modules/.registry.npmjs.org/discord.js/11.4.2/node_modules/discord.js/src/client/Client.js:433:7)

at ontimeout (timers.js:436:11)

at tryOnTimeout (timers.js:300:5)

at listOnTimeout (timers.js:263:5)

at Timer.processTimers (timers.js:223:10)
1 Like

The name of my project and odium-bot

1 Like

Hi All!

Cori, a staff member will be fixing this later this morning.

1 Like

It looks like we have a few IP addresses that have been blacklisted. I’ll be working with another Glitch staff member to resolve that on our end in just a little while.

@Coding are you saying that Discord is also taking a look at this from their end? Do you have a contact that you’re working with - we’d like to be able to resolve this on a more permanent basis and it would help to know someone who’s already aware of this on the Discord side of things.

1 Like

Hey Cori!

I didn’t say that, but I could try to find some discord staff to contact. Can I have a status update plz?

Oh I see. I was saying it as you would be looking into it, not that I’m talking to you.

1 Like

I wasn’t sure what you meant by

I’ll be reaching out to them later today to start the process, but if you already had an ongoing contact I was going to try to horn my way into that conversation. If that’s not what you meant then don’t worry about it.

I’m sitting down with someone else on our team to go over our process at 11ET and I think this will be resolved soon thereafter from our end - at least for this instance.

4 Likes

Ok, for some reason, I opened the projects and it installed node v8.14.0 for some reason, and now it seems to work. Very strange for so many people having the same issue and nobody knows the cause…

3 Likes

well we know the cause now. Some IPs were being banned.

2 Likes

Wait same! It works now!

2 Likes

Hey folks, sorry for the delayed update; we’ve removed a few of the hosts that Discord had banned so your projects are starting up on new hosts with new IPs that haven’t been banned. That should resolve the existing issues (and has nothing to do with reinstalling). There are a few more hosts that seem to have been banned that we’ll also be cleaning up today, but none of those seem to be related to any of the projects mentioned in the topic.

Additionally as I noted above, we’re hoping to work with the Discord folks to work out a better way to handle this.

6 Likes

Thanks! You really helped!

(I had like 1000s of users waiting on the bot :stuck_out_tongue: )

3 Likes

Hello for me everything seems back to normal thank you to the staff of glitch and Cori

4 Likes

Started again for me…

3 Likes

Nevermind. It was fixed.

2 Likes

I have the same problem. My bot is DTB-bot

2 Likes

Yeah, looks like it struck my bots again, this time on ajota and arashira.

2 Likes

This is also happening with my project, nootnootbot

2 Likes

Hey folks it looks like we had a host that was temporarily banned but it appears to have cleared up.

Let us know if you continue to see problems.

2 Likes