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

Question

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

Answer 1

Try downloading the Chrome Browser for Android in your phone. And then navigate again in your Desktop to localhost:9222 Android Remote Debugging just works with the mobile Chrome browser. Some users think that the native Android browser is Chrome but it isn't.

Answer 2

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

Answer 3

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 ^_^

Answer 4

C:\adb forward tcp:9222 localabstract:chrome_devtools_remote

helped me to find the cause on my system. It was having multiple devices connected. After removing all the devices, and connected only one required device resolved the issue.

Answer 5

The remote debugging features requires a small check. The USB debugging features should be rather turned off and only the option for USB Debugging under chrome (android) settings should be checked.

Also, run the adb forward command twice(the complete command with specific arguments).

Answer 6

You no longer need to fuss with adb, downloads or command lines. With Chrome v41 (canary), I just plugged in the phone, pointed the browser to chrome://inspect, then hit the "inspect" link below my device, and the debug window opened and worked. (Enable USB debugging in the developer options on the phone)

I add that this worked first time, whereas my efforts with Chrome v39 plus the platform tools sdk, adb and the rest, had still not given fruit after 6 hours or so.