I\'m following the steps to enable remote debugging (https://developers.google.com/chrome/mobile/docs/debugging). When I reach step 4, Chrome for Desktop returns with \"This web
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 ^_^