Xdebug Client connection timeout. :-( using phpstorm 7.1.3 / vagrant / virtualbox / magento

Question

For some time I used Phpstorm EAP and worked fine with xdebug. I recently purchased a personal license and imported all of my settings from EAP into 7.1.3. Now xdebug is not working.

Here xdebug.ini

zend_extension=xdebug.so xdebug.remote_host = 192.168.56.1 xdebug.remote_cookie_expire_time = 36000 xdebug.remote_log = /tmp/xdebug.log xdebug.remote_port = 9000 xdebug.remote_handler = dbgp xdebug.remote_mode = req xdebug.remote_enable = 1 xdebug.remote_autostart = 0 xdebug.idekey="PHPSTORM" xdebug.scream=0 xdebug.remote_connect_back=1 xdebug.show_local_vars=1 

xdebug is also displayed in php.ini. I even ran it at http://xdebug.org/wizard.php and the latest version is installed.

Phpstorm is listening on port 9000 for xdebug, and "Listen to PHP debugging connections" is enabled.

My xdebug journal constantly tells me about this:

 Log opened at 2014-07-18 17:46:16 I: Checking remote connect back address. I: Remote address found, connecting to 192.168.56.1:9000. E: Time-out connecting to client. :-( Log closed at 2014-07-18 17:46:16 

I even tried editing the registry: http://brianreiter.org/2010/09/18/fix-virtualbox-host-only-network-adapter-creates-a-virtual-public-network-connection-that-causes-windows- to-disable-services /

No matter what I try, xdebug expires. Even with all firewalls.

I am on Windows 7 Enterprise. VM - puphpet / centos65-x64

EDIT Forgot to mention IDE key in Phpstorm - PHPSTORM

Answer 1

To answer your confusion directly, two settings are highlighted. These are xdebug.remote_host and xdebug.remote_connect_back . The previous IP address is incorrect, especially in Vagrant settings. It should be something like 10.0.2.2 . In addition, the last setting should not be defined and enabled. When it is turned on, it completely ignores the previous parameter , which makes it useless. To summarize, we can say that the first parameter is incorrect, and the last parameter ignores it, but this last parameter is also incorrect. These settings are only part of the reason Xdebug will not work.

Advanced: Configuring Xdebug in PhpStorm with Vagrant

Vagrant represents a level of complexity that is not found in the standard non-virtualized development environment. Although the above points are probably correct, there are still additional settings and procedures that must be followed in order to run Xdebug in PhpStorm through Vagrant. For some time I struggled with this, and after several unsuccessful attempts, I managed to establish a connection. There is also a large shortage of documentation available on the Internet to perform this setup, so after successfully setting up the entire system, I documented the recommendations on my blog. The whole setup process is described in detail, seasoned with the corresponding screenshots. I also use CentOS 6.5 64bit, and the recommendations reflect that. It has even been tested against Magento.

How to configure Xdebug in PhpStorm via Vagrant