I am facing this same issue. While trying to figure out what’s wrong, I stumbled on this comment from @kellymears here Yarn dev return error - #8 by kellymears
I’m not sure what the issue is here, based on present info. I can say that users are successfully using bud with WSL2, and this is likely not a problem with bud but most likely a dev server configuration issue.
I’d think the next step is to make sure that your server is issuing a normal response (code 200). Others have reported similar issues and it has been the result of the server issuing a redirection or failure status. bud is not set up to follow proxy redirections, by default.
Under the network panel in devtools, what are the response headers being issued by the server? That’s the next thing I would check.
My bud.config.js
looks like this.
app
.setUrl('http://localhost:3000')
.setProxyUrl(new URL('https://bhanusingh.test'))
.watch(['resources/views', 'app']);
And https://bhanusingh.test
is accessible on my system setup with Local by Flywheel and I see no redirection status being 200 which would cause this issue as suspected in the above comment.
It clearly is the issue with how WordPress is setup locally.
Does anyone have idea on how can this be fixed?
If not what is the official recommended way proposed to setup WP, I am willing to switch the setup method if it runs my local dev setup.
Any help is appreciated.