# 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:** [April 3, 2017, 7:56am 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:** 6

<div class="post-metadata">

**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**Post date:** [April 3, 2017, 1:35pm UTC](https://meta.discourse.org/t/outgoing-invites-give-overdramatic-not-secure-connection-could-be-compromised-warning/60355/6 "2017-04-03T13:35:39Z")

</div>

To get HTTPS you just need to run discourse-setup again and provide an email address for let’s​ encrypt.

---

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