Local sites running in WSL2 not accessible in browser

[amykapernick]

When starting a site/app locally on my computer in WSL 2 ( Ubuntu 20.04 LTS (GNU/Linux 4.19.84-microsoft-standard x86_64)), the browser won't connect to the local server.

This happens every time I start my computer (has been happening for a weekish now), but only when starting after the computer has been shut down. If I restart the computer, the local servers work fine

Please fill out the below information:

• Your Windows build number: (Type ver at a Windows Command Prompt)
  Microsoft Windows [Version 10.0.19041.264]

• What you're doing and what's happening:
  Running a local server for dev site. Happens regardless of site. eg.:

// Eleventy Site
$ npx @11ty/eleventy --serve

[Browsersync] Access URLs:
 --------------------------------------
       Local: http://localhost:8080
    External: http://172.25.237.22:8080
 --------------------------------------
          UI: http://localhost:3001
 UI External: http://localhost:3001
 --------------------------------------
[Browsersync] Serving files from: _site
[Browsersync] Watching files...


// Gatsby site
$ gatsby develop

success run queries - 5.329s - 9/9 1.69/s
 DONE  Compiled successfully in 2177ms                                                                               2:10:28 PM
⠀
 I  Netlify CMS is running at http://localhost:8000/admin/
⠀
You can now view climate-clever in the browser.
⠀
  http://localhost:8000/
⠀
View GraphiQL, an in-browser IDE, to explore your site's data and schema
⠀
  http://localhost:8000/___graphql
⠀
Note that the development build is not optimized.
To create a production build, use gatsby build
⠀
success Building development bundle - 3.192s

• What's wrong / what should be happening instead:
  I should be able to access the apps at the provided local URL (localhost:8080 for eleventy and localhost:8000 for Gatsby), but when loading the page in the web browser it says it's unable to connect (in both Firefox and Edge)

• Strace of the failing command, if applicable: (If some_command is failing, then run strace -o some_command.strace -f some_command some_args, and link the contents of some_command.strace in a gist here).
  
  

[onomatopellan]

Do they work with --host 0.0.0.0 as argument?

https://docs.microsoft.com/en-us/windows/wsl/compare-versions#additional-networking-considerations

[amykapernick]

Nope, on some scripts this throws an error that --host isn't a recognised parameter, and on the rest the site starts properly, but the URLs still aren't accessible

[onomatopellan]

This happens every time I start my computer (has been happening for a weekish now), but only when starting after the computer has been shut down. If I restart the computer, the local servers work fine

That hint sounds a lot like Fast Startup. I always disable it and had no localhost problems so far.
https://www.tenforums.com/tutorials/4189-turn-off-fast-startup-windows-10-a.html

[amykapernick]

Awesome, that's working now! At least I have a workaround for now (that doesn't require me restarting my computer as soon as I turn it on)

I wonder what the issue is that's making it not work when computer has fast booted

[gsalamin]

To avoid disabling Fast Startup, restarting WSL as pointed in #4636 worked for me (wsl --shutdown).

[matze19999]

same problem here on 19640.mn_release.200530-1731 on Surface Pro X. wsl --shutdown doesn't work

[krojew]

Ran into this issue today. Seems like 127.0.0.1 doesn't work at all.

[WozniakMac]

Ran into this issue today. Seems like 127.0.0.1 doesn't work at all.

@krojew
Try to add C:\Windows\System32\wsl.exe to Windows Defender Firewall