Orion
Orion•5w ago

Deno 2.0 Bad resource ID after discord.js joinVoiceChannel

Hi, Seemingly out of nowhere, my deno 2.0 discord.js bot is throwing a crashing Bad resource ID error that seems uncatchable. The error seems to occur after joinVoiceChannel is executed and returned. It has previously been working with no issue for the last two days, and I've attempted to revert all changes, and the issue seems to persist. Any tips to resolve this would be great. Thank you in advance.
1 Reply
Orion
OrionOP•5w ago
error: Uncaught (in promise) BadResource: Bad resource ID
    at node:http:312:27
    at HttpsClientRequest._writeHeader (node:http:404:7)
    at HttpsClientRequest._flushHeaders (node:_http_outgoing:382:12)
    at TLSSocket.onConnect (node:http:450:16)
    at TLSSocket.emit (ext:deno_node/_events.mjs:405:35)
    at _afterConnect (node:net:159:12)
    at _afterConnectMultiple (node:net:219:3)
    at TCP.afterConnect (ext:deno_node/internal_binding/connection_wrap.ts:43:11)
    at ext:deno_node/internal_binding/tcp_wrap.ts:299:14
    at eventLoopTick (ext:core/01_core.js:177:7)
error: Uncaught (in promise) BadResource: Bad resource ID
    at node:http:312:27
    at HttpsClientRequest._writeHeader (node:http:404:7)
    at HttpsClientRequest._flushHeaders (node:_http_outgoing:382:12)
    at TLSSocket.onConnect (node:http:450:16)
    at TLSSocket.emit (ext:deno_node/_events.mjs:405:35)
    at _afterConnect (node:net:159:12)
    at _afterConnectMultiple (node:net:219:3)
    at TCP.afterConnect (ext:deno_node/internal_binding/connection_wrap.ts:43:11)
    at ext:deno_node/internal_binding/tcp_wrap.ts:299:14
    at eventLoopTick (ext:core/01_core.js:177:7)

Did you find this page helpful?