[Bug]: Xdebug with browser extension causes 502 Bad Gateway

[OlinB]

Platform

Windows

Operating system version

Windows 11 Pro 23H2

System architecture

Intel (x86)

Herd Version

1.13.0

PHP Version

No response

Bug description

When trying to use xdebug with the browser extension, activating the extension causes a 502 Bad Gateway.

Steps to reproduce

• add xdebug config to php.ini according to the documentation
• restart herd services
• load website without the extension enabled -> works
• load with extension enabled -> 502 Bad Gateway

Relevant log output

> No logs found.

[mpociot]

Do you get any errors in your PHP / Nginx log files?

[OlinB]

No php logs, but in nginx:
2025/01/22 15:02:58 [error] 13344#29948: *8 connect() failed (10061: No connection could be made because the target machine actively refused it) while connecting to upstream, client: 127.0.0.1, server: smala.test, request: "GET /backend HTTP/2.0", upstream: "fastcgi://127.0.0.1:9183", host: "smala.test", referrer: "https://smala.test/backend/backend/auth/signin"

[andrewpros]

Anyone fixed this?

I have the same issue, was trying this #731

but the Pro debug.conf file is overwritten each time Herd restart

[mpociot]

Which changes do you need to make to the debug.conf?

[andrewpros]

Changing the ports as explained by #731 (comment)

As a workaround i copied Pro folder to Free folder and changed the include of *.conf in main nginx.conf file to Free folder which is not overwritten so it works, but wonder if there is better way to do this.