Jump to content

Discord Bot stopped working

Closed 2.2.5

Couple of weeks ago I started getting a Discord email saying that the bot was making too many calls, so they reset the token. I reset the toke 3 times, until the bot stop working completly 

 

(1/1) => 💛 [ Llaneros Solo Duo Trio#0718 ] is online!
TypeError: Cannot read properties of undefined (reading 'CHANNEL_ID')
    at Client.<anonymous> (/var/www/rcon-bot/src/events/establishConnection.js:141:70)
    at Client.emit (node:events:514:28)
    at WebSocketManager.triggerClientReady (/var/www/rcon-bot/node_modules/discord.js/src/client/websocket/WebSocketManager.js:388:17)
    at WebSocketManager.checkShardsReady (/var/www/rcon-bot/node_modules/discord.js/src/client/websocket/WebSocketManager.js:371:10)
    at WebSocketShard.<anonymous> (/var/www/rcon-bot/node_modules/discord.js/src/client/websocket/WebSocketManager.js:201:16)
    at WebSocketShard.emit (node:events:514:28)
    at WebSocketShard.checkReady (/var/www/rcon-bot/node_modules/discord.js/src/client/websocket/WebSocketShard.js:181:12)
    at WebSocketShard.gotGuild (/var/www/rcon-bot/node_modules/discord.js/src/client/websocket/WebSocketShard.js:155:10)
    at WebSocketManager.<anonymous> (/var/www/rcon-bot/node_modules/discord.js/src/client/websocket/WebSocketManager.js:241:15)
    at WebSocketManager.emit (/var/www/rcon-bot/node_modules/@vladfrangu/async_event_emitter/dist/index.js:282:31)

 

 

I'm running the bot with supervisord, and I have full control of the server 

 

I reseted the Bot token several time but I'm always getting the same error. I manually checked all the referecences to CHANEL_ID and they seem fine 

I also run some lint validation over the jsons and both are fine as well 

 

jsonlint config.json
config.json: ok

 

jsonlint SERVERS/llaneros.json
SERVERS/llaneros.json: ok

 

 

The code as a I mentioned in our previous chat is way to messy to do a proper debugging, so maybe you can guide me on how to solve it 

 

image.jpeg.c96bf031c08d7a41d5c5d4cbd2f3d01f.jpeg

 

Share this comment


Link to comment

The token getting reset normally is caused by a boot loop through wherever you’re hosting. The bot only attempts one connection every time you start the file. 

As for the channel ID thing your configs are likely not up to date and the code is trying to find something in your config that does not exist. 

Share this comment


Link to comment
1.1m

Downloads

Total number of downloads.

5.6k

Customers

Total customers served.

81.5k

Files Sold

Total number of files sold.

1.6m

Payments Processed

Total payments processed.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.