Mappings between the project folders and the folders on the server should be done correctly in PhpStorm first for debugging to work. In this case, you can simply run the dbgp proxy on your NAT machine, configure xdebug.remote_host setting to the IP address of your NAT machine, and configure the IDEs to connect to the proxy running at :9001. Running a DBGp proxy also allows you to avoid NAT issues where (as seen from PHP+Xdebug on the server) all connections seem to come from the same IP (because your internal network is NATted). So, with DBGp proxy you can limit who can connect to the proxy, and you may have multiple developers debugging the same web server running behind a NATted firewall. Each developer has a separate debugging session running over this proxy, which makes it possible to do multi-user debugging of the same code on the same server. All developers in the team, in turn, then connect to that proxy. When a proxy is used, the PHP Xdebug extension no longer connects to PhpStorm directly, but instead connects to the DBGp proxy server. So this guide will take the longer way which doesn’t need an IF to start (or at least fewer IFs), that is by using Xdebug’s DBGp proxy. See those IFs? Personally, I don’t like IF in programming or in life. private development server), and if it’s not running behind a NATted firewall, and if you want this guide to end here. Sure if the web server is only accessible by the developers (e.g. “Er, wait a minute… Don’t you just use xdebug.remote_connect_back which has been introduced since Xdebug 2.1?" Xdebug.client_host=192.168.1.By Ray Naldo Multi-User Debugging in PhpStorm Using Xdebug and DBGp Proxy Photo by Philipp Katzenberger on Unsplash
If that still doesn’t work, you may have to manually add
zend_extension=/xdebug.output_dir = “/qm-api/storage/xdebug-profiles” xdebug.client_host=192.168.1.146 (Replace with your Windows IP) xdebug.client_port=9003 xdebug.cli_color=1 xdebug.start_with_request=trigger xdebug.log_level=3 xdebug.log=”/qm-api/storage/logs/xdebug.log” xdebug.idekey=PHPSTORM xdebug.discover_client_host=false xdebug.max_nesting_level=256 Here are my full Xdebug settings for example: zend_extension=YOUR_PATH_TO_xdebug.so xdebug.mode=debug xdebug.discover_client_host= false xdebug.client_host= YOUR_WINDOWS_IP_FROM_IP_CONFIG xdebug.client_port=9003 xdebug.start_with_request=trigger xdebug.idekey=PHPSTORM You can find your IP by typing ipconfig in a Powershell terminal. The important thing in the Xdebug settings is that you use the actual IP of the host computer in xdebug.client_host instead of 127.0.0.1.
0 kommentar(er)
