Randy Fay

Haven't heard anything about this lately, so closing. Happy to continue the conversation here or elsewhere, and we can reopen this if it's reproducible.

I have heard of people having to do that, but if you can do that, you can also `ddev config global --xdebug-ide-location= 172.23.103.149`, but DDEV does try to figure out...

Opened * https://github.com/ddev/ddev/issues/4803

@raphaelcangucu I'd sure appreciate if you could give more context on your situation, preferably in #4803. You don't say where you're running your IDE, for example. If you're running it...

@bernhardberger I'd be very happy to do a screenshare session with you to try to sort this out. Thanks for showing host.docker.internal there; that's what DDEV uses to figure out...

Thanks @bernhardberger - Please create a time on https://cal.com/randyfay/30min - I'll be available mostly today.

Also @bernhardberger please take a look at * https://github.com/ddev/ddev/issues/4803 which would have been a better place for your comment.

@bernhardberger Please try the linux-amd64 binary in https://github.com/ddev/ddev/pull/4813#issuecomment-1508914827 Instructions on testing with it are https://ddev.readthedocs.io/en/latest/developers/building-contributing/#testing-a-pr Make sure you're using the right binary before continuing, use `ddev --version`. Then `export DDEV_DEBUG=true`...

@bernhardberger ping - really hoping you'll be able to try this out as explained above. It's important to figure out why it didn't work in your situation.

Thanks. Please prioritize it, as I prioritized a meeting with you to explore this. It should take less than 15 minutes. This is important for you and other WSL2 users.