title: Using Chromium Remote Debugging from External Device
body: <p>Chrome can be run to support <a href="http://blog.chromium.org/2011/05/remote-debugging-with-chrome-developer.html" rel="noreferrer">remote debugging</a> by starting it via the command line with a prompt such as <code>chrome.exe --remote-debugging-port=9222 --user-data-dir=C:/foo</code>. This is often used <a href="https://developers.google.com/chrome-developer-tools/docs/remote-debugging" rel="noreferrer">to debug on android or iOs</a> using a Browser on a Desktop Device but I would like to debug chrome running on a desktop PC. from a "client browser" on the same machine one can call localhost:9222 and see the server browser, calling localhost:9222/json will result in a json representation of the tabs open in the "server browser". This works just fine.</p>
  
  <p>However, when I try to use another device in the same (wifi) network by calling [local IP]:9222 or [local IP]:9222/json (local IP is the IP of the server browser) I get a connection timeout. Is it possible to use remote debugging in such way? Are any other switches needed when starting the browser?</p>
  
  <p><strong>Edit</strong> I have found some use of forward tcp for the debugging of mobile devices, but there does <a href="http://peter.sh/experiments/chromium-command-line-switches/" rel="noreferrer">not seem to be such a switch for chrome</a>.</p>
  
  <p><strong>Edit 2</strong> This seems to be a bit of a duplicate of the questions <a href="https://stackoverflow.com/questions/12087762/remote-debugging-how-to-create-a-port-proxy">here</a> and <a href="https://stackoverflow.com/questions/6827310/chrome-remote-debugging-doesnt-work-with-ip/9269355#9269355">here</a> however, as of yet I have not gotten the solutions presented there to work.</p>
  
  <p>So, apparently this comes down to forwarding a port to localhost:9222. However, at least on windows machines I have no luck with SSH tunnels. Are there any other ways to forward on the machine?</p>