|
|
 |
|
|
Troubleshooting php debugger communications: dbg and PhpED are installed on the same network or there is no SSH tunneling setup between their machines
This is the set of instructions to troubleshoot and fix the communications between dbg - php debugger and PhpED - PHP IDE.
These instructions apply to the situations when SSH is not used. The troubleshooting instructions for communications using SSH are here.
To make sure that the communication between dbg and PhpED's DbgListener are working properly, in case if dbg and PhpED are located on the same network or if there is no SSH tunneling setup between their machines:
- Make sure that DbgListener is running on PhpED machine - check that satellite dish icon is in system tray. If it not there start PhpED - it will start DbgListener.
- Login to server (the machine where dbg is installed and running)
- Open a console on this server
- Run telnet command like this: "telnet <client computerIP> 7869" where client computerIP is an IP address of your client computer, where PhpED is running and 7869 is port selected in the settings of DbgListener. If communications were working Ok you'd see black dot inside the white circle in DbgListener icon and something like "01.01.2004 11:11:14 <serverIP> client connected" in the DbgListener log window, right after you had ran telnet. If this doesn't happen - there is problem in communications between the debugger and PhpED, caused by the firewall or the router or both.
Note: opening outgoing TCP ports on the firewall may weaken your server security! If you use DBG debugger on a public web server (e.g. available through the Internet) please consider using SSH daemon for debugging. In this case you don't need 7869 port to be opened at all.
|
|
| |
|
PHP Debugger with SSH
