Chrome remote debugging doesn't work with IP

You can setup an SSH tunnel in order to debug remotely. On the source machine execute:

ssh -L 0.0.0.0:9223:localhost:9222 localhost -N 

Then on the other machine point Chrome browser to http://source-machine-ip:9223

I don't think Chrome accepts connections from outside of localhost (for security reasons).I would suggest you have to build small proxy on the same host where Chrome is.

The following worked for me when running a Chrome remote debugging host on Windows 8.

1. Add an Inbound Rule to Windows Firewall
   • Search for "Windows Firewall" and select the "Windows Firewall" result
   • On the left of the "Windows Firewall" control panel window, click "Advanced Settings". This will open up "Windows Firewall with Advanced Security".
   • In the tree view on the left, click "Inbound Rules"
   • On the far right, click "New Rule..."
   • Select "Port" (Click Next)
   • Select TCP and set "Specific local ports" to 9222 (Click Next)
   • Select "Allow the connection" (Click Next)
   • Choose the profile access (Domain, Private, Public) to suit your needs (Click Next)
   • Give it a name like Chrome Remote Debugging (9222) (Click Finish)
2. Follow user3445047's instructions on port forwarding:

Run Chrome on the Windows host:

chrome.exe --remote-debugging-port=9222

Set up port forwarding on the Windows host:

Open up a cmd window. You must "Run as administrator".

Enter the following into the cmd window:

netshinterfaceportproxyadd v4tov4 listenport=9222 connectaddress=127.0.0.1

On the client, navigate to http://THE_HOST_IP_ADDRESS:9222 and you should be presented with a list of "Inspectable Pages".