Unable to get PHPStorm to connect to xdebug running in WSL 2 Follow

I know that it may sound like overkill but have you tried to completely disable Windows Firewall on _all_ profiles just to totally isolate any possible firewall intervention?

I asked  the same question on stack overflow and was able to fix it via the firewall settings (https://stackoverflow.com/a/63420260/1397894):

• In Windows Control Panel > Windows Firewall > Allow a program or feature through Windows Firewall you can see a list of software that is allowed to communicate through private and public networks.

For some weird reason though I had quite a few phpstorm entries there, each one probably an older Jetbrains Toolbox installation (I guess they don't get cleaned up properly?). I fear I will have to do this every time there's a new PhpStorm coming out :/

Thanks for sharing the link to the SO question, Windows firewall could be tricky sometimes.

As for the different PhpStorm entries, this is a somewhat normal scenario as each version has a different installation path.

I had a similar issue, but for me the solution was very different, but maybe this will help someone searching for a solution like me (for hours).
My problem was that absolutely nothing was happening after I configured xdebug. It ownly showed up in phpinfo, but not even logs were generated. For my solution, also Docker Desktop plays a role:

• I Have xdebug 3.x installed
• I also have Docker Desktop for Windows running
• Inside Docker for Desktop, I enabled "WSL2 Integration" for the WSL2 distribution my web server runs in.
• The magic config line for Xdebug for me was:
  xdebug.client_host=host.docker.internal
  Because the docker integration will leave this host entry in the WSL2 which also works without docker even running there!
• Boom, it worked. All other attempts failed, like copying the IP over and pasting it into the ini file and restarting the server.

I know this was a completely different setup, but if anyone else is as desperate as I was, this may hopefully help :-) 

Thanks for sharing what worked Nina. 

Does the debugging work even when the internet is turned off? And also how does it work when VPN is turned on?

Hi Nikhil,

sad thing is, this was just a one-trick-pony and...

... and after it didn't work a second time, it now works again, but the funny thing is that I had to set BOTH remote_host and client_host to host.docker.internal and BOTH remote_port and client_port to 9000 to get it working!
That's somewhat confusing, because I always thought those had to be different.

@Nina

...but the funny thing is that I had to set BOTH remote_host and client_host to host.docker.internal and BOTH remote_port and client_port to 9000 to get it working!
That's somewhat confusing, because I always thought those had to be different.

But they ARE the same thing.

remote_xxx is used by Xdebug v2 while Xdebug v3 uses client_xxx param name. BTW: v2-only param does nothing in v3.

Xdebug: Upgrading from Xdebug 2 to 3

Ah good to know! That's often also my problem: instead of actually reading more into the documentation, I just want to "get it running, NOW" and go through all the stackoverflow articles where you often find "mixed" configurations. From people who also are in my situation and just want to get it running ASAP. Also looking at the XDEBUG info in phpinfo, there was "_client" with port 9003 and "_remote" with port 9000 and if you don't really get deep into the topic, you might think something like (and yes, I admit this, fully ashamed) "one is for the one side, one is for the other side" or "one is if the debugging IDE is on the same machine, the other one is if the IDE is on an external (remote) machine". So you find all kinds of explanations why there should be two configurations for an IP and a port.

...finally many thanks for pointing this out! :-) 

Had came across the deprecation of the property earlier. The names are certainly confusing Nina. Thanks for the sharing the link here Andriy Bazanov. 

Had been using the settings as discussed here in this thread. However, when VPN is turned on, or, internet is disconnected the debugging no longer works. Hopefully using xdebug.client_host=host.docker.internal supports debugging in all the above scenarios.

Despite the popularity and wide adoption of WSL2, strangely, haven't come across a detailed article by @Jetbrains on how to set up debugging using WSL2.

Did any of you come across an article by PHPStorm that details the process of setting up debugging with WSL2? 

Guys Im having the same problem. I am very new to phpstorm and I am battling how to setup xdebug.

I have spent whole day - more than 12 hours trying to figure out what is what.

• I have set my WSL to use static IP
• I have enabled WSL distro integration in docker desktop
• I have set `remote_host`
• I have also set `remote_autostart` and `remote_connect_back`
• Xdebug module is loaded that i checked
• I also enabled logging
• I also installed the Chrome extension
• I checked phpstorm listening on port 9000 ok

This is my `xdebug.ini`:

zend_extension=xdebug.so
xdebug.remote_autostart=1
xdebug.remote_enable=1
xdebug.default_enable=1
xdebug.remote_connect_back=1
xdebug.remote_host=host.docker.internal
xdebug.remote_log=/tmp/xdebug.log

It should run on port 9000.
I can ping the WSL machine from within the container:

sh-5.0# ping -c 3 172.24.17.219
PING 172.24.17.219 (172.24.17.219) 56(84) bytes of data.
64 bytes from 172.24.17.219: icmp_seq=1 ttl=36 time=6.41 ms
64 bytes from 172.24.17.219: icmp_seq=2 ttl=36 time=3.64 ms
64 bytes from 172.24.17.219: icmp_seq=3 ttl=36 time=3.48 ms

But if I try to do the same from WSL machine to the docker container it does not work. I have also tried to turn off the firewall completely.

Docker container was instantiated using docker compose file:

version: "3"
services:
  wgtld.local:
    image: image.registry.sk/wy/uhs:int-php56
    container_name: wgtld.local
    hostname: wgtld.local
    restart: "no"
    environment:
      WEB_UID: ${WEB_UID}
    networks:
      - ${NETWORK_NAME}
    volumes:
      - ${PROJECT_PATH}:/var/www/html
      - ./nginx.conf:/etc/nginx/sites-enabled/default:ro
      - ./supervisord.conf:/etc/supervisor/supervisord.conf:ro
      - ./xdebug.ini:/etc/php/5.6/mods-available/xdebug.ini
      # - ./pool-www.conf:/etc/php/5.6/fpm/pool.d/www.conf:ro
    labels:
      - traefik.enable=true
      - traefik.http.routers.wgtld.rule=Host(`wgtld.local`)
      - traefik.docker.network=${NETWORK_NAME}
      - traefik.http.services.wgtld-service.loadbalancer.server.port=80
    privileged: true
    ports:
      - "8080:80"
    healthcheck:
      test: ["NONE"]
networks:
  system_apps:
    external: true

I think the issue is mainly that i do not understand well:

• If the project im working on (its working directory is on wsl) and phpstorm wants to connect to establish the xdebug session does it use WSL ip or host machine IP?
• I was trying to use

Im not sure If I used the correct configuration choice?

Guys any ideas / tips / tricks would be more than welcome!
Thank you!

Andrej Rehak, given that you specify xdebug.remote_host, you don't need xdebug.remote_connect_back to be enabled.
In general, the configuration looks correct, so it makes sense to check what you have in xdebug.log after you initiate a debugging session.