XDebug stopped working in PHPStorm

Question

I hit my head about it for hours.

I came back to do some work in PHPStorm after not using it after a couple of weeks, and for some reason debugging no longer works. It worked, but now this does not happen, and I have no idea what is happening.

I work on Windows using IIS, PHP version 5.3.8. XDebug is installed, and I installed the configuration in PHP.ini in accordance with the usual instructions.

When I run phpinfo (), everything looks fine (i.e. there is XDebug).

I double-checked various settings, downloaded a slightly newer version of XDebug than I used (Xdebug v2.2.1), but nothing seemed to explode it.

Can someone please give me some tips on what I can look at next?

UPDATE:

I spent a few more hours beating my head against this, and did not seem to get much more. XDebug is installed and loaded, according to phpinfo (). I turned on logging, but it really doesn't tell me much, except that XDebug really connects ...

Log opened at 2013-02-17 04:13:07 I: Connecting to configured address/port: localhost:9000. I: Connected to client. :-) -> <init xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" fileuri="file:///C:/web/dbg/index.php" language="PHP" protocol_version="1.0" appid="6912" idekey="PHPSTORM"><engine version="2.2.1"><![CDATA[Xdebug]]></engine><author><![CDATA[Derick Rethans]]></author><url><![CDATA[http://xdebug.org]]></url><copyright><![CDATA[Copyright (c) 2002-2012 by Derick Rethans]]></copyright></init> -> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" status="stopping" reason="ok"></response> Log closed at 2013-02-17 04:13:07 

So it seems that the problem is on the PHPStorm side, but I don't see where. I tried to create a very simple project, but could not get it for debugging.

Answer 1

Don't you hate it when you struggle with something for hours, and then in despair try something simple and it works?

I decided to try another port, 9001 instead of the standard 9000, and it WORKS!

Now I understand that I recently installed Twonky (for streaming video to my TV), and when I checked the settings, it was ... port 9000.

Answer 2

If the same question was today, I found this question along with several other SO questions, so I decided to post a solution that fixed it for me.

I was unable to map the file system. Which is strange, because I saw PHPStorm asking me when they were already out.

Hope this helps someone in the future :)

Answer 3

There was the same problem after updating El Capitan. The first hint that I used is Run -> Check Web Server Debugging. This tool from PHPStorm gave me a hint about xdebug.remote_host I am using v hosts and he complained to localhost that this is not the correct value. So I updated the xdebug parameter with xdebug.remote_connect_back=On and it will work!

Answer 4

Newer versions of PHPStorm have a debugger check. The official PHPStorm blog has a feature entry that can help you figure it out.

One snafu for me when I installed the box with php-fpm configured is that php-fpm also works on port 9000 by default, so I had to change the configured port in the php.ini and PHPStorm settings to about 9001.

For what it's worth, my current php.ini installation for xdebug is:

 [xdebug] zend_extension="/the/path/to/xdebug.so" xdebug.file_link_format="txmt://open?url=file://%f&line=%l" xdebug.remote_enable=1 xdebug.remote_autostart=On xdebug.remote_port=9001 xdebug.profiler_enable_trigger=1 xdebug.max_nesting_level=250 

Answer 5

I had the same problem! Finally, I realized that all my settings were correct, but on the browser side I did not enable debugging in the Chrome browser. Each browser has its own way to enable debugging to get started.

Answer 6

I had the same problem and solved it by deleting all the hours and then reloading phpStorm

Answer 7

I had the same problem and tried all the solutions that I could find in SO and on other sites (checked that both phpStorm and Xdebug were on the same ports, checked that I had a server mapping in the file system , reinstalled Xdebug, etc.), but in the end the problem was that we were launching the site on the internal server, and someone from IT changed the IP address of my computer to an address that is filtered out from allowed addresses, which can be connected to this server. This is why phpStorm started to ignore breakpoints from Xdebug.

I hope this helps someone in the future and saves him many hours.

Answer 8

I decided it myself too, because PHP-Storm and PHP-FPM are listening on the same port ... just kill the whole php-fpm port.

Answer 9

It was found that if the xdebug log file is not writable, it may not work. It is always better to set xdebug.remote_log and make it writable.