Xdebug 502 Bad Gateway errors

[abroes]

@ben.turner @clay I’m pinging you as you’ve both separately investigated a 502 error issue related to Xdebug (see below):

502 errors with xDebug

I tried this, but ran into quite a bit of issues since wp search-replace was failing in the CLI and all links are pointing to the “normal” url. Error: There has been a critical error on this website.Learn more about troubleshooting WordPress. There has been a critical error on this website. I’ll have to try this out with a different and perhaps less-complex install to see if I can debug it any further.

502 Request Error: prematurely closed connection while reading response header from upstream

Hi. I can install a ‘preferred’ site and it fires up fine. But i want to use xdebug so have tried to start a ‘custom’ install but it fails every time with a 502 Request Error. When i look at the Local Routers Logs there are numerous messages relating to the same issue… *14 upstream prematurely closed connection while reading response header from upstream, client: 192.168.95.1, server: austguide.local, request: “GET / HTTP/1.1”, upstream: “http://192.168.95.100:4004/”, host: “austguide.local” I…

I just wanted to reach out to tell you that this error only happens when you add/remove a breakpoint during a debug session. It’s a bug in Xdebug that was fixed in the 3.0.1 release -
https://xdebug.org/updates#x_3_0_1
https://bugs.xdebug.org/bug_view_page.php?bug_id=00001897

It would be great if a future version of Local could ship an updated Xdebug binary.

Thanks!

[batur]

I had the some problem and shared my solution here

[abroes]

@batur that works, but what ought to happen is that the developers fix this by simply shipping a new Xdebug binary. I’m not sure why they have been ignoring this thread.