Waiting for incoming connection with ide key '12998'

I have been using Storm for years and am currently on 2021.1, however, since reinstalling my system and Storm, I can not get xdebug to work anymore. I am using the Google Chrome extension.  

I have xdebug installed.  

I have the IDE Key: 

And I have set up the php.ini file for BOTH apache and the CLI 

[Xdebug]
zend_extension = /usr/lib/php/20200930/xdebug.so
xdebug.idekey =PHPSTORM
xdebug.remote_enable=1
xdebug.remote_host=127.0.0.1
xdebug.remote_port=9003

I have restarted apache several times.  I have turned on "break at first line of PHP scripts", I have Listen set on both Chrome and STORM.

I have looked on the Storm community pages, and on SO and I can not figure out why it is not working.

Any advice for me? 

 Many thanks ! 

0
7 comments

In most cases, I would start by checking XDebug logs first by adding an "xdebug.log" directive:
https://xdebug.org/docs/all_settings#log

Could you please add it and check what is logged on?

0

@Vincej

You are using Xdebug v3 but your Xdebug config still uses Xdebug v2 params. They do almost nothing in v3.

Xdebug: Upgrading from Xdebug 2 to 3 -- please go through and update your config params (in almost all cases it's just a matter of changing the parameter name; sometimes a value)

0

Hi Andriy, Thanks for that. I could not make the instructions work as given in the upgrade guide. However I found an SO a post you made answering this exact question: https://stackoverflow.com/questions/65619042/xdebug-3-config-file 

One thing that still unclear to me is that some people refer to the xdebug.ini file, but I just copied and pasted that answer into my php.ini file and Bingo it worked!  So, is putting it into the php.ini file wrong?? And if so, where is this xdebug.ini file?   

Many thanks ! 

 

0

So, is putting it into the php.ini file wrong?? And if so, where is this xdebug.ini file?

This depends on your OS / system setup.

In some setups (some Linux distros and MacOS) you can have multiple (partial) .ini files: PHP loads php.ini first and then any additional .ini files it can find.

You can see that info from "phpinfo()" output (on CLI you have a special "--ini" param just for that: "php --ini") -- topmost table: will show main config file used + any additional config files that were loaded & parsed.

Having everything in php.ini is perfectly fine. But if your system uses additional config files then the config from such additional .ini file will (should) overwrite the info from the main one (as they will be parsed after the main one).

0

Thank you - you are a rockstar! And I assume you are not even an employee of JetBrains, or are you?  

0

Well, the community would not know what to do with you! Many thanks! 

0

Please sign in to leave a comment.