Configure Xdebug
Install the PHP plugin
This functionality relies on the PHP plugin that should be installed and enabled in your IDE.
The plugin is available only in IntelliJ IDEA Ultimate.
Press Ctrl+Alt+S to open the IDE settings and select
.Switch to the Marketplace tab and use the search field to find the PHP plugin.
Click Install and restart the IDE if prompted.
Download Xdebug
Download the Xdebug extension compatible with your PHP version and install it as described in the installation guide.
If you are using an AMP package, the Xdebug extension may be already installed. Refer to the instructions specific for your package.
Integrate Xdebug with the PHP interpreter
Open the active php.ini file in the editor:
In the Settings/Preferences dialog (Ctrl+Alt+S), click PHP under Languages & Frameworks.
On the PHP reference page that opens, click next to the CLI Interpreter field.
In the CLI Interpreters dialog that opens, the Configuration file read-only field shows the path to the active php.ini file. Click Open in Editor.
To disable the Zend Debugger and Zend Optimizer tools, which block Xdebug, remove or comment out the following lines in the php.ini file:
zend_extension=<path_to_zend_debugger> zend_extension=<path_to_zend_optimizer>To enable Xdebug, locate or create the
[xdebug]
section in the php.ini file and update it as follows:[xdebug] zend_extension="<path to xdebug extension>" xdebug.mode=debug xdebug.client_host=127.0.0.1 xdebug.client_port="<the port (9003 by default) to which Xdebug connects>"[xdebug] zend_extension="<path to xdebug extension>" xdebug.remote_enable=1 xdebug.remote_host=127.0.0.1 xdebug.remote_port="<the port (9000 by default) to which Xdebug connects>"To enable multi-user debugging via Xdebug proxies, locate the
xdebug.idekey
setting and assign it a value of your choice. This value will be used to register your IDE on Xdebug proxy servers.Save and close the php.ini file.
Verify Xdebug installation by doing any of the following:
In the command line, run the following command:
php --versionThe output should list Xdebug among the installed extensions:
Create a php file containing the following code:
<?php phpinfo();Open the file in the browser. The
phpinfo
output should contain the Xdebug section:
Configure Xdebug in IntelliJ IDEA
Press Ctrl+Alt+S to open the IDE settings and select
.Check the Xdebug installation associated with the selected PHP interpreter:
On the PHP page, choose the relevant PHP installation from the CLI Interpreter list and click next to the field. The list shows all the PHP installations available in IntelliJ IDEA, see Configuring Local PHP Interpreters and Configuring Remote PHP Interpreters.
The CLI Interpreters dialog that opens shows the following:
The version of the selected PHP installation.
The name and version of the debugging engine associated with the selected PHP installation (Xdebug or Zend Debugger). If no debugger is configured, IntelliJ IDEA shows the corresponding message:
Alternatively, open the Installation Wizard, paste the output of the
phpinfo()
, and click Analyze my phpinfo() output. Learn more about checking the Xdebug installation in Validate the Configuration of a Debugging Engine.Define the Xdebug behaviour. Click Debug under the PHP node. On the Debug page that opens, specify the following settings in the Xdebug area:
In the Debug port field, appoint the port through which the tool will communicate with IntelliJ IDEA.
This must be the same port number as specified in the php.ini file:
xdebug.client_port="<the port (9003 by default) to which Xdebug connects>"xdebug.remote_port="<the port (9000 by default) to which Xdebug connects>"By default, Xdebug 2 listens on port 9000. For Xdebug 3, the default port has changed from 9000 to 9003. You can specify several ports by separating them with a comma. By default, the Debug port value is set to 9001,9003 to have IntelliJ IDEA listen on both ports simultaneously.
To have IntelliJ IDEA accept any incoming connections from Xdebug engine through the port specified in the Debug port field, select the Can accept external connections checkbox.
Select the Force break at first line when no path mapping specified checkbox to have the debugger stop as soon as it reaches and opens a file that is not mapped to any file in the project on the Servers page. The debugger stops at the first line of this file and Examine/update variables shows the following error message: Cannot find a local copy of the file on server <path to the file on the server> and a link Click to set up mappings. Click the link to open the Resolve Path Mappings Problem dialog and map the problem file to its local copy.
When this checkbox cleared, the debugger does not stop upon reaching and opening an unmapped file, the file is just processed, and no error messages are displayed.
Select the Force break at first line when a script is outside the project checkbox to have the debugger stop at the first line as soon as it reaches and opens a file outside the current project. With this checkbox cleared, the debugger continues upon opening a file outside the current project.
In the External connections area, specify how you want IntelliJ IDEA to treat connections received from hosts and through ports that are not registered as deployment server configurations.
Ignore external connections through unregistered server configurations: Select this checkbox to have IntelliJ IDEA ignore connections received from hosts and through ports that are not registered as deployment server configurations. When this checkbox is selected, IntelliJ IDEA does not attempt to create a deployment server configuration automatically.
Break at first line in PHP scripts: Select this checkbox to have the debugger stop as soon as connection between it and IntelliJ IDEA is established (instead of running automatically until the first breakpoint is reached). Alternatively turn on the option from the main menu.
Max. simultaneous connections Use this spin box to limit the number of external connections that can be processed simultaneously.
Configure Xdebug for using in the On-Demand mode
IntelliJ IDEA supports the On-Demand mode, where you can disable Xdebug for your global PHP installation and have it enabled automatically on demand only when you are debugging your command-line scripts or when you need code coverage reports. This lets your command line scripts (including Composer and unit tests) run much faster.
Disable Xdebug for command-line scripts:
In the Settings/Preferences dialog (Ctrl+Alt+S), go to PHP under Languages & Frameworks.
From the PHP executable list, choose the relevant PHP interpreter and click next to it. In the CLI Interpreters dialog that opens, click the Open in Editor link next to the Configuration file: <path to php.ini> file. Close all the dialogs and switch to the tab where the php.ini file is opened.
In the php.ini file, find the
[xdebug]
section and comment the following line in it by adding;
in preposition:;[xdebug] ;zend_extension = "<path to xdebug extension>"Open the CLI Interpreters dialog and click next to the PHP executable field. IntelliJ IDEA informs you that debugger is not installed:
To enable IntelliJ IDEA to activate Xdebug when it is necessary, specify the path to it in the Debugger extension field, in the Additional area. Type the path manually or click and select the location in the dialog that opens.
Configure Xdebug for using in the Just-In-Time mode
IntelliJ IDEA supports the use of Xdebug in the Just-In-Time (JIT) mode so it is not attached to your code all the time but connects to IntelliJ IDEA only when an error occurs or an exception is thrown. Depending on the Xdebug version used, this operation mode is toggled through the following settings:
Xdebug 2 uses the xdebug .remote_mode setting, which has to be set to
jit
.Xdebug 3 uses the xdebug.start_upon_error setting, which has to be set to
yes
.
The mode is available both for debugging command-line scripts and for web server debugging.
Depending on whether you are going to debug command-line scripts or use a Web server, use one of the scenarios below.
Command-line scripts
For debugging command-line scripts, specify the custom -dxdebug.remote_mode=jit
(for Xdebug 2) or -dxdebug.start_upon_error=yes
(for Xdebug 3) directive as an additional configuration option:
Press Ctrl+Alt+S to open the IDE settings and select
.From the PHP executable list, choose the relevant PHP interpreter and click next to it.
In the CLI Interpreters dialog that opens, click next to the Configuration options field in the Additional area.
In the Configuration Options dialog that opens, click to add a new entry.
Type
xdebug.start_upon_error
in the Configuration directive field andyes
in the Value field.Type
xdebug.remote_mode
in the Configuration directive field andjit
in the Value field.When you click OK, you return to the CLI Interpreters dialog where the Configuration options field shows
-dxdebug.remote_mode=jit
(for Xdebug 2) or-dxdebug.start_upon_error=yes
(for Xdebug 3).
Web server debugging
From the main menu, choose
.In the Validate Remote Environment that opens, choose the Web server to validate the debugger on.
Choose Local Web Server or Shared Folder to check a debugger associated with a local Web server.
Path to Create Validation Script: In this field, specify the absolute path to the folder under the server document root where the validation script will be created. For Web servers of the type Inplace, the folder is under the project root.
The folder must be accessible through http.
URL to Validation Script: In this field, type the URL address of the folder where the validation script will be created. If the project root is mapped to a folder accessible through http, you can specify the project root or any other folder under it.
Choose Remote Web Server to check a debugger associated with a remote server.
Path to Create Validation Script: In this field, specify the absolute path to the folder under the server document root where the validation script will be created. The folder must be accessible through http.
Deployment Server: In this field, specify the server access configuration of the type Local Server or Remote Server to access the target environment. For details, see Configure synchronization with a Web server.
Choose a configuration from the list or click Browse in the Deployment dialog.
Click Validate to have IntelliJ IDEA create a validation script, deploy it to the target remote environment, and run it there.
Open the php.ini file which is reported as loaded and associated with Xdebug.
In the php.ini file, find the
[xdebug]
section.Change the value of the
xdebug.start_upon_error
from the defaultdefault
toyes
.Change the value of the
xdebug.remote_mode
from the defaultreq
tojit
.
See also Just-In-Time debugging and PHP Exception Breakpoints with PhpStorm and Xdebug
Configure Xdebug running in a Docker container
To configure Xdebug running in a Docker container, provide the Xdebug-specific parameters in the Dockerfile, for example:
In this example, we're modifying /usr/local/etc/php/conf.d/docker-php-ext-xdebug.ini providing the mode
and client_host
Xdebug parameters.
Note that the xdebug.client_host
value should be replaced with the IP address of the machine where IntelliJ IDEA is running, which is accessible from the Docker container. If you are using Docker for Windows or Docker for Mac, you can set xdebug.client_host
to host.docker.internal
, which automatically resolves to the internal address of the host, letting you easily connect to it from the container.
In this example, we're modifying /usr/local/etc/php/conf.d/docker-php-ext-xdebug.ini providing the remote_enable
and remote_host
Xdebug parameters.
Note that the xdebug.remote_host
value should be replaced with the IP address of the machine where IntelliJ IDEA is running, which is accessible from the Docker container. If you are using Docker for Windows or Docker for Mac, you can set xdebug.remote_host
to host.docker.internal
, which automatically resolves to the internal address of the host, letting you easily connect to it from the container.
Configure Xdebug running on a Vagrant instance
To configure Xdebug running on a Vagrant instance, connect to the Vagrant machine and provide the Xdebug-specific parameters in the php.ini file:
Note that the xdebug.client_host
value is 10.0.2.2
. This is the gateway used in the default Vagrant setup, which allows connecting from the instance to host where IntelliJ IDEA is running.
Note that the xdebug.remote_host
value is 10.0.2.2
. This is the gateway used in the default Vagrant setup, which allows connecting from the instance to host where IntelliJ IDEA is running.
Configure Xdebug running in a WSL instance
To configure Xdebug running in a WSL environment, connect to the WSL Linux installation and provide the Xdebug-specific parameters in the php.ini file:
Note that the xdebug.client_host
value has to be set to the IP address of the WSL host machine. To obtain it, run the following command inside the WSL Linux installation:
Note that the xdebug.remote_host
value has to be set to the IP address of the WSL host machine. To obtain it, run the following command inside the WSL Linux installation:
If you use Docker Compose inside a WSL environment, do the following to obtain the correct WSL host IP address.
Connect to the WSL Linux installation and set an environment variable for the IP address of the WSL host machine in a
.bashrc
or.zshrc
file.export IP=$(hostname -I)Pass this environment variable to the
extra_hosts
parameter for thephp
service in the docker-compose.yml file.services: php: extra_hosts: docker.for.wsl2.host.internal: ${IP}