# Xdebug stopped working with Visual Studio **URL:** https://community.kinsta.com/t/xdebug-stopped-working-with-visual-studio/2393 **Category:** Application Support **Created:** [July 28, 2023, 6:10pm UTC](https://community.kinsta.com/t/xdebug-stopped-working-with-visual-studio/2393 "2023-07-28T18:10:05Z") **Posts on this page:** 1 **Showing post:** 5
### Author: ![ZachE](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/zache/32/1683_2.png) [@ZachE](https://community.kinsta.com/u/ZachE) #### Post date: [July 31, 2023, 11:37pm UTC](https://community.kinsta.com/t/xdebug-stopped-working-with-visual-studio/2393/5 "2023-07-31T23:37:36Z")
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: ```auto xdebug.mode=develop,debug xdebug.client_host=host.docker.internal ``` Source: [Xdebug Support: PHP debugging - #30 by nemanjac](https://community.kinsta.com/t/xdebug-support-php-debugging/71/30) If that doesn’t work, try these solutions instead, thinking it’s an xdebug options issue at play here: > [@Xdebug Support: PHP debugging](https://community.kinsta.com/t/xdebug-support-php-debugging/71/56): > > 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](https://community.kinsta.com/t/xdebug-support-php-debugging/71/35) and [this post](https://dev.to/jackmiras/xdebug-in-vscode-with-docker-379l). For some reason, using host.docker.internal no lon… > [@Xdebug Support: PHP debugging](https://community.kinsta.com/t/xdebug-support-php-debugging/71/70): > > 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… --- _[View the full topic](https://community.kinsta.com/t/xdebug-stopped-working-with-visual-studio/2393)._