Please describe the problem you are having in as much detail as possible:
events.js:182
throw er; // Unhandled 'error' event
^
Error: socket hang up
at createHangUpError (_http_client.js:343:15)
at TLSSocket.socketOnEnd (_http_client.js:435:23)
at emitNone (events.js:110:20)
at TLSSocket.emit (events.js:207:7)
at endReadableNT (_stream_readable.js:1045:12)
at _combinedTickCallback (internal/process/next_tick.js:102:11)
at process._tickCallback (internal/process/next_tick.js:161:9)
this error happen often in the last time when my Bot joins or leaves a server and it should not be an issue with my code/internet connection of my bots VPS.
Further details:
it shouldn't be, but it is.
so its something in my code?
I've also gotten a ton of this lately for no reason. No code has been changed. And it causes shards to become unresponsive.
its your network, sorry to disappoint.
oh okay well i will close this issue then but it s the same for me it worked so well for a long time and now i get it like idk every 7 hours maybe :c
I've been getting the same issue as well, I highly doubt it's my network...
Please re-open this issue @Dev-Yukine it's causing some serious problems.
same issue here, hasn’t been occurring until today after reinstalling d.js
@PassTheMayo @gavwin @Dev-Yukine @melmsie where do you host
OVH @devsnek
Melmsie uses OVH too
Wholesale
On Wed, Oct 4, 2017, 2:10 PM PassTheMayo notifications@github.com wrote:
OVH @devsnek https://github.com/devsnek
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/hydrabolt/discord.js/issues/1707#issuecomment-334242034,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATSBrPam8u5121dI9ckr2aRSHO3Nc6Geks5so8mvgaJpZM4Of346
.
Oh
Weird that two separate hosts are having the same issue with something that
I don't have an issue with in Eris. :Thonk:
On Wed, Oct 4, 2017, 4:06 PM PassTheMayo notifications@github.com wrote:
Oh
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/hydrabolt/discord.js/issues/1707#issuecomment-334273582,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATSBrDjfN1TYFyCzQifoTYZe6V4RrQtAks5so-UxgaJpZM4Of346
.
I haven't been having this issue until recently. I don't know what the issue is. I haven't touched iptables or blocked anything. Just to be safe, I am going to reinstall the VPS. /shrug
I have been having this issue a lot since the past 10-15 days
I host on vultr.
Account type: bot
Node: 8.5.2
Discord.js: master

since a lot of people here having this again. mine was an error in my guildCreate/guildLeave event code where i had wrong code using snekfetch. could you confirm your guildCreate/guildLeave event code isn't the issue?
I have disabled guildCreate and guildLeave so I can confirm that those events may not be the cause of the issue
Was any progress made with this issue? Unrelated to guildCreate and guildLeave, I've encountered these exceptions quite randomly on various occasions over the past year or so. This shouldn't be happening.
I also have this problem, also my app is freezing every ~2min.
Same problem here...
Same issue here tested on local machine and on openshift
Having this issue too. Happens about 5 seconds after I run a command.
I host on heroku. Been having this issue since I re-installed discord.js. I get this error whenever I send any message to a channel.
For those of you that are still experiencing this issue, is your code listening to the error event? The callback doesn't need to do anything in particular, besides execute without any further exceptions. I haven't tested its behaviour in all network conditions, but this seems to work.
mine is listening to it is it where the error com from ?
In my experience, listening to the event seems to prevent network errors like ECONNRESET from being thrown. Having said that, I haven't tested this extensively, so my perception might be mistaken.
Most helpful comment
I've been getting the same issue as well, I highly doubt it's my network...
Please re-open this issue @Dev-Yukine it's causing some serious problems.