Just curious why is it port 1338 did you change it because default is 1337.
Also if you are using WSL then I’m going to guess that there lies the issue. It doesn’t proxy the ports it was a known issue in WSL earlier days (atleast when I used it few years ago).
opened 06:15AM - 30 May 20 UTC
closed 02:28AM - 04 Aug 20 UTC
bug
fixedininsiderbuilds
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](https://gist.github.com/) here).
So I would say if you are using WSL, I think you need to use the 0.0.0.0 as the IP in the project, not localhost. This is about a year old btw
Fixing WSL2 localhost access issue - abdus.dev but as I said a known issue in WSL where ports and localhost is been a problem.
1 Like