You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When updating my windows \etc\hosts file the updates copy over into WSL2 just fine and appear in /etc/hosts. I should then be able to go to mynewhostname:3000 (or whatever port) and see the running application.
Actual behavior
When I got to localhost:3000 in a browser this works but when I got to mynewhostname:3000 it does not find the running application. I haven't been able to find any basic documentation on why this is. I have tried restarting all services from powershell and also the entire machine. The new host continues to be copied over fine but the browser does not recognize this. Feels like localhost is just a proxy for the IP address of WSL but then how can I proxy my new hostname to that IP address?
It's worth noting this only seems to be an issue with WSL2. Using WSL1 everything works as expected.
The text was updated successfully, but these errors were encountered:
Hi! We've identified this issue as a duplicate of another one that already exists in this repository. This specific instance is being closed in favor of tracking the concern over on the referenced thread.
Expected behavior
When updating my windows \etc\hosts file the updates copy over into WSL2 just fine and appear in /etc/hosts. I should then be able to go to mynewhostname:3000 (or whatever port) and see the running application.
Actual behavior
When I got to localhost:3000 in a browser this works but when I got to mynewhostname:3000 it does not find the running application. I haven't been able to find any basic documentation on why this is. I have tried restarting all services from powershell and also the entire machine. The new host continues to be copied over fine but the browser does not recognize this. Feels like localhost is just a proxy for the IP address of WSL but then how can I proxy my new hostname to that IP address?
It's worth noting this only seems to be an issue with WSL2. Using WSL1 everything works as expected.
The text was updated successfully, but these errors were encountered: