# "Your connection is not private" ISSUE

**URL:** <https://community.letsencrypt.org/t/your-connection-is-not-private-issue/18031>\
**Category:** Help\
**Created:** [July 18, 2016, 5:59am UTC](https://community.letsencrypt.org/t/your-connection-is-not-private-issue/18031 "2016-07-18T05:59:22Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![aringheadrian](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/aringheadrian/32/8060_2.png) [@aringheadrian](https://community.letsencrypt.org/u/aringheadrian)\
**Post date:** [July 18, 2016, 5:59am UTC](https://community.letsencrypt.org/t/your-connection-is-not-private-issue/18031/1 "2016-07-18T05:59:22Z")

</div>

On Friday (15.07.2016) I installed a SSL Let’s Encrypt Certificate. All good until here. Starting from yesterday(17.07.2016), at random points of time I got only “Your connection is not private” security issue on every path of my website I accessed and for no reason, the certificate was valid. No change no nothing… and after a while it works again.

I really need help with it !  
I’ve tested my domain/hosting with: [https://www.ssllabs.com/ssltest/analyze.html?d=www.thejourney.ninja](https://www.ssllabs.com/ssltest/analyze.html?d=www.thejourney.ninja) and I get an A+. Can you help me with this one guys, please ?

Thank you !

More details below:

My domain is: www.thejourney.ninja

I ran this command: -

It produced this output: Your connection is not private (from time to time)

My operating system is (include version): MacOSX El Capitan

My web server is (include version): Apache 2.4.23

My hosting provider, if applicable, is: [speedhost.ro](http://speedhost.ro)

I can login to a root shell on my machine (yes or no, or I don’t know): -

I’m using a control panel to manage my site (no, or provide the name and version of the control panel): Yes, DirectAdmin

---

<div class="post-metadata">

**Author:** ![pfg](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/pfg/32/1924_2.png) [@pfg](https://community.letsencrypt.org/u/pfg)\
**Post date:** [July 18, 2016, 6:12am UTC](https://community.letsencrypt.org/t/your-connection-is-not-private-issue/18031/2 "2016-07-18T06:12:02Z")

</div>

There are some mixed content warnings on some subsites (for example, you link to an image via `http://www.thejourney.ninja/stars404.png` on the “Privacy Policy” page). This would get rid of the green lock or show a warning, depending on your browser.

Other than that, I don’t see any problems with your configuration.

---

<div class="post-metadata">

**Author:** ![aringheadrian](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/aringheadrian/32/8060_2.png) [@aringheadrian](https://community.letsencrypt.org/u/aringheadrian)\
**Post date:** [July 18, 2016, 6:26am UTC](https://community.letsencrypt.org/t/your-connection-is-not-private-issue/18031/3 "2016-07-18T06:26:53Z")

</div>

I just fixed that link with https:// instead of http://, but besides this only some times we get for all the website paths the your-connection-is-not-private ‘error’ and after a while it just works again. Don’t know how I can show this to you guys ☹

---

<div class="post-metadata">

**Author:** ![pfg](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/pfg/32/1924_2.png) [@pfg](https://community.letsencrypt.org/u/pfg)\
**Post date:** [July 18, 2016, 6:35am UTC](https://community.letsencrypt.org/t/your-connection-is-not-private-issue/18031/4 "2016-07-18T06:35:03Z")

</div>

What browser are you using? What does this error look like, and is there an option to show more error details?

---

<div class="post-metadata">

**Author:** ![aringheadrian](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/aringheadrian/32/8060_2.png) [@aringheadrian](https://community.letsencrypt.org/u/aringheadrian)\
**Post date:** [July 18, 2016, 7:19am UTC](https://community.letsencrypt.org/t/your-connection-is-not-private-issue/18031/5 "2016-07-18T07:19:24Z")

</div>

I mainly use Chrome, but when I get the error I get it on all: Mozilla, Safari even in Edge(sometimes) ☹  
The error looks like this:

“www.thejourney.ninja uses an invalid security certificate. The certificate is not trusted because it is self-signed. The certificate is only valid for localhost Error code: SEC\_ERROR\_UNKNOWN\_ISSUER”

 ![](https://global.discourse-cdn.com/letsencrypt/original/2X/b/b2cbd880bd2c220e22599d82d1b2409a30901048.png)

---

<div class="post-metadata">

**Author:** ![tialaramex](https://avatars.discourse-cdn.com/v4/letter/t/f08c70/32.png) [@tialaramex](https://community.letsencrypt.org/u/tialaramex)\
**Post date:** [July 18, 2016, 7:38am UTC](https://community.letsencrypt.org/t/your-connection-is-not-private-issue/18031/6 "2016-07-18T07:38:56Z")

</div>

When this happens you are being shown the wrong certificate, which means you’re not talking to the real www.thejourney.ninja and so the browser is protecting you.

It could be that there is some misconfiguration at Speedhost, which causes this. But it is more likely that some other system is trying to put itself between your web site and you, and this of course is exactly what the SSL system is trying to prevent from happening.

When this happens, there should be a way to see the presented (wrong) certificate, it might be a little different in each browser, I think in Firefox you can click Add Exception then View Certificate, and the “Issued To” and “Issued By” stuff is most relevant here, a screenshot of that, when this problem arises might help pin down the issue exactly.

- It could be that you have software installed on your Mac which does this, it might describe itself as “anti-virus” software or say that it protects against Malware. In this case you can usually re-configure the software to fix the problem

- It could be that your home or place of work has a proxy doing this to everyone on the network. If you did not agree to this then you can ask for it to no longer be used on your connections.

- It could be that a network provider, on their own or in co-operation with a nation state is interfering between you and the server where this system is running.

It can also help if you can find someone elsewhere on the Internet who sees the same problem, maybe a friend with a different ISP ? If it’s just happening to you, that suggests one of the top items from my list. Often the information on the wrong certificate that’s presented can help identify who made it and why. But if it’s just a goof at Speedhost it may not help, in that case you’d have to ask their support staff to investigate.

---

<div class="post-metadata">

**Author:** ![serverco](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/serverco/32/4251_2.png) [@serverco](https://community.letsencrypt.org/u/serverco)\
**Post date:** [July 18, 2016, 7:42am UTC](https://community.letsencrypt.org/t/your-connection-is-not-private-issue/18031/7 "2016-07-18T07:42:20Z")

</div>

You have 3 main nameservers for your domain ns1. ns2 and ns3. [dow-media.com](http://dow-media.com)

ns1 and ns3 provide the IP address 46.4.152.167

ns2 provides the IP address 88.198.25.154 - which doesn’t have the correct cert on it ( and probably isn’t where you want people to go anyway).

If you correct your DNS settings at all your nameservers it should correct your issue.

---

<div class="post-metadata">

**Author:** ![aringheadrian](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/aringheadrian/32/8060_2.png) [@aringheadrian](https://community.letsencrypt.org/u/aringheadrian)\
**Post date:** [July 18, 2016, 7:46am UTC](https://community.letsencrypt.org/t/your-connection-is-not-private-issue/18031/8 "2016-07-18T07:46:07Z")

</div>

I will check with my hosting company support and get back to you. Thank you!

---

<div class="post-metadata">

**Author:** ![aringheadrian](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/aringheadrian/32/8060_2.png) [@aringheadrian](https://community.letsencrypt.org/u/aringheadrian)\
**Post date:** [July 18, 2016, 8:07am UTC](https://community.letsencrypt.org/t/your-connection-is-not-private-issue/18031/9 "2016-07-18T08:07:28Z")

</div>

My hosting company support told me that they restarted the server and it should be ok now, but can you tell me how did you tested that the ns2 server is redirecting to the wrong ip, please ?

Thank you !

---

<div class="post-metadata">

**Author:** ![serverco](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/serverco/32/4251_2.png) [@serverco](https://community.letsencrypt.org/u/serverco)\
**Post date:** [July 18, 2016, 8:13am UTC](https://community.letsencrypt.org/t/your-connection-is-not-private-issue/18031/10 "2016-07-18T08:13:18Z")

</div>

I did it from linux with the command below ( which show’s it’s now OK )

```auto
$ dig www.thejourney.ninja @ns2.dow-media.com +short
46.4.152.167

```

You can also test your DNS with various online tools - such as [dnscheck.pingdom.com](http://dnscheck.pingdom.com) [intodns.com](http://intodns.com) or [viewdns.info](http://viewdns.info)

---

<div class="post-metadata">

**Author:** ![aringheadrian](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/aringheadrian/32/8060_2.png) [@aringheadrian](https://community.letsencrypt.org/u/aringheadrian)\
**Post date:** [July 18, 2016, 8:44am UTC](https://community.letsencrypt.org/t/your-connection-is-not-private-issue/18031/11 "2016-07-18T08:44:10Z")

</div>

Thx! I’ll see if I encounter the error/issue from now on and let you know if I do.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [August 17, 2016, 8:44am UTC](https://community.letsencrypt.org/t/your-connection-is-not-private-issue/18031/12 "2016-08-17T08:44:41Z")

</div>

Closed on August 17, 2016, 8:44am UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
