#Phpstorm debug docker update#
#Phpstorm debug docker pro#
#Phpstorm debug docker mac#

The provided answer with config below is working via HTTP requests but not for phpunit tests or cli scripts.Ĭontent of /etc/php8/conf.d/50_xdebug.ini

#Phpstorm debug docker update#

Update 19 August 2022 - This does not work debugging cli scripts (phpunit tests)

#Phpstorm debug docker mac#

Disabled Mac firewall thinking that maybe port 9001 cannot be used by Docker.Changed start_with_request=trigger instead of yes.Changed xdebug.ini config to use remote host, then but no success.I don't understand why the connection is not happening/failing.Īlso I have a docker-compose.yml file that has the service API above as api: Tried: 172.18.0.4:9001 (from REMOTE_ADDR HTTP header), localhost:9001 (fallback through xdebug.client_host/xdebug.client_port) :-( ERR: Could not connect to debugging client. WARN: Creating socket for 'localhost:9001', connect: Address not available. WARN: Creating socket for 'localhost:9001', poll success, but error: Operation in progress (29). WARN: Could not connect to client host discovered through HTTP headers, connecting to configured address/port: localhost:9001. WARN: Creating socket for '172.18.0.4:9001', poll success, but error: Operation in progress (29). INFO: Client host discovered through HTTP header, connecting to 172.18.0.4:9001.

INFO: Checking header 'HTTP_X_FORWARDED_FOR'. Here are Xdebug logs inside docker container at /var/log/xdebug.log /var/www/html/app # tail -f /var/log/xdebug.log In PhpStorm I am listening to port 9001 (I use 9000 for other service). I have one container with PHP where Xdebug is installed and configured like this: zend_extension=/usr/lib/php8/modules/xdebug.so

#Phpstorm debug docker pro#

It appears that there is a currently unresolved bug in Windows Docker Desktop that makes Docker drop idle TCP connections after a period of inactivity, causing XDebug sessions to end, even if a script is continuing to run.I ported a local development setup from Linux to a new Mac machine and am having problems with getting Xdebug to work with PhpStorm in a Mac M1 Pro machine.

This comment suggests that this is because the IDE is closing the connection before XDebug can send the 'stopping' response.

But after a few minutes, step debugging is once again unavailable and requests hang indefinitely.

Restarting PhpStorm not only allows the request/script's execution to resume, but it also allows step debugging to resume.

Turning off 'Listening for PHP Debug Connections' in the IDE results in scripts immediately resuming execution, but turning it back on results in the next request also hanging indefinitely.

When execution is hanging without PhpStorm's debug panel showing any activity WARN: 20:55:26.677006: There was a problem sending 179 bytes on socket 5: Broken pipe. XDebug works for both browser requests and CLI scripts, and I can successfully initiate step debugging, but after a few minutes, the connection between XDebug and PhpStorm always seems to disappear along with a 'broken pipe' warning when XDebug tries to send a 'stopping' response, and subsequent requests/scripts hang indefinitely. simultaneous connections' value, but the problem seems to happen even if it's set to its highest value (20) without ever appearing to create more than a couple tabs in the debug panel.

There are also background processes happening automatically which might possibly be getting processed by XDebug in a way that creates more connections to PhpStorm than its 'Max. Xdebug.profiler_output_name => cachegrind.out.%p Xdebug.mode => develop,coverage,debug,gcstats,profile,trace Xdebug.gc_stats_output_name => gcstats.%p

With these XDebug settings: php -i | grep xdebug

With an entry in Settings > PHP > Servers called 'Docker'.

With a container with the environment variable PHP_IDE_CONFIG=serverName=Docker.