8 replies

Sharding times out after several other shards launched successfully

Good afternoon everybody,
I'm currently stuck with a sharding problem that only occurs on my external VPS. At the moment I can't really differenciate if it is because of said VPS or if it is problem with discord.js, that's why I'm here as my last option of help.
When running the bot on my local computer everything works just fine. Every shard launches correctly and is ready to use afterwards. Now I tried to migrate everything to a VPS to try to put the bot into operation. The problem now is that after several shards launched successfully, the next one times out and I get the following error:

Error [ShardingReadyTimeout]: Shard 45's Client took too long to become ready.
    at Timeout.onTimeout (/home/container/node_modules/discord.js/src/sharding/Shard.js:183:16)
    at listOnTimeout (node:internal/timers:559:17)
    at processTimers (node:internal/timers:502:7) {
  code: 'ShardingReadyTimeout'
}

Error [ShardingReadyTimeout]: Shard 45's Client took too long to become ready.
    at Timeout.onTimeout (/home/container/node_modules/discord.js/src/sharding/Shard.js:183:16)
    at listOnTimeout (node:internal/timers:559:17)
    at processTimers (node:internal/timers:502:7) {
  code: 'ShardingReadyTimeout'
}

My sharding manager looks like this:

const { ShardingManager } = require('discord.js');

require('dotenv').config();

const manager = new ShardingManager('./bot.js', { token: process.env.TOKEN, respawn: true });

manager.on('shardCreate', shard => console.log(`Shard ${shard.id} launching...`));

manager.spawn({ delay: 1500, timeout: 30000 }).catch(error => console.log(error));

const { ShardingManager } = require('discord.js');

require('dotenv').config();

const manager = new ShardingManager('./bot.js', { token: process.env.TOKEN, respawn: true });

manager.on('shardCreate', shard => console.log(`Shard ${shard.id} launching...`));

manager.spawn({ delay: 1500, timeout: 30000 }).catch(error => console.log(error));

I hope someone finds the solution to this, thanks in advance!

d-Iaa

discord.js - Imagine an app•3y ago•

8 replies

Nils

Sharding times out after several other shards launched successfully

Error [ShardingReadyTimeout]: Shard 45's Client took too long to become ready.
    at Timeout.onTimeout (/home/container/node_modules/discord.js/src/sharding/Shard.js:183:16)
    at listOnTimeout (node:internal/timers:559:17)
    at processTimers (node:internal/timers:502:7) {
  code: 'ShardingReadyTimeout'
}

Error [ShardingReadyTimeout]: Shard 45's Client took too long to become ready.
    at Timeout.onTimeout (/home/container/node_modules/discord.js/src/sharding/Shard.js:183:16)
    at listOnTimeout (node:internal/timers:559:17)
    at processTimers (node:internal/timers:502:7) {
  code: 'ShardingReadyTimeout'
}

My sharding manager looks like this:

const { ShardingManager } = require('discord.js');

require('dotenv').config();

const manager = new ShardingManager('./bot.js', { token: process.env.TOKEN, respawn: true });

manager.on('shardCreate', shard => console.log(`Shard ${shard.id} launching...`));

manager.spawn({ delay: 1500, timeout: 30000 }).catch(error => console.log(error));

const { ShardingManager } = require('discord.js');

require('dotenv').config();

const manager = new ShardingManager('./bot.js', { token: process.env.TOKEN, respawn: true });

manager.on('shardCreate', shard => console.log(`Shard ${shard.id} launching...`));

manager.spawn({ delay: 1500, timeout: 30000 }).catch(error => console.log(error));

I hope someone finds the solution to this, thanks in advance!

Sharding times out after several other shards launched successfully

Similar Threads

Sharding times out after several other shards launched successfully

Similar Threads

Similar Threads

Similar Threads