Sage 10 Localhost:3000 Issue Windows

sage
, ,
1

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:

2

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.

1 Like
3

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

4

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

5

Unfortunately not,

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

Thank you!