Heroku SSL added but visiting domain still says connection is not private
<p>I use Heroku for deploying my app and I used GoDaddy to purchase my custom domain name and I purchased my SSL certificate from them. </p>

<p>Let's call my heroku hosted version of my application example-101.herokuapp.com
And let's call my custom domain I own mycustomdomain.com</p>

<p>I was trying to set up my GoDaddy purchased SSL certificate through heroku, and followed all of the steps here through step 7: 
<a href="http://www.joshwright.com/tips/setup-a-godaddy-ssl-certificate-on-heroku" rel="noreferrer">http://www.joshwright.com/tips/setup-a-godaddy-ssl-certificate-on-heroku</a></p>

<p>Everything appears to be set up well. When I look in my Heroku GUI, at my settings for example-101.herokuapp.com, under 'Custom Domains' it lists <strong>www.mycustomdomain.com</strong> and <strong>mycustomdomain.com</strong>, each with DNS target <strong>mycustomdomain.com.herokudns.com</strong> and <strong>www.mycustomdomain.com.herokudns.com</strong> respectively.</p>

<p>When I run in the terminal: </p>

<pre><code>curl -kvI https://www.mycustomdomain.com
</code></pre>

<p>the output says it "Connected", it "successfully set certificate verify locations", and after all the handshakes it says "SSL certificate verify ok."</p>

<p><strong>Now, here is where I'm afraid my problem may be.</strong></p>

<p>In GoDaddy, under my DNS Management for mycustomdomain.com, I followed heroku instructions by creating a new record as follows: 
Type: CNAME
Name: www
Value: example-101.herokuapp.com
TTL: 1 hour</p>

<p>But this was based on documentation that doesn't take into regard adding an SSL certificate.</p>

<p>When I run</p>

<pre><code>heroku certs
</code></pre>

<p>it gives me the following: 
Name: brachiosaurus-94028
Common Names: www.mycustomdomain.com, mycustomdomain.com
Trusted: True
Type: SNI</p>

<p><strong>Should I be referencing brachiosaurus-94028 anywhere?</strong></p>

<p>When I actually try to visit www.mycustomdomain.com in my browser, the error it reads is NET::ERR_CERT_COMMON_NAME_INVALID , and in the details, it says the Subject is  *.herokuapp.com
Is that the issue? That it's pointing to herokuapp.com when it should be pointing to herokussl.com or something of that nature?</p>

<p>If you have any insight on why this isn't working please let me know.</p>

<p>Also, I just set all of this up about an hour ago. Does it take a day or two before it it working properly and the browser recognizes the SSL certificate? Am I jumping the gun on asking for help?</p>