# Sage 10 Localhost:3000 Issue Windows

**URL:** https://discourse.roots.io/t/sage-10-localhost-3000-issue-windows/26557
**Category:** sage
**Tags:** bud, wsl, windows
**Created:** 2024-01-18T13:23:05Z
**Posts:** 5

## Post 1 by @mustterziu — 2024-01-18T13:23:06Z

Hey everyone,

I’m running into a bit of a snag with Sage 10 on localhost:3000 after trying to set it up on Windows using the WSL terminal.

Here’s the scoop: When I hit https://localhost:3000, I get hit with this error message: “Error occurred while trying to proxy: localhost:3000/”. Weirdly enough, I can access “domainname.local” without a hitch, but localhost:3000 is giving me a headache.

Anyone else faced this or got any clues on what might be causing this hiccup? Your insights would be a lifesaver!

This is the error I am getting in terminal too:

```
Network

 › Proxy ┄ http://pozhegubrothers.local/
 › Dev ┄ http://localhost:3000/
          ┄ http://192.168.85.191:3000/

 Press h to show help[server] › ✖ [HPM] Error occurred while proxying request localhost:3000/ to http://pozhegubrothers.local/ [ECONNREFUSED] (https://nodejs.org/api/errors.html#errors_common_system_errors)
[server] › ✖ [HPM] Error occurred while proxying request localhost:3000/favicon.ico to http://pozhegubrothers.local/ [ECONNREFUSED] (https://nodejs.org/api/errors.html#errors_common_system_errors)
```

Thanks a bunch! :raised_hands:

---

## Post 2 by @talss89 — 2024-01-18T21:47:26Z

Hello again @mustterziu,

This error points to Bud not being able to access your upstream `pozhegubrothers.local` HTTP service.

Could you share your `bud.config.js` file?

From inside WSL, you should be able to successfully `curl http://pozhegubrothers.local`. If not, you need to take a look at how hosts records / DNS / local machine is set up.

I have also heard rumours of WSL networking breaking over ipv6. As a last resort, it might be worth looking in to that. [Looks like a patch was released late last year for Win 11 only.](https://github.com/microsoft/WSL/issues/4518#issuecomment-1778054781)

---

## Post 3 by @decoycircuit — 2024-01-22T11:16:16Z

@mustterziu Also check to see if Windows Defender Firewall blocks WSL. That continues to be an issue with my WSL setup.

---

## Post 4 by @nadeaumarc — 2024-02-03T22:59:44Z

I’m having the same problem, did you end up finding a solution?

---

## Post 5 by @mustterziu — 2024-02-04T12:35:33Z

Unfortunately not,

I decided to go back in traditional Wordpress development without sage!

Thank you!

---

## Post 6 by @ben — 2024-02-04T17:03:15Z