# 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:** [Avril 3, 2017, 7: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:** 7

<div class="post-metadata">

**Author:** ![jomaxro](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jomaxro/32/126216_2.png) [@jomaxro](https://meta.discourse.org/u/jomaxro)\
**Post date:** [Avril 3, 2017, 3:24 UTC](https://meta.discourse.org/t/outgoing-invites-give-overdramatic-not-secure-connection-could-be-compromised-warning/60355/7 "2017-04-03T15:24:02Z")

</div>

> [@fefrei](#):
>
> Maybe we should take this as the last nail in the coffin to add a check to the admin dashboard as long as HTTPS isn’t enabled?

I can still think of at least one situation where this isn’t feasible - internal sites that aren’t visible outside the company network. Let’s Encrypt can’t work for those sites, and a constant dashboard warning would be quite obnoxious. There would need to be a way to disable it for situations like these if we add a check to the dashboard.

---

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