Getting error: "Error occurred while trying to proxy: localhost:3000/"

sage
21

Yes the site works fine on my local WP, I access it through http://127.0.0.1/my-site.

22

Then that’s the URL you need to be using instead of example.test…

1 Like
24

I don’t understand. I’m trying to get hot reload and automatic scss recompilation in reaction to changes through yarn dev.

URLs like http://127.0.0.1/my-site won’t achieve that. I just tried and sure enough it doesn’t react to changes…

25

Doesn’t Local use .local for their sites? You mentioned several times in here that you’re using Local. This is what you’re using for your setup, right?

If your Local site was named example.local, you would replace example.test with example.local in your Bud config.

Then when you are running yarn dev, you’d visit the dev server at http://localhost:3000.

26

I apologize. I didn’t know Local (https://localwp.com/) until today and I naively thought I was being asked whether my WP site is a regular one running on my local machine.

So actually I am not using Local.

27

The only thing that matters is that your proxy URL in the Bud config needs to be set to the URL that the Bud dev server will proxy. It should be set to the URL to your local development environment.

28

This is what I have in bud.config.js now:

app
    .setUrl('http://localhost:3000')
    .setProxyUrl('http://localhost/my-site')
    .watch(['resources/views', 'app']);

Yet when visiting http://localhost:3000/ I still see the same error:

Screenshot_1
Screenshot_1917×222 9.19 KB

http://localhost/my-site/ works fine. But no hot reload or anything of course.

So frustrating. Why is it not working?

29

XAMPP sounds frustrating… try using Local or another local development setup that assigns an actual hostname for sites (example.test, example.local, etc.)

30

I am now using Local WP and my site is locally accessible at http://my-site.local/.

Bud.config.js:

app
    .setUrl('http://localhost:3000')
    .setProxyUrl('http://my-site.local/')
    .watch(['resources/views', 'app']);

The issue remains the same - when visiting localhost:3000 I’m still getting:

Error occurred while trying to proxy: localhost:3000/

Has it even been tested on Windows? I mean, is there any Windows user here for whom it works?

31

This thread has been unlisted (invisible to all users except with a direct link).

Why???

32

Can you confirm whether or not you’re running Local from WSL? Earlier in this topic you had confirmed that you were already doing this, even though you were not actually using Local yet

33

Can’t we use Local installed from Windows using the regular .exe install file? Gosh you guys made this maximally difficult from every possible angle lol - never gone through a setup as difficult as this before. I find it kind of extreme.

Anyway before spending time going through that thread in an attempt to install Local from WSL, could you please confirm that this is necessary and that it is likely to result in localhost:3000 working?

34

What a ridiculous reply :joy: Shit on us, then expect us to spend more time to hand hold you as you learn how to develop on WSL for free

Give it a shot and learn how to troubleshoot and solve problems