title: Chrome remote debugging from another machine
body: <p>Chrome has a really awesome feature that allows you to open the dev tools from another browser or window. It works by starting chrome with this flag:</p>
  
  <pre><code>--remote-debugging-port=9222
  </code></pre>
  
  <p>Then from another window/browser you can go to <a href="http://localhost:9222" rel="noreferrer">http://localhost:9222</a> and open dev tools for any running tab in Chrome. For security reasons Chrome will not allow access from another machine by IP, lets say <a href="http://192.168.1.2:9222" rel="noreferrer">http://192.168.1.2:9222</a>.</p>
  
  <p>However there is an additional flag that indicates it opens this ability, here is what Chrome has to say for it:</p>
  
  <pre><code>--remote-debugging-address 
  </code></pre>
  
  <blockquote>
    <p>Use the given address instead of the default loopback for accepting
    remote debugging connections. Should be used together with
    --remote-debugging-port. Note that the remote debugging protocol does not perform any authentication, so exposing it too widely can be a
    security risk.</p>
  </blockquote>
  
  <p>Either it's not working or I have no idea how to format it. I have tried the following:</p>
  
  <pre><code>--remote-debugging-port=9222 --remote-debugging-address=http://192.168.1.2:9222
  --remote-debugging-port=9222 --remote-debugging-address=http://192.168.1.2
  --remote-debugging-port=9222 --remote-debugging-address=192.168.1.2:9222
  --remote-debugging-port=9222 --remote-debugging-address=192.168.1.3 //maybe thinking its supposed to be the IP of the remote machine
  </code></pre>
  
  <p>The target machine a Mac</p>