Hello everybody:

Here is my setup:

Workstation:

- Windows 11 25H2
- PhpEd Pro 21.0 (Build 21033)
- Debug Port 7870

Server:

- Windows Server 2022
- Apache 2.4.66 (x64)
- PHP 8.3.29 (x64_nts)
- Debug extension v.12.0.23
- PATH env. variable includes PHP path
- PHPRC env. variable point to the PHP ini
- OpenSSH Server (windows)
- php.ini


Code:

zend_extension=dbg-php-8.3.dll debugger.enabled=On debugger.profiler_enabled=On debugger.fail_silently=Off debugger.IPv6_enabled=On debugger.JIT.enabled=Off debugger.hosts_allow=locahost 127.0.0.1 [::1] debugger.hosts_deny=ALL debugger.ports=7869/10

I can verify that I can SSH and SFTP to the server from the workstation.

I added these items to the IDE accounts:
- SSH terminal
- SSH tunnel
- SFTP file transfer

I verify them that they work independent inside the IDE. I create a project for remote debugging with local files sync with the remote server. Debugging HTTP works without problem. However when I try to debug a CLI, it opens a terminal windows and a pop-up "Waiting for debug session" and writes 12 times on the prompt without executing

ending with one

Then it timeout and pop another one saying that "Failed to start debug session" and that the debug module is not installed and that I should run the Wizard.

Fine, I deleted the project and ran the wizard. Every prompt goes OK, confirms all the parts of the installation, even it's able to auto upload to the server the dbg-wizard.php. Then Until arrive the part to configure the CLI, when it tries to connect to the terminal get stuck. If I open the details window, I can see the same problem, it keeps writing over and over the . I have to cancel this test and proceed until I complete the project configuration.

Once again, the result is the same HTTP debug, no problem, CLI debug, the same problem as before. Open the terminal writes those 12 echo commands, not execution.

Looking at the documentation of the debugger, it says that the CLI debugger can be manually trigger by putting the DBGSESSID on the environment variables. So from the same prompt that is left without executing, erase all the command and execute this 2 lines.



It works without problem. Of course, I could keep doing this, but that is slow, locating the file path on the remote server and execute on the terminal that has the debugging environment. At this point, I would rather to run my own SSH from a Windows Terminal as that is more capable for auto complete, ANSI codes and keys than the terminal build-in the IDE. The only advantage was that you could select the script to debug on the IDE and auto-locate the file and start debugging.

Does anybody has the same problem? Does anybody knows how to fix this? Or should this be considered a bug?

Thanks