I use PHPStorm along with Xdebug to step through my code. PHPStorm is running on a Windows 7 machine, and my local webserver is running on a separate CentOS 6.4 machine. I've done a phpinfo(); to verify that Xdebug is being loaded by PHP, and it is. The following are the settings for my Xdebug in the PHP.ini:
[xdebug]
zend_extension="/usr/lib/php/modules/xdebug.so"
xdebug.remote_enable = 1
xdebug.remote_port = 9000
xdebug.remote_host = "192.168.1.130"
xdebug.remote_log = "/var/log/httpd/xdebug_log"
I similarly setup PHPStorm to use my CentOS server as the debugging server, and I listen for connections. I assigned static IPs to both of these machines. Using a Chrome Xdebug plugin to set the appropriate cookies, I attempt to set a breakpoint, but nothing happens. When I go to look in /var/log/httpd/xdebug_log (which has 777 permissions), nothing is written there. I've opened up port 9000, and I can telnet from my CentOS machine back to my Windows machine on port 9000 no problem. I also set SELinux to permissive, but to no avail.
Any ideas what could be happening here?
Try to configure your project in PhpStorm
Open Settings->Languages & Frameworks->PHP->Debug
Uncheck the "Ignore external connections through unregistered server configurations" option
OK
Add to your php.ini:
xdebug.mode=debug
I was having the same issue, below are the steps I performed to resolve it:
Make sure you have xdebug installed and in php.ini uncomment xdebug.mode=debug
Open Settings->Languages & Frameworks->PHP->Debug, Assign Debug Port value, you can find this port from php.ini. In my case, it was 9002
Now Validate debugger configurations - here you need to add the path to your web application files and URL. Click validate.
Now Start Listening -> Enable listening for PHP Debug Connection.
After this setup you can set a break point and start debugging with XDEBUG.
In my case, i added folder that im debugging to exclusive, so it return 502 or blank page when i put breakpoint. Remove exclusive folder and everything working.
You can consider this blog to find more solution: Link.
sudo gedit /etc/php/7.2/mods-available/xdebug.ini
zend_extension=xdebug.so
xdebug.remote_enable = 1
xdebug.remote_port = 9898
xdebug.idekey = “PHPSTORM”
xdebug.show_error_trace = 1
xdebug.remote_autostart = 0
xdebug.mode=debug
xdebug.client_port=9898
I need help to configure xdebug, for debugging projects from IDE netbeans.
These are the features of my components:
XAMPP 1.8.2
PHP: 5.4.16
netbeans: 7.3.1
Apache: 2.4.4 (Win32)
this is the final part of my php.ini file:
[XDebug]
zend_extension = "C:\xampp\php\ext\php_xdebug-2.2.3-5.4-vc9-nts.dll"
;xdebug.profiler_append = 0
;xdebug.profiler_enable = 1
;xdebug.profiler_enable_trigger = 0
xdebug.profiler_output_dir = "C:\xampp\tmp"
;xdebug.profiler_output_name = "cachegrind.out.%t-%s"
xdebug.remote_enable = 1
xdebug.remote_handler = "dbgp"
xdebug.remote_host = "127.0.0.1"
;xdebug.trace_output_dir = "C:\xampp\tmp"
when I run phpinfo(), there is no xdebug installed, and when I debug a project from netbeans, it says "Waiting For Connection (netbeans-xdebug)".
can someone help me to configure it?
Have you rectified the issue ? If not then please try this.
1.) php.ini file content
[xDebug]
zend_extension = "c:\xampp\php\ext\php_xdebug-2.2.3-5.4-vc9.dll"
xdebug.remote_autostart=on
xdebug.remote_enable=on
xdebug.remote_enable=1
xdebug.remote_handler="dbgp"
;xdebug.remote_host="localhost:81"
xdebug.remote_host=192.168.1.5
;xdebug.remote_connect_back=1
xdebug.remote_port=9000
xdebug.remote_mode=req
xdebug.idekey="netbeans-xdebug"
xdebug.remote_host=192.168.1.5 - This is the IPv4 address of my system, I changed to this because I couldn't debug with localhost and 127.0.0.1.
in NetBeans IDE, open Tools-> Options -> PHP -> Debugging. The values of debugger port and Session Id should match with the port and idekey specified in php.ini.
Now save php.ini, restart Apache and try to debug.
Thanks Johnson
When Netbeans starts a Debugging session, it starts two Listeners, one on 0.0.0.0:9000 (all IPv4 IPs the system has), and the other on the IPv6 interface.
If Netbeans and the Web Server are on the same system, ideally XDebug would be configured to send the data back to 127.0.0.1:9000, on which NetBeans would be listening on (and only per session)...
xdebug.remote_enable=1
xdebug.remote_handler=dbgp
xdebug.remote_host=127.0.0.1
xdebug.remote_port=9000
xdebug.remote_autostart=0
xdebug.remote_connect_back=0
If for whatever reason XDebug is not able to report back to 127.0.0.1, or Netbeans is not listening on 127.0.0.1, you can configure XDebug to send the data back to the $_SERVER['REMOTE_ADDR'] of the original request...
xdebug.remote_connect_back=1
This way you don't have to specify the exact IP (i.e., as in the above answer the LAN IP: 192.168.1.5). The downside here is that any source can connect.
If you have further trouble, this...
xdebug.remote_autostart=1
... will also start the debugging process for all requests, and not just for the ones with the proper session start query or cookie. The downside here is that all requests will initiate debug data collection and reporting back (making everything slower, and generating more data).
Though from what I've gathered, the majority of these "Waiting For Connection (netbeans-xdebug)" issues on Windows (with XAMPP, Wamp-Server, etc) are usually a result of Windows Firewall and McAfee (or other firewall and anti-virus software) blocking the connection...
Source: Netbeans "Waiting For Connection (netbeans-xdebug)" Issue
I am a .Net programmer and very new to PHP.
Recently I was trying to host an open source PHP application on my machine(Windows). After the Struggle for 5-6 days I will list the steps which worked for me.
I uninstalled every previous installations of XAMPP and NetBeans and proceeded with fresh installations.
This might not be the solution for everyone but it worked for me and I hope it helps someone.
install XAMPP
install netbeans for PHP.
Open IIS and stop it. It is running on port 80 by default.(I am running XAMPP on port 80 i.e. default, Running on other port might need additional configuration settings)
Open XAMPP control panel and start Apache. If port 80 is free no problem should arise.
Open localhost in browser in should display XAMPP home page.
open phpinfo() link on the left pane and copy all the contents on page.
Go to: http://xdebug.org/wizard.php and paste all the content in TextBox and click Analyze my phpinfo output. It will diplay you the Xdebug file suitable for your configuration.
Download the given Xdebug dll and copy it in C:\xampp\php\ext (Xampp being the default Xampp installation directory)
Goto XAMPP control panel, click on Config button in front of Apache and select php.in,
Find line similar or exacly like,
;zend_extension = "C:\xampp\php\ext\php_xdebug.dll"
(Semicolon means it is commented)
Remove the semicolon and replace the path with the path of dll you just copied like:
zend_extension = "C:\xampp\php\ext\php_xdebug-2.3.2-5.4-vc9.dll"
Similarly find lines
;xdebug.remote_enable = 0
;xdebug.remote_handler = "dbgp"
remove semicolons in front of both lines and make remote_enable = 1
xdebug.remote_enable = 1
xdebug.remote_handler = "dbgp"
Restart Apache server.
Copy your website code under C:/XAMPP/htdocs/(your_website)/
that means your index.php should be at C:/XAMPP/htdocs/(your_website)/index.php
Open Netbeans select New project -> PHP -> PHP project from existing source and select the folder you just copied in htdocs folder.
Set it to run on Local web server.
Set a breakpoint on first line of index.php and debug.
That's it.
Additional settings were suggested on various different posts but above mentioned steps worked perfectly for me.
I want to mention something here about xdebug.remote_host
xdebug.remote_host="127.0.0.1"
Is Not valid. It may work in some cases, but the quotes can also cause issues. Most people don't have issues when using IP addresses in quotes, but this sets a bad precedent. It makes people think that if you want to use a hostname or URL you need to put it in quotes. This is incorrect, urls in quotes will not work.
If you want to debug using a url, you can do this by just putting the url after the equals like this:
xdebug.remote_host=subdomain.mydomain.com
I also want to mention that if you have a port number, don't add it. This doesn't work:
xdebug.remote_host=subdomain.mydomain.com:9000
This is what you want to do:
xdebug.remote_host=subdomain.mydomain.com
xdebug.remote_port=9000
If you do this, I also caution you make sure remote_connect_back is disabled. Like this:
xdebug.remote_connect_back=0
or you can ommit it entirely, like this:
;xdebug.remote_connect_back=1
If remote_connect_back is enabled, it will try and pull your IP address from the incoming connection and ignore the remote_host and port setting.
Xdebug uses plain old TCP to make connections. This is not HTTP. This means tools like Fiddler will not show any packets or information on debugging. If you need to debug, and see if the server is making a call to your IDE there are a few ways you can go about checking.
Wireshark will allow you to see TCP traffic. Also if you are on Windows, Microsoft Message Analyzer can also monitor TCP.
But, if all you are trying to do is remove your IDE is a possible cause of remote debugging problems, I suggest instead you start a local TCP server.
This is a great free java program to start a TCP server: http://sockettest.sourceforge.net/
In the IP Address section, just list 127.0.0.1 or leave it at 0.0.0.0. Then list the port number, which is usually defaulted to 9000 for xdebug.
Once the TCP server is running, open your remote webpage with an xdebug_break(); function call in it. This will tell xdebug on the remote server to start debugging on whatever server and port you listed in your php.ini.
Watch the socket server and see if you get a connection. The first data sent should look something like this:
<init appid="APPID"
idekey="IDE_KEY"
session="DBGP_COOKIE"
thread="THREAD_ID"
parent="PARENT_APPID"
language="LANGUAGE_NAME"
protocol_version="1.0"
fileuri="file://path/to/file">
If you have made it this far, remote debugging is working! Just stop the server and setup your IDE to listen on that port!
If you are like most of us, your developer machine is behind a router with NAT. This means that everyone in your office has the same public IP address. This is a problem because when xdebug contact that IP address to start debugging, it hits the router, and not your computer. The router can be configured to pass certain port numbers to individual computers, but you may not want to do that as that port will be open until you change your router settings back.
Another option is to use SSH. There is a great example of how to do this here: http://stuporglue.org/setting-up-xdebug-with-netbeans-on-windows-with-a-remote-apache-server/#attachment_1305
My preferred option is to use Ngrok. Ngrok is a great tool for redirecting http, https and TCP traffic. In order to use the TCP redirect function you need to sign up for a free account.
Once you have signed up for an account, and added your API key to your computer run this command on the computer that your IDE is on:
ngrok tcp 9000
This will open a tcp (not http) tunnel from the ngrok server to whatever machine you ran the command on. I am using port 9000, you can change this port if your IDE is configured for a different Xdebug port.
This is what you should see:
You will need to see what the url is for the TCP tunnel that was opened. In this example it is:
0.tcp.ngrok.io:14904
For this session, the Xdebug setting on your server should be this:
xdebug.remote_host=0.tcp.ngrok.io
xdebug.remote_port=14904
The URL and port will change each time ngrok is launched. If you want to have the same url and port, you have to upgrade to a paid account. Make sure to restart apache after you make changes to your php.ini.
I just spent hours reading so many answers on this page and others like it, and nobody mentioned what ended up being the solution for me:
Make Sure Your Chosen Port Settings Match in All 3 Locations
My problem was that there are THREE places that the chosen port needs to match. Two of mine said 9001 and one said 9000. I changed them all to 9000.
That was the problem and why Netbeans would only say “Waiting For Connection (netbeans-xdebug)”.
The 3 port setting locations are:
php.ini (xdebug.remote_port=9000)
project properties > Run Configuration > Advanced
Netbeans > Tools > Options > PHP > Debugging
Check also the "windows" firewall settings.
For me it doesn't worked because my LAN network was declared as "Public network".
After i switched it to "Work network" it worked fine.
Try this setting if you have latest version of Xdebug the old version syntax has been changed
https://xdebug.org/docs/upgrade_guide
xdebug.mode=debug
xdebug.start_with_request = Yes
;xdebug.mode=profile
;xdebug.start_with_request=trigger
xdebug.client_host = "localhost"
xdebug.client_port = 9003
xdebug.remote_handler = "dbgp"
xdebug.log = "C:\xampp\tmp\xdebug\xdebug.log"
xdebug.trace_output_dir = "C:\xampp\tmp"
In my case the Apache log showed a PHP warning about not having set date.timezone. Xdebug/netbeans began working as soon as I set it in php.ini and restarted apache.
date.timezone = America/Los_Angeles
This is PHP 5.5.
I'm on Windows with xampp and changed the [XDebug] section of my php.ini (at the bottom) to the following to get it working:
zend_extension = "C:\xampp\php\ext\php_xdebug.dll"
xdebug.remote_enable=on
xdebug.remote_handler=dbgp
xdebug.remote_host=localhost
xdebug.remote_port=9000
Sourced from the Netbeans wiki here: http://wiki.netbeans.org/HowToConfigureXDebug
If you have Apache running, remember to restart it after configuring XDebug and saving php.ini.
Adding this did work for me:
xdebug.idekey=netbeans-xdebug
I my case if I add following in php ini it did not work
zend_extension_ts="C:\PHP\PHP560\ext\php_xdebug-2.4.0rc4-5.6-vc11.dll"
But If I add
zend_extension="C:\PHP\PHP560\ext\php_xdebug-2.4.0rc4-5.6-vc11.dll"
It is working fine.
Having correctly set up the php.ini file, netbeans, port forwarding on the router, I was still getting the wretched "waiting for connection (netbeans-xdebug). I eventually noticed on the netbeans page "Do not forget to set output_buffering = Off in your php.ini file".
So I checked the /etc/php/7.x/apache2/php.ini file and sure enough it's value was 4096. So I reset output_buffering=Off and lo it worked !!!
Hope this helps someone, as the message implies it is a connection error rather than a configuration error.
check this out: Launch XDebug in Netbeans on an external request
another way is to open a new window:
try to go on Project > run configuration > advance
and switch to default, check if it opens another window in the browser
A try could be to start php -i in command window. When redirecting the output an error was
For me it was the FINAL solution because I had a wrong version of Xdebug downloaded
For me it should have been : php_xdebug-2.1.2-5.3-vc6.dll
But I had: php_xdebug-2.2.4-5.3-vc9.dll. So an error occurred from php -i
E:\Programme\php>php -i > myOutputFromPhp
yields following ERROR
Cannot load Xdebug - it was built with configuration API220090626,TS,VC9, whereas
running engine is API220090626,TS,VC6
I had the same problem.
why?
First I installed WAMP, thank Netbeans and they work together as a charm.
Later I installed XAMPP and Localhost sites were run smoothly but NetBeans could never connect to XAMPP (netbeans-xdebug).
At the same time NetBeans were working good with Wamp.
My solution was to go back to Wamp. It is better than nothing.
My PC:
Win-7-32, NetBeans-8.0.2,
wampserver2.5-Apache-2.4.9-Mysql-5.6.17-php5.5.12-32b
xampp-win32-5.6.8-0-VC11
For Ubuntu users:
sudo su
apt-get install php5-dev php-pear
pecl install xdebug
find / -name 'xdebug.so' 2> /dev/null
it will return something like: /usr/lib/php5/20121212/xdebug.so
vi /etc/php5/apache2/php.ini
add this line: zend_extension="/usr/lib/php5/20121212/xdebug.so"
service apache2 restart
restart IDE
I spent a lot of time trying to get the optimal set up and thing this deserves its own reply, even though #Johnson T A's one it's almost correct.
He says
xdebug.remote_host=192.168.1.5 - This is the IPv4 address of my system, I changed to this because I couldn't debug with localhost and 127.0.0.1.
Well, not everybody can use a private address, or it may be dynamic, or other things. Also, in my case I was suffering from very long wait times before debugging actually started - 30 s or so every time. That was unpractical.
I'm sure everyone having these problems are at least on Windows 7 or so. The problem is related to a mix between name resolution and xdebug. To overcome them make sure that:
Port 9000 is not in use. If that's the case, change it to a unused one, both in php.ini and in netbeans.
Make sure that xdebug.remote_enableis on.
If you want to be able to debug using both localhost and 127.0.0.1 addresses, open \Windows\System32\drivers\etc and make sure that there you have the following lines:
127.0.0.1 localhost
::1 localhost
Make sure that the first line doesnt have a # before it and the second one does have it.
My working php.ini section (I don't need profiler so I disabled it):
[XDebug]
zend_extension = "C:\xampp\php\ext\php_xdebug.dll"
xdebug.profiler_append = 0
xdebug.profiler_enable = 0
xdebug.remote_enable = on
xdebug.remote_handler = "dbgp"
xdebug.remote_host = "localhost"
xdebug.remote_port = 9001
xdebug.trace_output_dir = "C:\xampp\tmp"
xdebug.remote_log = "C:\xampp\tmp\xdebug\xdebug.log"
xdebug.idekey = "netbeans-xdebug"
xdebug.remote_autostart = on
xdebug.remote_connect_back = on
Stop netbeans debugger. Restart Apache.
I bet you won't suffer from long waiting times anymore nor strange behaviour with debugger.
Explanation:
Althought in etc/hosts they say "localhost name resolution is handled within DNS itself", for whatever reason it doesn't work well with xdebug if you don't have it explicitely stated in that file. Explicitly putting it seems to do no harm overall, and solves this problem with xdebug. But also you need to explicitly disable the sIPv6 short notation for localhost (::1) in order for all this to work. Don't know the internal reasons but triead all the combinations and this one works for me like a charm.
I had this issue for one project, but not for others. So xdebug was correctly configured, the project settings were ok, but it still did not work.
So I just deleted the nbproject subdirectory, containing the project settings, and created a new project with the existing source. This solved the issue for me.
Select a specific browser for debugging:
Right Click on project -> select Properties
Select categories: Browser then selected a specific browser for debugging
If your xdebug is not working correctly, check your server log:
$ sudo less /var/log/httpd/error_log
To check connections, use this command:
$ sudo netstat -an
After starting debug on netbeans, if you use the netstat command, you can see the port of xdebug (probably it's 80):
tcp6 0 0 192.168.33.10:80 192.168.33.2:49901 ESTABLISHED
The port of netbeans is 9000:
tcp 0 0 192.168.33.10:52024 192.168.33.2:9000 ESTABLISHED
You can change the xdebug's port from here (From the top menu, Tools -> Options -> PHP):
If the connection is not established, it is highly possible that your connection is blocked by your anti-virus program or firewall. You can check it in your anti-virus program or firewall and remove the block as it is a safe connection.
After you make changes to your php.ini or xdebug.ini files, regardless of how you're running your web server, make sure to restart that web server (for example: service httpd restart on CentOS) or Apache will not pick up the changes you've made to that .ini file.
The xdebug package on CentOS is "phpXXu-pecl-xdebug".
Defaults on most recent Xdebugs are usually fine. It's only strictly necessary to get these two values right, somewhere in an Apache .ini file:
xdebug.remote_enable=on
xdebug.remote_host=[DNS entry that resolves to the IP4 of your debugger]
I had the same problem and tried to solve it for hours. I finally found out that the chrome extension ipflood which changes the headers to make it look like you are using a proxy, was the cause.
It works perfectly fine after I disabled it!
Also, consider whether the NTS or the TS version of xdebug is suitable for your case.
Check the Apache log for hints
For Windows users this is what worked for me:
Obtain your phpinfo() output and copy it here: https://xdebug.org/wizard
It will tell you what is the exact dll you have to download.
Copy that dll into C:\xampp\php\ext, and rename it to php_xdebug.dll
Pay attention at the version of xdebug you have installed. That was the key for me! My version of xdebug was version 3 so I had to...
Update php.ini file to have the following (for xdebug v3):
[XDebug]
zend_extension = xdebug
xdebug.mode=debug
xdebug.client_host=localhost
xdebug.client_port=9000
xdebug.idekey="netbeans-xdebug"
Restart Apache Webserver and Netbeans.
I'm trying to use XDebug in the following scenario
my computer Windows 7, Netbeans 6.9
Physical Host at computer on the same network (Windows 7) with virtual Box
Virtual CentOS 6.2, with Apache server 2.2.15 and PHP 5.3.3
the PHP code of my website is on a shared folder on CentOS, in /var/www/html/mysite and have separate and can access it by server ip 192.168.1.240
Edited C:\Windows\System32\drivers\etc\hosts 192.168.1.240 mysite
the PHP code is accessible from my Windows host, on \\HostIP\html\mysite, with R/W permissions
I created a Netbeans project on my computer, pointing to \\HostIP\html\mysite. In the project Run configuration, I have the following:
Run as: Remote Web Site
Project URL: http://mysite/
Index file: index.php (does exist in the project)
In the Advanced Run Configuration:
I checked "Default"
I haven't touched the proxy settings
I have the following in the php.ini on my CentOS VM
;extension=xdebug.so
zend_extension="/usr/lib64/php/modules/xdebug.so"
xdebug.remote_enable=on
xdebug.remote_log="/var/log/xdebug.log"
;xdebug.remote_host=192.168.1.31
xdebug.remote_connect_back=1
xdebug.remote_handler=dbgp
xdebug.remote_port=9000
note: I tried the configurations with extension=xdebug.so and tried commenting xdebug.remote_connect_back=1 with uncomment xdebug.remote_host=192.168.1.31 which is my computer ip address.
so basically i have all the configurations like this image
but still not working! after run the debugger will open this url
http://mysite/index.php?XDEBUG_SESSION_START=netbeans-xdebug
and nothing will happened just netbeans Listing waiting for Xdebug connection
When i want to debug on a remote host i normally have to forward my local 9000 port to the remote server's local 9000 via a ssh tunnel:
ssh -R 9000:localhost:9000 username#remote.example.com
Use bitvise ssh client or putty on windows to get the same effect.
Also in the project settings -> run configuration -> Advanced button
make sure to specify the remote and local full paths the the project files so the debugger can attach (don't worry about the port in this screen leave as standard).
I know this is an old post, but it seemed like the one I ran across the most tonight.
The NAT Network setup is the way to get the least amount of conflict. In the Windows 7 Firewall, setup a custom Inbound Rule to allow inbound traffic to port 9000 for the entire /24 network that the VM is on (192.168.202/24).
My working XDebug setup in the php.ini, using 2.2.7 with Netbeans 8.0.2:
zend_extension=xdebug.so
xdebug.remote_enable=1
xdebug.remote_connect_back=1
xdebug.remote_port=9000
xdebug.idekey="netbeans-xdebug"
xdebug.show_local_vars=0
;xdebug.extended_info=1
xdebug.output_buffering=off
xdebug.remote_log=/var/log/xdebug.log
Lastly, I want to point out that Netbeans listens for the remote address setup in the remote file config. Doing a quick netstat -an showed that Netbeans was listening on port 9000, with a CLOSE_WAIT status on an old address from my initial bridged network setup. Even after changing the Project URL, and the Remote Connection IP address, and closing several xdebug connections, this never changed. Only after closing Netbeans, does the stale connection drop. Once Netbeans is started again, the new remote server URL is used for the remote xdebug connection.
Mention of Netbeans holding a stale state was never discussed, and the ability to stop the xdebug connection from the IDE gives a false sense of resetting the socket.
If it still doesn't work, use the provided debugclient on the VM, visit the project page with "?XDEBUG_SESSION_START=netbeans-xdebug" appended to the index.php URL, and watch for the xdebug info to come in. At least then you know it works locally.
Try setting up any breakpoint to your executed script. Debug session may not show up while ide does not respect "break at first line" flag.
Also check if xdebug.idekey property in php.ini equals to ideKey in Netbeans' settings.
I am trying to get Xdebug remote debugging to work, I am using PHPStorm as my IDE.
My webserver/code is hosted on a remote machine (amazon ec2).
I have the following lines in my php.ini on my remote server (PHP CLI since I am doing PHPUnit debugging)
zend_extension=/usr/lib/php5/20090626+lfs/xdebug.so
xdebug.remote_enable = 1
xdebug.remote_autostart = 1
xdebug.remote_handler = dbgp
xdebug.remote_mode = req
xdebug.remote_connect_back = 1
xdebug.remote_port = 9000
Since I am programming from my home network, I opened port 9000 on my personal router.
I have PHPStorm's xdebug server set to point to the remote server on port 80 with Xdebug as it's Debugger.
Now when I try to debug a PHPUnit test from PHPStorm it just says
'waiting for incoming connections with ide key '12115'
Except, it picks a random ide key every single time (I want to hope that PHPUnit is setting the idekey on the server itself)
I have been trying to get this to work for over 10 hours, I have tried defining my a specific remote_host in the php.ini instead of using remote_connect_back but that also did not work. I have tried setting an idekey in php.ini and that did not work as well.
Is there anyway to confirm that Xdebug is working as intended on the webserver side? How can I test my Xdebug settings without using Phpstorm, I don't know if it is a connection issue between my home network and the remote server or what.
Any guidance to help narrow down the issue would be great.
I know that the question is a little old, but since I had the same problem and just found a solution, I have decided to post here for anyone interested.
My solution is heavily based on the one provided by Rafael Dohms in
his blog post entitled: Debugging PHPUnit Tests in NetBeans with
XDebug
Environment
IDE: PHPStorm 6.0.2
Server: WAMP Server (32-bit & PHP 5.4.3) 2.2E
XDebug: 2.2.2
XDebug
zend_extension=c:\wamp\bin\php\php5.4.3\ext\php_xdebug-2.2.2-5.4-vc9.dll
xdebug.extended_info=1
xdebug.remote_enable=1
xdebug.remote_handler=dbgp
xdebug.remote_mode=req
xdebug.remote_host=127.0.0.1
xdebug.remote_port=9000
xdebug.remote_log=c:/wamp/tmp/xdebug/xdebug_remote.log
The above configuration parameters go into the "php.ini" file for CLI. For the default WAMP installation, the full path to this file is: C:\wamp\bin\php\php5.4.3\php.ini
PHPStorm
First of all, you must create a "Server Configuration" (google "Creating a Server Configuration - JetBrains" for the official doc on the subject) specifying "Xdebug" as the "Debugger".
Then, create a new "PHP Remote Debug Configuration" (google "Creating and Editing Run/Debug Configurations - JetBrains" for the official doc on the subject) specifying the following values under the "Configuration" section:
Servers: the server created above
Ide key: PHPSTORM
Now, select that configuration and press the "Debug" button (or "Shift + F9"). PHPStorm will display the "Debug" panel and show the message: Waiting for incoming connection with ide key 'PHPSTORM'
Finally, "run" you PHPUnit test. There are several ways. One of them is:
Right click the name of the file the PHPUnit test resides in.
Select "Run file name"
That's it! XDebug will take control from here on.
If you're running Xdebug 2.2.0RC1, then the remote debug-log (http://xdebug.org/docs/all_settings#remote_log) will tell you succeeded and failed connection attempts. That might pinpoint whether the problem is on the Xdebug side, or phpstorm side.
In my case, the problem was that I had the xdebug config in /etc/php/fpm/php.ini, but php-cli uses /etc/php/cli/php.ini.
Since it took me a day to get it to work, I will sum up, what in learned:
Make sure, you are changing the right php.ini, XAMPP uses another php.ini and php version, than the one preinstalled on OS X Mavericks.
Define a logfile and if nothing is written into it, you a changing the wrong php.ini
In phpstorm you can validate your server connection and gain insight, if you are working on the right php.ini or what is still wrong.
You have to change settings for debug (might be worth to change the port to 9001), the server, all in phpstorm preferences and set up.
You have to set the php language level and the Interpreter (use the one your Apache mysql php configuration uses) e.g. /Application/XAMPP/xamppfiles/bin, click on ... to see Php and if debugger is attached. You might have to use another version of xdebug.
In Servers you have to define Host as
http://yourdefinitionofprojectonlocalhost
with usually Port 80 and Xdebug. Here it is essential to validate the remote environment.
Under debug you can set the Debug Port, if you change it to 9001, change it in the php.ini too, choose Can Accept external Connections.
If you do not enable Start to listen for PHP Debug Connection, you have no hope of getting it to work (Icon in upper right corner or down in Run menu).
In Edit Configurations... you have to define a PHP Web Application to be able to use Debug in the Run menu.
It took me a day to get it to work. The main issues being editing the wrong php.ini (do not forget to restart apache after edit) and the fact, that xdebug did not work with the php version.
As you can see I tried a lot of options in my php.ini and ended up using version of xdebug in found in my mamp directory:
;zend_extension="/usr/lib/php/extensions/no-debug-non-zts-20100525/xdebug.so"
zend_extension="/Applications/MAMP/bin/php/php5.5.10/lib/php/extensions/no-debug-non- zts-20121212/xdebug.so"
[xdebug]
;xdebug.var_display_max_children = 999
;xdebug.var_display_max_data = 99999
;xdebug.var_display_max_depth = 100
;xdebug.remote_enable = 1
;xdebug.remote_port=9001
;xdebug.profiler_enable=1
xdebug.remote_connect_back=0
;xdebug.remote_handler=dbgp
;xdebug.remote_host=localhost
;xdebug.profiler_output_dir=/Users/mypath/tmp
xdebug.remote_log=/Users/mypath/xdebug.log
;xdebug.remote_mode=req
xdebug.remote_enable=1
xdebug.remote_handler=dbgp
xdebug.remote_mode=req
xdebug.remote_host=127.0.0.1
xdebug.remote_port=9001
Wish you more speedy success than I had.
In my case, it started working when I changed the port to something other than 9000.
Phpstorm's phpunit command was now:
/usr/bin/php -dxdebug.remote_enable=1 -dxdebug.remote_mode=req -dxdebug.remote_port=9002 -dxdebug.remote_host=10.0.2.2 /var/www/application/vendor/phpunit/phpunit/phpunit --bootstrap /var/www/application/tests/Bootstrap.php --configuration /var/www/application/tests/phpunit.xml <testfile> --teamcity