-
Notifications
You must be signed in to change notification settings - Fork 847
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
Request to http://localhost:port #6162
Comments
it turns out there are no correlations between saving scripts with restarting the application. |
@chapov - I was able to fix this on my machine by removing WSL, doing a couple of reboots, then enabling it again. Not ideal but it's working again so 🤷 |
You don't need to remove WSL, it stops working every now and then after reboots, rebooting again fixes it. There must be some race condition at the start. |
Nope. Multiple reboots didn't fix this for me. Only that worked for me was removing WSL and adding it back. YMMV, obviously. |
disable fast boot. i had this exact issue, just disable fast startup from the control panel => power options |
I want to cross-post this comment here as well:
|
This issue has been automatically closed since it has not had any activity for the past year. If you're still experiencing this issue please re-file this as a new issue or feature request. Thank you! |
Win32NT 10.0.19041.0 Microsoft Windows NT 10.0.19041.0
wsl2
Ubuntu 18.04
Linux version 4.19.128-microsoft-standard (oe-user@oe-host) (gcc version 8.2.0 (GCC)) #1 SMP Tue Jun 23 12:58:10 UTC 2020
i run in wsl - docker and app nodejs.
all in good, port 5508 is listening, http://localhost:5508 is open:
I am saving the js script. nodemon restart my nodejs application.
port 5508 is down! http://localhost:5508 not connected.
netstat -aon
with cmd shows that the port is not listeningStarted yesterday
why? :)
The text was updated successfully, but these errors were encountered: