Discord JS : socket hang up

Kyoya · June 15, 2019, 6:58pm

(node:1592) UnhandledPromiseRejectionWarning: Error: socket hang up

How can I fix commands are not working my bot!

cori · June 15, 2019, 8:32pm

Hey @Kyoya, which project is having trouble? Can you give us more of the error for context?

Kyoya · June 16, 2019, 2:43pm

Hey @cori , can you renew my glitch IP ?

Kyoya · June 16, 2019, 2:44pm

Full ERROR:

at TLSSocket.emit (events.js:185:15)
at endReadableNT (_stream_readable.js:1106:12)
at process._tickCallback (internal/process/next_tick.js:178:19)
(node:177) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 28)
(node:177) UnhandledPromiseRejectionWarning: Error: socket hang up
at TLSSocket.onConnectEnd (_tls_wrap.js:1083:19)
at Object.onceWrapper (events.js:272:13)
at TLSSocket.emit (events.js:185:15)
at endReadableNT (_stream_readable.js:1106:12)
at process._tickCallback (internal/process/next_tick.js:178:19)
(node:177) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 29)
(node:177) UnhandledPromiseRejectionWarning: Error: socket hang up
at TLSSocket.onConnectEnd (_tls_wrap.js:1083:19)
at Object.onceWrapper (events.js:272:13)
at TLSSocket.emit (events.js:185:15)
at endReadableNT (_stream_readable.js:1106:12)
at process._tickCallback (internal/process/next_tick.js:178:19)
(node:177) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 30)
(node:177) UnhandledPromiseRejectionWarning: Error: socket hang up
at TLSSocket.onConnectEnd (_tls_wrap.js:1083:19)
at Object.onceWrapper (events.js:272:13)
at TLSSocket.emit (events.js:185:15)
at endReadableNT (_stream_readable.js:1106:12)
at process._tickCallback (internal/process/next_tick.js:178:19)
(node:177) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 31)
(node:177) UnhandledPromiseRejectionWarning: Error: socket hang up
at TLSSocket.onConnectEnd (_tls_wrap.js:1083:19)
at Object.onceWrapper (events.js:272:13)
at TLSSocket.emit (events.js:185:15)
at endReadableNT (_stream_readable.js:1106:12)
at process._tickCallback (internal/process/next_tick.js:178:19)
(node:177) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 32)
(node:177) UnhandledPromiseRejectionWarning: Error: socket hang up
at TLSSocket.onConnectEnd (_tls_wrap.js:1083:19)
at Object.onceWrapper (events.js:272:13)
at TLSSocket.emit (events.js:185:15)
at endReadableNT (_stream_readable.js:1106:12)
at process._tickCallback (internal/process/next_tick.js:178:19)
(node:177) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 33)
(node:177) UnhandledPromiseRejectionWarning: Error: socket hang up
at TLSSocket.onConnectEnd (_tls_wrap.js:1083:19)
at Object.onceWrapper (events.js:272:13)
at TLSSocket.emit (events.js:185:15)
at endReadableNT (_stream_readable.js:1106:12)
at process._tickCallback (internal/process/next_tick.js:178:19)
(node:177) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 34)
(node:177) UnhandledPromiseRejectionWarning: Error: socket hang up
at TLSSocket.onConnectEnd (_tls_wrap.js:1083:19)
at Object.onceWrapper (events.js:272:13)
at TLSSocket.emit (events.js:185:15)
at endReadableNT (_stream_readable.js:1106:12)
at process._tickCallback (internal/process/next_tick.js:178:19)
(node:177) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 35)
(node:177) UnhandledPromiseRejectionWarning: Error: socket hang up
at TLSSocket.onConnectEnd (_tls_wrap.js:1083:19)
at Object.onceWrapper (events.js:272:13)
at TLSSocket.emit (events.js:185:15)
at endReadableNT (_stream_readable.js:1106:12)
at process._tickCallback (internal/process/next_tick.js:178:19)
(node:177) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 36)
(node:177) UnhandledPromiseRejectionWarning: Error: socket hang up
at createHangUpError (_http_client.js:336:15)
at TLSSocket.socketOnEnd (_http_client.js:429:23)
at TLSSocket.emit (events.js:185:15)
at endReadableNT (_stream_readable.js:1106:12)
at process._tickCallback (internal/process/next_tick.js:178:19)
(node:177) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 37)
(node:177) UnhandledPromiseRejectionWarning: Error: socket hang up
at TLSSocket.onConnectEnd (_tls_wrap.js:1083:19)
at Object.onceWrapper (events.js:272:13)
at TLSSocket.emit (events.js:185:15)
at endReadableNT (_stream_readable.js:1106:12)
at process._tickCallback (internal/process/next_tick.js:178:19)
(node:177) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 38)
(node:177) UnhandledPromiseRejectionWarning: Error: socket hang up
at TLSSocket.onConnectEnd (_tls_wrap.js:1083:19)
at Object.onceWrapper (events.js:272:13)
at TLSSocket.emit (events.js:185:15)
at endReadableNT (_stream_readable.js:1106:12)
at process._tickCallback (internal/process/next_tick.js:178:19)
(node:177) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 39)
1560696193544 Upps, ping yedik ama yine de Shiina Aktif!
(node:177) DeprecationWarning: Collection#find: pass a function instead
(node:177) DeprecationWarning: Collection#find: pass a function instead
(node:177) DeprecationWarning: Collection#find: pass a function instead
(node:177) DeprecationWarning: Collection#find: pass a function instead
(node:177) UnhandledPromiseRejectionWarning: Error: socket hang up
at TLSSocket.onConnectEnd (_tls_wrap.js:1083:19)
at Object.onceWrapper (events.js:272:13)
at TLSSocket.emit (events.js:185:15)
at endReadableNT (_stream_readable.js:1106:12)
at process._tickCallback (internal/process/next_tick.js:178:19)
(node:177) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 40)
(node:177) UnhandledPromiseRejectionWarning: Error: socket hang up
at TLSSocket.onConnectEnd (_tls_wrap.js:1083:19)
at Object.onceWrapper (events.js:272:13)
at TLSSocket.emit (events.js:185:15)
at endReadableNT (_stream_readable.js:1106:12)
at process._tickCallback (internal/process/next_tick.js:178:19)
(node:177) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 41)
(node:177) UnhandledPromiseRejectionWarning: Error: socket hang up
at TLSSocket.onConnectEnd (_tls_wrap.js:1083:19)
at Object.onceWrapper (events.js:272:13)
at TLSSocket.emit (events.js:185:15)
at endReadableNT (_stream_readable.js:1106:12)
at process._tickCallback (internal/process/next_tick.js:178:19)
(node:177) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 42)
(node:177) UnhandledPromiseRejectionWarning: Error: socket hang up
at TLSSocket.onConnectEnd (_tls_wrap.js:1083:19)
at Object.onceWrapper (events.js:272:13)
at TLSSocket.emit (events.js:185:15)
at endReadableNT (_stream_readable.js:1106:12)
at process._tickCallback (internal/process/next_tick.js:178:19)
(node:177) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 43)
(node:177) UnhandledPromiseRejectionWarning: Error: socket hang up
at TLSSocket.onConnectEnd (_tls_wrap.js:1083:19)
at Object.onceWrapper (events.js:272:13)
at TLSSocket.emit (events.js:185:15)
at endReadableNT (_stream_readable.js:1106:12)
at process._tickCallback (internal/process/next_tick.js:178:19)
(node:177) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 44)
(node:177) UnhandledPromiseRejectionWarning: Error: socket hang up
at TLSSocket.onConnectEnd (_tls_wrap.js:1083:19)
at Object.onceWrapper (events.js:272:13)
at TLSSocket.emit (events.js:185:15)
at endReadableNT (_stream_readable.js:1106:12)
at process._tickCallback (internal/process/next_tick.js:178:19)
(node:177) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 45)
(node:177) UnhandledPromiseRejectionWarning: Error: socket hang up
at TLSSocket.onConnectEnd (_tls_wrap.js:1083:19)
at Object.onceWrapper (events.js:272:13)
at TLSSocket.emit (events.js:185:15)
at endReadableNT (_stream_readable.js:1106:12)
at process._tickCallback (internal/process/next_tick.js:178:19)
(node:177) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 46)
(node:177) UnhandledPromiseRejectionWarning: Error: socket hang up
at TLSSocket.onConnectEnd (_tls_wrap.js:1083:19)
at Object.onceWrapper (events.js:272:13)
at TLSSocket.emit (events.js:185:15)
at endReadableNT (_stream_readable.js:1106:12)
at process._tickCallback (internal/process/next_tick.js:178:19)
(node:177) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 47)
(node:177) DeprecationWarning: Collection#find: pass a function instead
(node:177) DeprecationWarning: Collection#find: pass a function instead
(node:177) DeprecationWarning: Collection#find: pass a function instead
(node:177) DeprecationWarning: Collection#find: pass a function instead
(node:177) UnhandledPromiseRejectionWarning: Error: socket hang up
at createHangUpError (_http_client.js:336:15)
at TLSSocket.socketOnEnd (_http_client.js:429:23)
at TLSSocket.emit (events.js:185:15)
at endReadableNT (_stream_readable.js:1106:12)
at process._tickCallback (internal/process/next_tick.js:178:19)
(node:177) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 48)

MOD EDIT: formatting

cori · June 17, 2019, 2:12pm

Hey @Kyoya, what project was this for?

Kyoya · June 23, 2019, 1:26pm

Hey, @cori for shiina-trbot project.

cori · June 23, 2019, 2:51pm

Hey @Kyoya I’m only seeing socket hangup error very intermittently right now; I think the first step is to figure out which command is causing that problem so you can determine what socket request is failing.

I’m also seeing a lot of other errors like Cannot read property 'delete' of null or Cannot read property 'id' of null, coming from a couple of different places in your code. Those seem to indicate that you’re assuming that the incoming messages have a guild property and some of them do not - checking to see if the msg has a guild before trying to use the guild’s id will help get rid of those errors, which may make troubleshooting the socket hangup errors easier.

Kyoya · June 25, 2019, 2:07pm

@cori, i can’t fix this , same error! Idk how to fix.

cori · June 25, 2019, 4:39pm

Hey @Kyoya I’m still seeing a bunch of unrelated error and warnings that aren’t related to the socket hung up issue and (at least is what I was able to see) none of the socket hung up issues. I don’t know which errors you’re asking about fixing, but if you’re talking about the socket error, you might try remixing your bot and adding it to a single channel in a guild you control and then testing your commands one by one. That could keep the noise in the logs down to a minimum while you try to isolate what code is causing the error.

Kyoya · June 26, 2019, 4:16pm

Hello my problem is that my discord bot cannot login I have 1 error(Error: socket hang up)
Project: shiina-trbot

cori · June 26, 2019, 5:16pm

Hey @Kyoya since this is the same problem you asked about in Discord JS : socket hang up I’m merging this topic with that one - creating a new topic probably isn’t going to help fix your problem.

I’ve provided a few suggestions there, but I don’t see that you’ve tried any of them. The first thing you need to do is to figure out what part of your bot’s code is causing the socket hang up error.