I setup Laravel Homestead. I then configured both homestead xdebug.ini and PHPStorm to make the debugging work.
Here is my xdebug.ini inside homestead
zend_extension=xdebug.so xdebug.remote_autostart = on xdebug.remote_enable = on xdebug.remote_connect_back = on xdebug.remote_port = 9000 xdebug.idekey = "vagrant"
To start a debugging session the steps I follow are
- In PHPStorm –> Start Listening for connections
- In PHPStorm set a breakpoint
- In my browser –> Use XDebug Chrome Helper OR add to my URL ?XDEBUG_SESSION_START=
- Load the page
This works perfectly. My problem is when I’m inside homestead command line and I run a
php artisan command then I can’t get it to hit my breakpoints.
What I’ve tried
XDEBUG_CONFIG="idekey=PHPSTORM" PHP_IDE_CONFIG="serverName=server_name" php -dxdebug.remote_host="127.0.0.1" artisan mycommand
php -d xdebug.profiler_enable=On artisan mycommand
I also tried to set
sudo service php5-fpm restartbut still my breakpoints never get hit in PHPStorm
Two things are important:
remote_connect_backcan not work in the CLI case because Xdebug can not detect the remote IP when you are in the console
- When using homestead / VirtualBox in the NAT network configuration, your development machine (which is running PHPStorm) does not have the IP
127.0.0.1seen from inside the VM. Instead, it has usually an IP like
10.0.2.2. To find out the correct IP, have a look at your Apache’s
The following worked for me:
php -dxdebug.remote_autostart=on -dxdebug.remote_connect_back=off -dxdebug.remote_host=10.0.2.2 artisan
- edit If your breakpoints are not hit, you have to set up the folder mappings correctly (as your path in the IDE is different from what the web server sees:
export PHP_IDE_CONFIG="serverName=yourservername"in your VM, where
yourservernameis what you configured in the screenshot under “name”
Add a Php Remote Debug Configuration with an IDE key and the server configured above
And add your IDE key and the remote_host to the VM’s XDEBUG-CONFIG
export XDEBUG_CONFIG="idekey=artisan remote_host=10.0.2.2"
Or, if that all is just too complicated or not working – you can trigger your artisan command via a url (route) using