title: localhost and 192.168.x.x over HTTPS for a-frame webVR development and local testing
body: <p>I'm trying to develop a A-frame-based VR experience. </p>
  
  <p>I can test it on my mac via <code>http://localhost</code> but can't do the same using mobile phone or VR headset via <code>http://192.168.1.123</code>. </p>
  
  <p>The problem is that those browsers demand that the page is served over <code>HTTPS</code> rather than <code>HTTP</code>, otherwise it denies access to the device motion sensor, making testing impossible. </p>
  
  <p>Using the following instructions, I managed to successfully have my VR web page served over  with a valid certificate. </p>
  
  <ul>
  <li><a href="https://www.freecodecamp.org/news/how-to-get-https-working-on-your-local-development-environment-in-5-minutes-7af615770eec/" rel="nofollow noreferrer">https://www.freecodecamp.org/news/how-to-get-https-working-on-your-local-development-environment-in-5-minutes-7af615770eec/</a></li>
  <li><a href="https://github.com/mattdesl/budo/blob/master/docs/command-line-usage.md#ssl-and-https" rel="nofollow noreferrer">https://github.com/mattdesl/budo/blob/master/docs/command-line-usage.md#ssl-and-https</a></li>
  </ul>
  
  <p>But, that is not enough, mobile device and headset access the page over a local-wifi IP like <code>192.168.1.123</code> rather than localhost and the ssl certificate doesn't seem to work for those, even if i replace <code>localhost</code> by the correct IP when generating the domain key &amp; certificates. </p>
  
  <p>i guess each device browser would need to have its trusted store updated or something...</p>
  
  <p>Would be curious to know how people solved their problem in their a-frame local development and testing flow. </p>