# Your connection is not private

**URL:** <https://forum.ghost.org/t/your-connection-is-not-private/44236>\
**Category:** Developer help\
**Created:** [January 18, 2024, 12:02pm UTC](https://forum.ghost.org/t/your-connection-is-not-private/44236 "2024-01-18T12:02:46Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![cassyblaise](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/cassyblaise/32/26300_2.png) [@cassyblaise](https://forum.ghost.org/u/cassyblaise)\
**Post date:** [January 18, 2024, 12:02pm UTC](https://forum.ghost.org/t/your-connection-is-not-private/44236/1 "2024-01-18T12:02:46Z")

</div>

Hey everyone, Please can someone help me out with error, I am using mailgun and everything was very well, but lately I starting this error, is a new user want to sign up they do experience this error also, and my users can not view their email in the browser, Please can anyone help out? Thanks

 ![Screenshot (35)](https://us1.discourse-cdn.com/flex015/uploads/ghost2/original/3X/c/0/c077b1c3f59093d57387d2be8e50f75a2db9f60e.png)

---

<div class="post-metadata">

**Author:** ![mjw](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/mjw/32/30781_2.png) [@mjw](https://forum.ghost.org/u/mjw)\
**Post date:** [January 18, 2024, 3:36pm UTC](https://forum.ghost.org/t/your-connection-is-not-private/44236/2 "2024-01-18T15:36:53Z")

</div>

Why are you attempting to connect to this address using HTTP? It’s not intended to be used this way; the subdomain is for Mailgun tracking only.

Typically, you’ll have MX records for the bare domain plus MX records for Mailgun, e.g., `mg.yourdomain.com`, and optionally a CNAME for tracking, e.g., `email.mg.yourdomain`.

It would seem that you have misconfigured Ghost if one of these is hyperlinked in an email. Therefore, please share your config and newsletter settings.

---

<div class="post-metadata">

**Author:** ![cassyblaise](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/cassyblaise/32/26300_2.png) [@cassyblaise](https://forum.ghost.org/u/cassyblaise)\
**Post date:** [January 18, 2024, 10:41pm UTC](https://forum.ghost.org/t/your-connection-is-not-private/44236/3 "2024-01-18T22:41:53Z")

</div>

(post deleted by author)

---

<div class="post-metadata">

**Author:** ![Cathy\_Sarisky](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/cathy_sarisky/32/25750_2.png) [@Cathy\_Sarisky](https://forum.ghost.org/u/Cathy_Sarisky)\
**Post date:** [January 18, 2024, 11:29pm UTC](https://forum.ghost.org/t/your-connection-is-not-private/44236/4 "2024-01-18T23:29:29Z")

</div>

Yikes! Those look like real credentials. You’ll need to change those – immediately!

---

<div class="post-metadata">

**Author:** ![cassyblaise](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/cassyblaise/32/26300_2.png) [@cassyblaise](https://forum.ghost.org/u/cassyblaise)\
**Post date:** [January 19, 2024, 5:31am UTC](https://forum.ghost.org/t/your-connection-is-not-private/44236/5 "2024-01-19T05:31:51Z")

</div>

No, the there are not real, I did change them before putting online

---

<div class="post-metadata">

**Author:** ![nehakakar](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/nehakakar/32/28483_2.png) [@nehakakar](https://forum.ghost.org/u/nehakakar)\
**Post date:** [January 19, 2024, 6:30am UTC](https://forum.ghost.org/t/your-connection-is-not-private/44236/6 "2024-01-19T06:30:49Z")

</div>

Hey cassyblaise, please follow this steps.  
Go to settings and click on privacy after clicking the privacy there will be tracking prevention there you’ll have to choose standard option, definitely your problem will solve.  
Thank you.

---

<div class="post-metadata">

**Author:** ![cassyblaise](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/cassyblaise/32/26300_2.png) [@cassyblaise](https://forum.ghost.org/u/cassyblaise)\
**Post date:** [January 19, 2024, 6:35am UTC](https://forum.ghost.org/t/your-connection-is-not-private/44236/7 "2024-01-19T06:35:25Z")

</div>

Hey nehakakar, please if I may understand you clearly, do you mean google chrome setting?

---

<div class="post-metadata">

**Author:** ![nehakakar](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/nehakakar/32/28483_2.png) [@nehakakar](https://forum.ghost.org/u/nehakakar)\
**Post date:** [January 19, 2024, 6:36am UTC](https://forum.ghost.org/t/your-connection-is-not-private/44236/8 "2024-01-19T06:36:54Z")

</div>

Ohh that is for edge browser, for chrome go to setting and click on privacy and security after that go to safe browsing then choose standard protection.

---

<div class="post-metadata">

**Author:** ![nehakakar](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/nehakakar/32/28483_2.png) [@nehakakar](https://forum.ghost.org/u/nehakakar)\
**Post date:** [January 19, 2024, 6:39am UTC](https://forum.ghost.org/t/your-connection-is-not-private/44236/9 "2024-01-19T06:39:56Z")

</div>

yes but follow second one

---

<div class="post-metadata">

**Author:** ![cassyblaise](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/cassyblaise/32/26300_2.png) [@cassyblaise](https://forum.ghost.org/u/cassyblaise)\
**Post date:** [January 19, 2024, 6:51am UTC](https://forum.ghost.org/t/your-connection-is-not-private/44236/10 "2024-01-19T06:51:00Z")

</div>

Thanks for your time and respond, I know this can be fix through the privacy at the browser, but how about my users and the people that are using the blog, not everyone will have the knowledge of fixing this error from their browser, some may just leave the site out of frustration and never visit it again.

---

<div class="post-metadata">

**Author:** ![nehakakar](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/nehakakar/32/28483_2.png) [@nehakakar](https://forum.ghost.org/u/nehakakar)\
**Post date:** [January 19, 2024, 6:58am UTC](https://forum.ghost.org/t/your-connection-is-not-private/44236/11 "2024-01-19T06:58:45Z")

</div>

I’m sorry but I was facing the same issue, so I suggest to you. Did I something wrong here, please answer me.

---

<div class="post-metadata">

**Author:** ![cassyblaise](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/cassyblaise/32/26300_2.png) [@cassyblaise](https://forum.ghost.org/u/cassyblaise)\
**Post date:** [January 19, 2024, 7:18am UTC](https://forum.ghost.org/t/your-connection-is-not-private/44236/12 "2024-01-19T07:18:38Z")

</div>

No, I did not said you did anything wrong. what am try to say is, it is not everyone that is using the website will have the will have the knowledge of fixing this error from their browser.  
Btw, I am not saying your answer is wrong.

---

<div class="post-metadata">

**Author:** ![nehakakar](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/nehakakar/32/28483_2.png) [@nehakakar](https://forum.ghost.org/u/nehakakar)\
**Post date:** [January 19, 2024, 7:25am UTC](https://forum.ghost.org/t/your-connection-is-not-private/44236/13 "2024-01-19T07:25:55Z")

</div>

Okay. I understood that.

---

<div class="post-metadata">

**Author:** ![mjw](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/mjw/32/30781_2.png) [@mjw](https://forum.ghost.org/u/mjw)\
**Post date:** [January 19, 2024, 3:33pm UTC](https://forum.ghost.org/t/your-connection-is-not-private/44236/14 "2024-01-19T15:33:09Z")

</div>

Your config isn’t set up correctly for using Mailgun for **transactional** email. Indeed, attempting to sign-up fails to send the magic link.

Moreover, this method is not used for sending **bulk** email, i.e., newsletters, which will utilize CNAME. Can you please share the newsletter config, and also explain how you landed on the [email.mg.merklepal.com](http://email.mg.merklepal.com) URL?

---

<div class="post-metadata">

**Author:** ![cassyblaise](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/cassyblaise/32/26300_2.png) [@cassyblaise](https://forum.ghost.org/u/cassyblaise)\
**Post date:** [January 20, 2024, 5:33am UTC](https://forum.ghost.org/t/your-connection-is-not-private/44236/15 "2024-01-20T05:33:26Z")

</div>

@mjw I have reached out to mailgun support, they have fix the errors for me, and everything is working fine now. Thanks a lot for your time, I truly appreciate it.

---

<div class="post-metadata">

**Author:** ![mjw](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/mjw/32/30781_2.png) [@mjw](https://forum.ghost.org/u/mjw)\
**Post date:** [January 20, 2024, 11:59am UTC](https://forum.ghost.org/t/your-connection-is-not-private/44236/16 "2024-01-20T11:59:32Z")

</div>

It would be really helpful if you shared the detail since the underlying cause and resolution isn’t evident.

---

<div class="post-metadata">

**Author:** ![cassyblaise](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/cassyblaise/32/26300_2.png) [@cassyblaise](https://forum.ghost.org/u/cassyblaise)\
**Post date:** [January 20, 2024, 3:45pm UTC](https://forum.ghost.org/t/your-connection-is-not-private/44236/17 "2024-01-20T15:45:06Z")

</div>

Ok, I honestly do not know how to explain this but I will try my best. I do not if the method I used in setting up the newsletter config is wrong or something but I was following this instructions from this YouTube channel( [https://www.youtube.com/watch?v=YnjYWhceepU](https://www.youtube.com/watch?v=YnjYWhceepU) ) and everything workout fine, but early this month I notice this error “Your connection is not private” I tried to fixed it but nothing workout, so that was when I reached out for help here in this forum and also the mailgun support team. and this was this reply I got from them:  
“Thank you for contacting Sinch Mailgun Support. I noticed that the Certificate was not up. I went ahead and manually generated the certificate for  
[email.mg.merklepal.com](http://email.mg.merklepal.com) and confirmed it is secure now.”

So, basically I think, the issue was SSL Certificate was not up or it has expired.

I am sorry for the long note, but I hope this will help out a bit, Thanks 🙏

---

<div class="post-metadata">

**Author:** ![cassyblaise](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/cassyblaise/32/26300_2.png) [@cassyblaise](https://forum.ghost.org/u/cassyblaise)\
**Post date:** [January 20, 2024, 3:48pm UTC](https://forum.ghost.org/t/your-connection-is-not-private/44236/18 "2024-01-20T15:48:51Z")

</div>

Btw @mjw Please, if you have a better solution on how to Set up the newsletter config, Please I don’t mind you can share it with us, Thanks.

---

<div class="post-metadata">

**Author:** ![mjw](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/mjw/32/30781_2.png) [@mjw](https://forum.ghost.org/u/mjw)\
**Post date:** [January 20, 2024, 3:54pm UTC](https://forum.ghost.org/t/your-connection-is-not-private/44236/19 "2024-01-20T15:54:31Z")

</div>

> [@cassyblaise](#):
>
> “Thank you for contacting Sinch Mailgun Support. I noticed that the Certificate was not up. I went ahead and manually generated the certificate for  
> [email.mg.merklepal.com](http://email.mg.merklepal.com) and confirmed it is secure now.”

I can see that the URL now returns an HTTP 404 error, and the certificate is valid. However, what isn’t clear is why you visited the link, and why it was an issue for you. The URL is for tracking, and this is achieved using a 1px image in the body of a newsletter email.

Moreover, I note that sign-up to your site still fails: Failed to send magic link email. As pointed out earlier, your transactional mail setup has errors.

---

<div class="post-metadata">

**Author:** ![cassyblaise](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/cassyblaise/32/26300_2.png) [@cassyblaise](https://forum.ghost.org/u/cassyblaise)\
**Post date:** [January 20, 2024, 4:44pm UTC](https://forum.ghost.org/t/your-connection-is-not-private/44236/20 "2024-01-20T16:44:49Z")

</div>

I did not visit the link per say, I emailed my the article from ghostcms, and once I click view online from my inbox it was redirected to my browser, that was when I notice the wrong.

[Next page](https://forum.ghost.org/t/your-connection-is-not-private/44236.md?page=2)
