title: How to get https certificate working on local Laravel Homestead site
body: <p>I'm getting this problem:</p>
  <p><a href="https://i.stack.imgur.com/8VNn7.png" rel="noreferrer"><img src="https://i.stack.imgur.com/8VNn7.png" alt="enter image description here" /></a></p>
  <p>The error that I'm seeing in Windows 10 Chrome Version 65.0.3325.181 (Official Build) (64-bit) is:</p>
  <blockquote>
  <p>Your connection is not private</p>
  <p>Attackers might be trying to steal your
  information from ((mysite)) (for example, passwords,
  messages, or credit cards). Learn more NET::ERR_CERT_AUTHORITY_INVALID</p>
  <p>This page is not secure (broken HTTPS).</p>
  <p>Certificate - missing</p>
  <p>This
  site is missing a valid, trusted certificate
  (net::ERR_CERT_AUTHORITY_INVALID).</p>
  </blockquote>
  <p>Firefox Quantum 59.0.2 (64-bit) says:</p>
  <blockquote>
  <p>Your connection is not secure</p>
  <p>The owner of ((mysite)) has configured their website
  improperly. To protect your information from being stolen, Firefox has
  not connected to this website.</p>
  <p>Connection is Not Secure</p>
  <p>Could not verify this certificate because the
  issuer is unknown.</p>
  </blockquote>
  <p>I have already tried: <a href="https://stackoverflow.com/a/47755133/470749">https://stackoverflow.com/a/47755133/470749</a></p>
  <pre><code>vboxmanage --version
  5.2.6r120293
  
  vagrant -v
  Vagrant 2.0.2
  
  git branch
  * (HEAD detached at v7.3.0)
  
  vagrant box list
  laravel/homestead (virtualbox, 5.2.0)
  
  vagrant box update
  ==&gt; vboxHomestead: Checking for updates to 'laravel/homestead'
      vboxHomestead: Latest installed version: 5.2.0
      vboxHomestead: Version constraints: &gt;= 5.2.0
      vboxHomestead: Provider: virtualbox
  ==&gt; vboxHomestead: Box 'laravel/homestead' (v5.2.0) is running the latest version.
  </code></pre>
  <p>I wonder if this means that I'm not yet using <a href="https://github.com/laravel/homestead/releases/tag/v7.1.0" rel="noreferrer">release 7.1.0</a> (which has in its changelog &quot;sign SSL certificates with a custom root certificate&quot;), and I wonder if that's why I have this SSL HTTPS problem.</p>
  <p>What are the next steps I should try now to get the certificate working?</p>