Opening Handshake has timed out (no CF ban)

I mean seriously, this is the second time I get this, both times since updating to the most recent version 14.15.x from before I think 14.14.x and it happened on different apps while both of them were running on the same server on the same network and the other one didn't experience any problems. Of course it now happened on the app that doesn't have the "warn" and "error" eventlisteners registered on Client,... also it only happened those two times,.. within like 2 weeks or since when the last update was released. Anyway, this is the stack trace:
1|kokomi | 05-30 08:00:43 +02:00: Error: Opening handshake has timed out
1|kokomi | 05-30 08:00:43 +02:00: at ClientRequest.<anonymous> (/home/pi4/kokomi/node_modules/ws/lib/websocket.js:872:7)
1|kokomi | 05-30 08:00:43 +02:00: at ClientRequest.emit (node:events:519:28)
1|kokomi | 05-30 08:00:43 +02:00: at TLSSocket.emitRequestTimeout (node:_http_client:845:9)
1|kokomi | 05-30 08:00:43 +02:00: at Object.onceWrapper (node:events:633:28)
1|kokomi | 05-30 08:00:43 +02:00: at TLSSocket.emit (node:events:519:28)
1|kokomi | 05-30 08:00:43 +02:00: at Socket._onTimeout (node:net:589:8)
1|kokomi | 05-30 08:00:43 +02:00: at listOnTimeout (node:internal/timers:573:17)
1|kokomi | 05-30 08:00:43 +02:00: at process.processTimers (node:internal/timers:514:7)
1|kokomi | 05-30 08:00:43 +02:00: Error: Opening handshake has timed out
1|kokomi | 05-30 08:00:43 +02:00: at ClientRequest.<anonymous> (/home/pi4/kokomi/node_modules/ws/lib/websocket.js:872:7)
1|kokomi | 05-30 08:00:43 +02:00: at ClientRequest.emit (node:events:519:28)
1|kokomi | 05-30 08:00:43 +02:00: at TLSSocket.emitRequestTimeout (node:_http_client:845:9)
1|kokomi | 05-30 08:00:43 +02:00: at Object.onceWrapper (node:events:633:28)
1|kokomi | 05-30 08:00:43 +02:00: at TLSSocket.emit (node:events:519:28)
1|kokomi | 05-30 08:00:43 +02:00: at Socket._onTimeout (node:net:589:8)
1|kokomi | 05-30 08:00:43 +02:00: at listOnTimeout (node:internal/timers:573:17)
1|kokomi | 05-30 08:00:43 +02:00: at process.processTimers (node:internal/timers:514:7)
nothing more to go on except that I can hardly think of it being a cf ban, rate limits or even a network error... my other app has 2 more ws connections (to twitch and SE) and even that one didn't show any hickups at that time.
1 Reply
d.js toolkit
d.js toolkit6mo ago
- What's your exact discord.js npm list discord.js and node node -v version? - Not a discord.js issue? Check out #other-js-ts. - Consider reading #how-to-get-help to improve your question! - Explain what exactly your issue is. - Post the full error stack trace, not just the top part! - Show your code! - Issue solved? Press the button!
Want results from more Discord servers?
Add your server