I don’t know what your setup is so I can’t really give your specific instructions but I can give the generic steps:
Start the proxy
Tell Komodo to connect to that proxy using Prefs > Debugger > Connection: I am running a debugger proxy… and Proxy Key. Looks like you used komodo
Configure your xdebug env to connect to the Proxy
Helpful additional info would be:
a screenshot of your Komodo debugger config
the IP of each machine
You can run pydbgpproxy wherever you want as long as you use the right IPs and Port numbers and those are all routable and not blocked by either a firewall or another process using those ports. eg. if you tell pydbgpproxy to listen for connections on port 9000 AND you tell Komodo to listen on port 9000 one will block the other depending on which process starts first.
I don’t know what this is. It’s not from our docs? Why are you using it? Can you give me a reference why you’re using it?
First thing I notice is that your remote server is configured to connect to 192.168.56.101:9000 but so is your -d option in the pydbgpproxy command. They are different machines so that configuration doesn’t make sense.
The PHP config should have the IP of the Windows machine. (my guess is this one is wrong).
The -d option for pydbgpproxy should be the IP of the PHP server.
Yes, it works with the “xdebug.remote_host=192.168.1.106” (on 192.168.56.106), and using pydbgpproxy -i 127.0.0.1:9001 -d 192.168.1.106:9000 (on 192.168.1.106).
The pydbgpproxy docs are only for itself. It assumes your debug process is properly configured which yours wasn’t. You wouldn’t have been able to debug with or without the proxy
Glad we got you sorted!
set PYTHONPATH=“C:\Program Files (x86)\ActiveState Komodo IDE 10\lib\support\dbgp\pythonlib;%PYTHONPATH%”
cd C:\Program Files (x86)\ActiveState Komodo IDE 10\lib\support\dbgp\bin
pydbgpproxy
I get this :
INFO: dbgp.proxy: starting proxy listeners. appid: 6904
INFO: dbgp.proxy: dbgp listener on 127.0.0.1:9000
INFO: dbgp.proxy: IDE listener on 127.0.0.1:9001
Then in Komodo :
a specific port : 9001 (because “IDE listener on 9001”)
debugger proxy :
127.0.0.1:9000
komodo
Listen for debug, then :
INFO: dbgp.proxy: connection from 127.0.0.1:52983 [<main.sessionProxy instance at 0x025EAF58>]
INFO: dbgp.proxy: ‘Closing connection, invalid protocol used’ <main.sessionProxy instance at 0x025EAF58>
No handlers could be found for logger “dbgp.server”
INFO: dbgp.proxy: session stopped
INFO: dbgp.proxy: connection from 127.0.0.1:52984 [<main.sessionProxy instance at 0x025F1058>]
INFO: dbgp.proxy: ‘Closing connection, invalid protocol used’ <main.sessionProxy instance at 0x025F1058>
INFO: dbgp.proxy: session stopped
INFO: dbgp.proxy: connection from 127.0.0.1:52985 [<main.sessionProxy instance at 0x025F10D0>]
INFO: dbgp.proxy: ‘Closing connection, invalid protocol used’ <main.sessionProxy instance at 0x025F10D0>
INFO: dbgp.proxy: session stopped
It would be extremely useful to have a video that shows how to make this work, with a windows host and a linux VM.
If I don’t need a proxy, how do I debug in komodo ?
As I said, local folder is synced to VM folder.
So, does “mapped urls” is the only way to debug in this case ? (btw, “mapped urls” debugging only works with port 9000 for me)
In which scenario a proxy would be used ? Is it with komodo using directly the remote file ?
Can you please clarify this :
“Proxy Listener Address: The interface IP address and port Komodo uses to listen for connections from the proxy. By default, the debugger proxy uses port 9000 to listen for remote debuggers and port 9001 to listen for connections from Komodo.” :
does 9000 corresponds to this : “Komodo should listen for debugging connection on a specific port: 9000”.
and 9001 to this : “I am running a debugger proxy and Komodo should use it : Proxy listener address : 127.0.0.1:9001” ?
Thanks!