Google Chrome for Android Remote Debugging - "localhost:9222" Not Available

Question

I found that I had to have USB debugging enabled on Chrome and on my device.

1. Chrome for Mobile - Settings > Developer Tools > [x] Enable USB Web debugging
2. Device - Settings > Developer options > [x] USB debugging
3. Connect Device to Computer

4. Enable port forwarding on Computer

   C:\adb forward tcp:9222 localabstract:chrome_devtools_remote

5. Go to http://localhost:9222 in Chrome for Computer

Can you please provide the version of Chrome on Android you are using? Open "about:version" URL and please provide values of "Google Chrome" an "Application" fields.

And can you please check the following -- after you turn on USB Web debugging (step 2 of the doc), what this sequence of commands outputs to you:

adb root
adb shell cat /proc/net/unix | grep chrome_devtools_remote

(The idea is to check, if the remote debugging socket opens on the device after you turn on USB Web debugging)

Have you changed your localhost at all? If so then try 127.0.0.1:9222 instead of localhost:9222.

I had two really dumb problems preventing me from doing this correctly, maybe my experience will help.

1: The "adb forward..." from the most voted-up comment on the YouTube channel explaining how to do it contains a few weird characters (https://www.youtube.com/watch?feature=player_embedded&v=s4zpL4VBbuU). If, like me, you pasted it in cmd without double-checking, the server will start without an error, but the service won't work properly. Make sure you're using this line with your path to adb

adb forward tcp:9222 localabstract:chrome_devtools_remote

2: ESET NOD32 Antivirus has this thing called HIPS (Host-Based Intrusion Prevention System), and it doesn't like you messing around with localhost:####

http://kb.eset.com/esetkb/index?page=content&id=SOLN2950

Maybe your Antivirus software has something similar that can be deactivated?

Hope this helps someone ^_^