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

Error: read ECONNRESET when using Ubuntu 20.04 on WSL2 #8949

Open
kasmith11 opened this issue Oct 24, 2022 · 7 comments
Open

Error: read ECONNRESET when using Ubuntu 20.04 on WSL2 #8949

kasmith11 opened this issue Oct 24, 2022 · 7 comments

Comments

@kasmith11
Copy link

When following the Getting Started guide, I am getting CRASH: Error: read ECONNRESET when running node pokemon-showdown start --no-security using Ubuntu 20.04 on WSL2

`RESTORE CHATROOM: lobby
RESTORE CHATROOM: staff

CRASH: Error: read ECONNRESET
at Pipe.onStreamRead (node:internal/stream_base_commons:217:20)
at Pipe.callbackTrampoline (node:internal/async_hooks:130:17)

CRASH: Error: read ECONNRESET
at Pipe.onStreamRead (node:internal/stream_base_commons:217:20)
at Pipe.callbackTrampoline (node:internal/async_hooks:130:17)

CRASH: Error: read ECONNRESET
at Pipe.onStreamRead (node:internal/stream_base_commons:217:20)
at Pipe.callbackTrampoline (node:internal/async_hooks:130:17)

Worker 1 now listening on 0.0.0.0:8000
Test your server at http://localhost:8000

@TecToast
Copy link

TecToast commented Nov 3, 2022

Don't know why this is happening, but I had the same problem and I figured out that the reason is the Repl Server, which can be toggled off in the config (exports.repl = true is the default) if you don't need it

@singiamtel
Copy link
Contributor

I think this is Artemis crashing

@baskuit
Copy link

baskuit commented Dec 1, 2022

Similar error on Kubuntu 22.04. Have not been able to use showdown on any of my linux distros in months.

@baskuit
Copy link

baskuit commented Dec 6, 2022

I was able to fix this on my Kubuntu 22.04 by rolling back to the last version of NodeJS 14 @kasmith11

@kasmith11
Copy link
Author

@baskuit do you have the specific NodeJS version number?

@baskuit
Copy link

baskuit commented Dec 7, 2022

node-v14.21.1 @kasmith11

@JoshElias
Copy link

Running into this issue as well in Arch Linux. using v14.21.1 did resolve the issue. Will reply if I find what is causing this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants