-
Notifications
You must be signed in to change notification settings - Fork 822
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
localhost:3000 / 127.0.0.1:3000 nodejs server unable to connect via windows browsers #8509
Comments
@Sandy-Garrido the |
Hmm, thanks, though That answer suggests to enter the wsl ip all the time, this changes, so does that mean I will have to change this every time ? |
@Sandy-Garrido is this what you're trying to connect?
|
Doh 🤦♂️ I see where you're going with that I think. I'll give that solution a try haha |
Hey, so I tried: However, it's still not giving me the desired result, just doesn't want to connect. Am I missing something from that thread? btw, yes, was the answer to your question I quoted |
Okay, whilst yes, what I wanted didn't work. With your comments etc, I've managed to at least create a logon script that will get the WSL IP and run the netsh command so that I don't need to keep changing it! thanks for you're help! |
Calc84 |
Version
Microsoft Windows [Version 10.0.22000.708]
WSL Version
Kernel Version
5.10.102.1
Distro Version
Ubunutu 20.04.4 LTS
Other Software
No response
Repro Steps
Expected Behavior
Actual Behavior
Unable to connect to localhost wsl nodejs server
I am however able to access it via the wsl ip 172.29.229.115:3000 but this IP changes every time I restart or restart WSL which isn't useful for me every time as the project I'm working on requires the host to be a particular domain which I set via HOSTS.
I don't recall this working in the past as it's the first time I've needed to have a specific domain set in my host file
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: