ZachE
July 31, 2023, 11:37pm
5
So it looks like maybe the lsof didn’t reveal it because it’s running on a docker internal address/namespace, so you might have to find it from within the context of the devkinsta_fpm container shell:
docker exec devkinsta_fpm -c "lsof \| grep :900"
Could you try adjusting the PHP xdebug configuration:
xdebug.mode=develop,debug
xdebug.client_host=host.docker.internal
Source: Xdebug Support: PHP debugging - #30 by nemanjac
If that doesn’t work, try these solutions instead, thinking it’s an xdebug options issue at play here:
Hi @sonicviz and @jscotti , I agree that from a PHP development standpoint this is an important feature. I’m assuming when the Roadmap was finalized, basic web design needs were prioritized based on our surveys, interviews and forum engagement. I have notified our developers about this issue and spent a good deal of time figuring out how to get this work. Hopefully this works for everyone:
I based my setup on @sonicviz 's findings and this post . For some reason, using host.docker.internal no lon…
Here’s how I got it working. From the wrench/site configurations option in DevKinsta I made sure “enable xdebug” was checked. In the PHP.ini editor I had the following lines:
xdebug.remote_autostart=1
xdebug.remote_enable=1
xdebug.profiler_enable=1
xdebug.profiler_enable_trigger = 1
xdebug.discover_client_host = 1
You can verify this with a phpinfo(); output, but the config on my system was still using the classic port 9000, not the 9003 XDebug 3 supposedly moved to.
I have the PHP Debugv…