Can't connect to local server started in WSL2 from Windows

[vinnyvinnyvinny]

• Your Windows build number: Version 10.0.19041.172

• What you're doing and what's happening:
  I'm unable to connect to a rails server started in my WSL2 instance of Ubuntu. The server starts as expected and is able to receive requests from ubuntu:

However when trying to access via windows, I get a ERR_CON_REFUSED error:

Issue doesn't seem to apply to port 80, for example, running "sudo nc -l 80" and then making a request from windows browser results in ubuntu receiving the request:

This issue also occurs when starting mailcatcher on port 1080, I'm unable to access mailcatcher from a windows browser event though it is accessible from within ubuntu:

Mailcatcher in Links:

Trying to connect in Chrome on Windows:

This was working up until yesterday evening, however has now stopped working. I also updated my windows install to KB4552455 earlier in the day yesterday, but am unsure whether this is related or not.

[crramirez]

Hello,

This is configured to only Listen in the local interface: tcp://127.0.0.1:3000. Configure it to listen in all interfaces, something like tcp://0.0.0.0:3000

Regards,
Carlos

[vinnyvinnyvinny]

Hi @crramirez .

Thanks for you reply, I tried this, but unfortunatey I'm getting the same result:

[crramirez]

Ok I am out of ideas

[therealkenc]

Other half is the IP address on the client. Once you are listening on 0.0.0.0 (which looks good in the screencap), use the IP address returned by hostname -I on the WSL side on the client. Likely same as #4851, which is open and actionable (contrast question, answered).

[vinnyvinnyvinny]

I somehow managed to get it working again. Steps I carried out that resolved the issue:

1. run the following command in Powershell
   Get-Service LxssManager | Restart-Service
2. Enabled the following Under "Turn Windows features on and off"

• Hyper-V
• Windows Hypervisor Platform

3. Restart

No idea what of the above caused the issue to go away, but it seems to be working now.

[uiosun]

I somehow managed to get it working again. Steps I carried out that resolved the issue:

1. run the following command in Powershell
   Get-Service LxssManager | Restart-Service
2. Enabled the following Under "Turn Windows features on and off"

• Hyper-V
• Windows Hypervisor Platform

1. Restart

No idea what of the above caused the issue to go away, but it seems to be working now.

I only run Get-Service LxssManager | Restart-Service, the error is resolve!

Thank you!

[czepesch]

I somehow managed to get it working again. Steps I carried out that resolved the issue:

1. run the following command in Powershell
   Get-Service LxssManager | Restart-Service
2. Enabled the following Under "Turn Windows features on and off"

• Hyper-V
• Windows Hypervisor Platform

1. Restart

No idea what of the above caused the issue to go away, but it seems to be working now.

I only run Get-Service LxssManager | Restart-Service, the error is resolve!

Thank you!

Windows updated yesterday, had similar issue.
In my case it was:

Enabled the following Under "Turn Windows features on and off"
Hyper-V
Windows Hypervisor Platform