# Outgoing invites give overdramatic "not secure connection, could be compromised" warning

**URL:** <https://meta.discourse.org/t/outgoing-invites-give-overdramatic-not-secure-connection-could-be-compromised-warning/60355>\
**Category:** Feature\
**Created:** [3. April 2017 um 07:56 UTC](https://meta.discourse.org/t/outgoing-invites-give-overdramatic-not-secure-connection-could-be-compromised-warning/60355 "2017-04-03T07:56:16Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![dylanh724](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/dylanh724/32/119642_2.png) [@dylanh724](https://meta.discourse.org/u/dylanh724)\
**Post date:** [3. April 2017 um 07:56 UTC](https://meta.discourse.org/t/outgoing-invites-give-overdramatic-not-secure-connection-could-be-compromised-warning/60355/1 "2017-04-03T07:56:16Z")

</div>

This _could_ be a browser warning, but it seems like it’s coming from Discourse:

 ![](https://global.discourse-cdn.com/meta/original/3X/2/e/2e4b3a3ac36cb503fc7df528cd1bfeaf7cf16b4a.jpg)

If this was from Discourse, how about a warning before you send out mass invites that they’ll receive a scary sketchy SSL warning with a recommendation to get SSL before inviting out?

We only launched our forum not long ago and were planning to get SSL in a few weeks. I would’ve definitely waited. It’s sort of an overdramatic message, as this applies to _any_ site without SSL (http).

**Even if it’s browser based then… should still show a warning that some browsers may do this**. However, just a heads up - this sucks after sending out 2300 invites from our mailing list ☹ don’t let others make my mistake.

SSL is great practice – i have it for all my sites except my forum because it’s newer and haven’t got around to it yet.

---

_[View the full topic](https://meta.discourse.org/t/outgoing-invites-give-overdramatic-not-secure-connection-could-be-compromised-warning/60355)._