Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot read property 'url' of null. discord.js/src/client/websocket/WebSocketShard.js:268 #5590

Closed
Pliexe opened this issue May 6, 2021 · 6 comments · Fixed by #6018
Closed
Assignees

Comments

@Pliexe
Copy link

Pliexe commented May 6, 2021

Casually am randomly getting this error which am guessing is executed when the shard opens each time.

this.debug(`[CONNECTED] ${this.connection.url} in ${Date.now() - this.connectedAt}ms`);

Screenshot_20

@nab138
Copy link

nab138 commented May 21, 2021

I get the same error and it happens a random amount of time after starting the bot

@meister03
Copy link
Contributor

meister03 commented May 25, 2021

It can happen on a instable connection and the error is known since 2 Months

@Muh9049
Copy link
Contributor

Muh9049 commented Jun 11, 2021

By any chance will this be fixed before v13 release? Just had 1 shard crash and restart last night because of it. Is there any way to error handle it manually ourselves for now?

@MagesticChicen
Copy link

I agree, this needs to be fixed quite urgently. My client seems to run into this error frequently and with no real means to fix it alot of us are just stranded waiting months for anything to change. Preventing an instable connection is easier said than done

@kyranet
Copy link
Member

kyranet commented Jun 13, 2021

As announced, discord.js v13 (which includes a fix for this) is releasing by the mid-end of this month. If a fix is so urgent, feel free to use the @dev tag from npm to prepare your bots for v13 and check #djs-at-dev in the official Discord server for any help.

@Muh9049
Copy link
Contributor

Muh9049 commented Jun 13, 2021

As announced, discord.js v13 (which includes a fix for this) is releasing by the mid-end of this month. If a fix is so urgent, feel free to use the @dev tag from npm to prepare your bots for v13 and check #djs-at-dev in the official Discord server for any help.

Wait, so does the master branch already have a fix for this, or are you saying v13 will have a fix for this whenever it's released? Because I'm using the master branch right now, and that error still occurred. I'm assuming it's because I'm using an older commit that I installed with npm i discordjs/discord.js before. I will try installing with npm i discord.js@dev later if a newer commit indeed fixes this issue.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 31, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants