That does seem like odd behavior, but we’re not seeing anything out of the ordinary on any of our hosts. @midnight_ocean, @razefeixx, and @iBisho can you provide project name so we can take a closer look?
The same problem started to my bots too. It also doesn’t look like it is the code, since nothing were changed, and it is returning the same “Something took too long” timeout on login.
(node:3217) UnhandledPromiseRejectionWarning: Error: Something took too long to do.
at timeout.client.setTimeout (/rbd/pnpm-volume/ba5c37af-02df-4742-91c4-c5ceb7c6f78a/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/ba5c37af-02df-4742-91c4-c5ceb7c6f78a/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)
(node:3217) 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(). (rejection id: 6)
(node:3217) [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.
I’ve also been having the same issue with my bot where it says that it is live, but not online on discord. At first I couldn’t figure it out so I commented out certain parts of the code that dealt with timeouts and cooldowns. Funnily enough it seemed like it worked and it came back online on Discord however it immediately went back to it’s previous state and I can not figure out what the error means. My bot’s name is zielo-rules.
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.
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)
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.
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.
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…
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.
Seemed to have worked for the first few hours, but then my project arashira can’t connect again. The other one that was affected at the same time isn’t having an issue yet.
I now have the exact same problem, I am also relatively busy now, so I noticed it around 7 hours after it happened. My project is https://n-emoter.glitch.me, and I hope it gets resolved as soon as possible.
heh, I feel like a regular to this thread. The two projects of mine that had been banned have been struck again. On an unrelated note, is there a way to see what host a project is on from the editor?
Hi @Andromander we did have another host banned by Discord. Only one of the bots you’ve previously mentioned was on that host, and it’s now been re-homed, so things should be looking up. Let us know if you see further problems.
We had another banned host which we’ve emptied - all your bots should be finding new hosts and no longer be having trouble connecting.
The most likely cause is that there’s one or more bots that are violating some aspect of the Discord terms of service, and when they get banned Discord bans that IP address, which causes an entire host to be banned on Glitch’s end, effecting whatever bots are running on the host.
We haven’t been able to find a way to work with the Discord team to resolve these issues yet. Luckily they’re not all that common in general. That said this is really the only strategy open to us, and we’re sorry for the frustration.
Hello it’s been about 2 weeks that my bot works very well but I once again received this error, the name of my project is odium-bot
Error: Something took too long to do.
at timeout.client.setTimeout (/rbd/pnpm-volume/51b31f91-b1da-449a-b956-85c4e0ef9cf2/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/51b31f91-b1da-449a-b956-85c4e0ef9cf2/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)
Thank you for any help I hesitated to open another topic desolate for disarray ^^
Hey @zeis974 we don’t have any currently-banned hosts, so there’s nothing for us to do on that front. We’ve seen on occasion where Discord will ban an IP address but subsequently unban it without any apparent action, so maybe that’s what’s happened in this case?
If you’re still experiencing the problem, though, then I suggest you open a new topic - it seems likely to be specific to your bot and not more widespread.
Hi, I just started having this problem today with my bot, kakuhou-surgeon. It’s a private application, but I can send an invite link if you need to look at it.
Having the same issue. Started a couple days ago the bot went offline , The project is private so if you need the link I will privately send it.
Edit: Remixed the project to fix the issues. You guys should really talk to discord though about why they are blocking your ips.
Edit 2: Well, ok apparently it isn’t entirely fixed commands are duplicating
I remixed the project but forgot to regen my token all is fixed now (at least with the edit 2 issue)
We can confirm the problem is caused by Discord banning some IPs. We’re in the process of moving impacted projects on to new IPs, so your projects should begin to work again soon.
If you see this error in your own project and haven’t already let us know the project name - then let us know and we’ll get you back up and running shortly.
We don’t have any banned IPs at the moment - it looks like your project had the debugger running. I’ve disabled that - let me know if you still have a problem. Thanks.
Please be aware due to the free nature of this platform; people that don’t know how to code and abused Discord’s API and thus Discord has banned some Glitch IPs.
Hey @whatusernameisleft, @Callum is correct, your project was running on a host that was banned by Discord. I’ve moved it to a new host and it should work better now.
We did have a host being banned by Discord, and your project was on that host. I’ve moved all of those projects to a new host and you should be good to go! Sorry for the bother!
Hello, I’ve been having the same issue with my bot once again lol. I’ve tried refreshing my bot: zielo-rules multiple times but for some reason i’m still getting the same error. Were there multiple hosts banned by discord?
Hey @hmaltr, welcome to the Glitch forum! You bot was on a host that’s been banned by Discord. I’ve moved it to a new host, so things should be looking up!
Hello. My ryougi-shiki project seems to be having the same problem. Moving it, or anything that could help, would be greatly appreciated. It’s a private project so if an invite is required, I can provide that in private.
Hello, I am also experiencing the same issue.
Error: Something took too long to do.
at timeout.client.setTimeout (/rbd/pnpm-volume/4d176b40-8997-4f61-90a6-789d48e6e00f/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/4d176b40-8997-4f61-90a6-789d48e6e00f/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)
This is a common Discord API error. Something is not connecting right. You can view the Discord API status here. You can try to get a new Bot token to see if that speeds up the recovery process.
Hey, this has already happened to my project once and it has just started again. My project is private, so let me know if you can move my project so that I can give you access. Thanks!
Hey @JMGbaum, I don’t need access to your project to move it, just the project name. Since your project is private, no one aside from folks you explicitly invite and a few Glitch staff will see your code (in part so we can help with problems like this), so you can safely provide your project name here. However, you’re also welcome to send a private forum message to the @support_staff group or to me, or to send an email to [email protected] with your project details.
We don’t need the project’s “join” invite token to see your project; the project name is sufficient. You should avoid posting project invite tokens publicly for any project, private or not, because that gives anyone who follows them full access to your project and all of its data.
I feel so badly for just adding to the problem, but… here’s aboc-discord-radio
This bot is supposed to be a 24/7 Voice chat radio, so it’s imperative that this gets fixed quickly. As far as I know, this problem started maybe about 5 hours ago, and I’ve swapped out 3 tokens. Nothing works. If you guys can, could you work on creating a solution that we can do ourselves?
(node:274) UnhandledPromiseRejectionWarning: Error: Something took too long to do.
at timeout.client.setTimeout (/rbd/pnpm-volume/0c9e459d-0634-416d-9f1b-b719eadc83ac/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/0c9e459d-0634-416d-9f1b-b719eadc83ac/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)
(node:274) 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(). (rejection id: 16)
(node:274) [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.
1552997620229 Ping Received
Hello, I have the same problem with my test bot it was working well but after once I restarted, the same error comes and my project name is amazing-bot
I’ve moved all the projects on the (banned) host your project was on to a new host. Your bot should be able to connect to the Discord API now. SOrry for the bother!
Your and @Jojo_the_Joker’s bots were on a banned host. I’ve moved them to a new server and everything should start running properly again. Sorry for the bother!
We had an unusually large number of hosts banned by Discord today. I’ve moved all of the projects on those servers to new ones and these problems should be resolved now.
Hello There me and my friends bot is getting the error and we were wondering if it involved the slow api or if we were on a banned host. Could you please take a look, Thanks. d4rkythebot-main
Hello, my project bunny-bot-bunny-wc has run into the same problem.
By the way, is a more permanent solution to this problem planned? It sounds like quite a bother on your end, having to constantly monitor requests to move hosts in this thread.
Hi, I have a problem with my discord bot, it’s the same problem I’ve had before and they said it has to do with what discord banned the host.
Project name: habbosk-bot-discord
@owocean, This is not caused by a token being used too much. This is when discord Blocks a host from glitch because of so many requests. So then the projects that were on that host receive a connection error and have to be moved by a glitch staff member to a new host for it to work again.
Actually, I am pretty sure the reason is just because of multiple requests over and over which causes discord to automatically ban the ip that is making the requests. It has absolutely nothing to do with the bots that are on the projects.
Discord’s not particularly forthcoming about the specific reasons for a given ban, but among the reasons is that a bot’s token is suspended for some reason but the bot continues to make requests with the suspended token and eventually Discord auto-bans the originating IP address.
Since we don’t control what Discord bots created on Glitch are able to to (and in what ways they might break Discord’s rules and trigger a ban) we don’t have any control over when Discord bans a Glitch IP. That’s something Discord would have to address by changing how they handle banning, so if you’d like a permanent fix you would have to bring it up with them. Based on the fact that we don’t monitor response traffic from Discord to projects hosted on Glitch we don’t even have a way to know which bots are problematic in real time.
We’re thinking about ways we might be able to be more proactive about this, but for the moment this is as permanent a fix as we’re able to offer. Sorry for the inconvenience!
My main project (“stealthy”) and one of my other projects (“fade-”).
At first I attributed the problem to Discord API because of this: https://status.discordapp.com/incidents/05vzjpb7ph13.
However, it’s been fixed for a while and all my friends have their bots online. Even some on glitch.
Note: I don’t see any errors and my bot is still online so I think it’s running on one of my other projects.
Edit: I found the project and migrated all my files there temporarily. Hope this gets fixed soon as that project has all the people I know.
I’m not sure if you guys did anything but my project randomly started working. Thanks anyways.
My Discord Bots are all offline and I am getting an error
“(node:4078) UnhandledPromiseRejectionWarning: Error: Something took too long to do.”
I tried npm install, and enable-pnpm…
Your bot is on a banned host by discord, this will be resolved in the next few hours. It is not a problem with your project and there is nothing you can do about it, you will just have to wait!
Hey folks, we have a slew of banned hosts this morning, so this is going to take a while, but we’ll eventually get through them all. I’ll post back when we’re done, and thanks for your patience!
Everyone!
If your project does not have a website on it, and you are still having the problem, then remix the project, and copy over any .env variables, then you can delete the old project and that should fix it! You will have to invite any members that were on the project back, and add the project to any teams it was on if it was on any!
Hey folks, all the banned hosts (there were almost 50) have now been recycled and there shouldn’t be any more bots with this problem at this moment. Sorry for the inconvenience!
Remixing you project will not always be sufficient to resolve this issue, since Discord bans entire hosts, and a Remix may start on the same host as the source project, in which case the Remix won’t work right from the start.
Your bot could be logging in too many times. After 1,000 logins with the same token, Discord will change the token. In short: generate a new token and use that.
Hey @IamSsum we don’t have any currently banned hosts, although sometimes bans are temporary.
You can always check to see if your specific project is banned using curl -I https://discordapp.com/api/v7/gateway in your project’s console. If you see 200 OK on the first line your project’s host isn’t banned.
Hey there, I attempted curl -I https://discordapp.com/api/v7/gateway, and got back
HTTP/1.1 429 too many requests
I believe that means I need to migrate my project’s host, is there some way I can do that or do you need to do it from your end?
Hey folks we have a long list of banned hosts that we’re working our way through. We’ll let you know when we’ve recycled all the banned hosts, sorry for the bother!
((node:3217) UnhandledPromiseRejectionWarning: Error: Something took too long to do.
at timeout.client.setTimeout (/rbd/pnpm-volume/ba5c37af-02df-4742-91c4-c5ceb7c6f78a/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/ba5c37af-02df-4742-91c4-c5ceb7c6f78a/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)
(node:3217) 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(). (rejection id: 6)
(node:3217) [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.)
Discord Ban mega-thread! (Discord bot / Something took too long to do) thats the thread on glitchs support page , give them your project name in the comments and tell them to unban your host and wait till cori send a message and they will unban it without deleting any projects or changing Names
is there anything we can do from our end to prevent this going forward? I’m not sure what if anything I did that contributed to triggering this, do you have any idea what that could have been or what I can do about it?
@alvinmattallen no, not really, or at least nothing that’s likely to have a direct impact. I mean, you should definitely be watching your bot for signs it’s being warned of a ban so that you can address whatever issue there is before they ban an entire IP address, but that’s probably only relevant to a few bots overall. There isn’t a single project, or even a small group of projects that we can pin down as the culprit for triggering a ban, and this is an automated process that they’re unlikely to change on Discord’s side of things.
I have gotten this error,
(node:9969) UnhandledPromiseRejectionWarning: Error: Something took too long to do.
at timeout.client.setTimeout (/rbd/pnpm-volume/56331746-8c95-4640-9930-e44692348b7d/node_modules/.registry.npmjs.org/discord.js/11.5.0/node_modules/discord.js/src/client/ClientManager.js:40:57)
at Timeout.setTimeout [as _onTimeout] (/rbd/pnpm-volume/56331746-8c95-4640-9930-e44692348b7d/node_modules/.registry.npmjs.org/discord.js/11.5.0/node_modules/discord.js/src/client/Client.js:434: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)
(node:9969) 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(). (rejection id: 7)
(node:9969) [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.
I get the same error, it registers the “console logs” well, but when it loads the commands or logs it stops (it does not give any type of error and I have not changed anything since then) nor is it due to errors in the programming of the bot.)
(node:721) UnhandledPromiseRejectionWarning: Error: Something took too long to do.
9:07 PM
at timeout.client.setTimeout (/rbd/pnpm-volume/07e6f2e6-ec3f-483c-ae32-72d1bb1379cf/node_modules/.registry.npmjs.org/discord.js/11.5.0/node_modules/discord.js/src/client/ClientManager.js:40:57)
9:07 PM
at Timeout.setTimeout [as _onTimeout] (/rbd/pnpm-volume/07e6f2e6-ec3f-483c-ae32-72d1bb1379cf/node_modules/.registry.npmjs.org/discord.js/11.5.0/node_modules/discord.js/src/client/Client.js:434:7)
9:07 PM
at ontimeout (timers.js:498:11)
9:07 PM
at tryOnTimeout (timers.js:323:5)
9:07 PM
at Timer.listOnTimeout (timers.js:290:5)
9:07 PM
(node:721) 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(). (rejection id: 6)
9:07 PM
(node:721) [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.
Yeah, of course. It say “something took too long to do”. But after i check the error after it, there’s something error in the package make the project went down. Sorry, i didn’t check the error clearly.
This issue just happened for me.
My project is colossal-butterfly,
I tried resetting the project and updating my packages but nothing seems to work for me.
Hi, I’ve read the first few posts of this thread and learned that my projects are also all IP-banned with the same error messages (client took too long etc)
Is it possible to lift the ban? My project names are ‘smile’ and ‘laugh’. thank you
This is a thing about your “glitch” / “client” being in a banned host by discord state the name of your project on the tread and a support member / cori will fix it.
And also, i use on it some api request to the same project name so it will be completely different and I can’t do it on mobile (I usually did mistakes on mobile)
Genuinely at a loss rn. I have never had this issue with Glitch. I have used them for over a year and my host has never been banned or anything .-. At least not that I have seen … Considering that my bot is up 24/7 lmao … I don’t know whats going on
(node:9526) UnhandledPromiseRejectionWarning: Error: Something took too long to do.
1:43 PM
at timeout.client.setTimeout (/rbd/pnpm-volume/5417cfa4-bea3-43ec-90ae-634ba5a40d81/node_modules/.registry.npmjs.org/discord.js/11.4.2/node_modules/discord.js/src/client/ClientManager.js:40:57)
1:43 PM
at Timeout.setTimeout [as _onTimeout] (/rbd/pnpm-volume/5417cfa4-bea3-43ec-90ae-634ba5a40d81/node_modules/.registry.npmjs.org/discord.js/11.4.2/node_modules/discord.js/src/client/Client.js:433:7)
1:43 PM
at ontimeout (timers.js:498:11)
1:43 PM
at tryOnTimeout (timers.js:323:5)
1:43 PM
at Timer.listOnTimeout (timers.js:290:5)
1:43 PM
(node:9526) 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(). (rejection id: 6)
1:43 PM
(node:9526) [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.
Hey all - we see there’s an issue with Discord bots running off Glitch and we’re actively working to get them back online. I appreciate your patience and am sorry for the inconvenience!
The error message is Error: Something took too long to do.
Like, if you were to do console.log(error.message) you would get Error: Something took too long to do.
If you were to do console.log(error) you would get UnhandledPromiseRejectionWarning: Error: Something took too long to do.
node:9526) UnhandledPromiseRejectionWarning: Error: Something took too long to do.
1:43 PM
at timeout.client.setTimeout (/rbd/pnpm-volume/5417cfa4-bea3-43ec-90ae-634ba5a40d81/node_modules/.registry.npmjs.org/discord.js/11.4.2/node_modules/discord.js/src/client/ClientManager.js:40:57)
1:43 PM
at Timeout.setTimeout [as _onTimeout] (/rbd/pnpm-volume/5417cfa4-bea3-43ec-90ae-634ba5a40d81/node_modules/.registry.npmjs.org/discord.js/11.4.2/node_modules/discord.js/src/client/Client.js:433:7)
1:43 PM
at ontimeout (timers.js:498:11)
1:43 PM
at tryOnTimeout (timers.js:323:5)
1:43 PM
at Timer.listOnTimeout (timers.js:290:5)
1:43 PM
(node:9526) 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(). (rejection id: 6)
1:43 PM
(node:9526) [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.
I am having an issue, which I assume is related, ALL my bots are unresponsive, they can login, but are not sending the response to commands, it can receive the command input, but not send the output
My bot can’t even login at this point. I know that something is wrong, because there’s a banner on the forum saying that Discord bots are currently experiencing issues.
Not surprised if that’s the case. See One of the Glitch IPs is banned by Discord as Discord wants us to use a “real hosting provider” instead of Glitch, as voiced by Jake.
hi! so i know about the cloudflare and stuff but it usually gives me timeout, until a few seconds ago, it started saying somtehing took too long to do. do you mind helping me check out this project: lost-soul-new
Discord is currently having hosting issues GLOBALLY. There is only a very small percentage of people/bots who currently have access to the service. I am posting this so that you guys know that its probably not another ban wave, but instead simply discord itself being down. As such, bots are also down as it is the entire service, including the API that the bots connect to. Please be PATIENT and allow discord some time to figure out what is wrong. You can keep an eye on the progress through status.discordapp.com ^^
It cannot come online automatically here because library stopped connecting to discord and throwed error something took long to do. This means bot will not connect to discord api until whole project is restarted i.e after 12hrs (technical restrictions) or unless refresh is ran in console.
Hey @mmoomocowm, your project is not on a currently-banned host. Sometimes Discord bans can be temporary; are you still seeing this problem?
As a reminder to everyone, you can use curl -I https://discordapp.com/api/v7/gateway in your project’s console. If you see anything other than HTTP/1.1 200 OK then there’s some sort of problem; a 429 there means you’re banned.