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
1 Like
yes, glitch on mobile devices can get very glitchy, especially if their laggy.
Project name: gunes-bot helpp me
woof.js loaded!
1:39 PM
6 minutes ago
1561139008946 Ping Received
1:43 PM
1561139021062 Ping Received
1:43 PM
(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.
1:43 PM
1561139301123 Ping Received
1:48 PM
1561139308745 Ping Received
THERES THE ERROR XD
most of that is not an error…
(node:9526) UnhandledPromiseRejectionWarning: Error: Something took too long to do. that is the error
1 Like
Same error
Project name: lighting-bot
Except the top, the entire thing is an error message (except for the ping messages)
The rest of it explains where the error is occuring.
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!
7 Likes
Did your entire site just get ip banned? XD
1 Like
Project name: level-discord
pls help
Project name: emergency
If I try other projects, they don’t work either. I get the message “Something took too long to do” after 5 minutes.
1 Like
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.
1 Like
no the error is
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.
1 Like
That entire mess is all one error
1 Like
Projects name:
canvas-discord
tsundere-glitch
weez-discord
2 Likes
why are you replying that to me?
And why does the system just keep removing my quotes.
2 Likes
Project name:
foxhole-global
2 Likes