# Facebook login was flagged as non compliant by Facebook after change to Let's Encrypt certificate system

**URL:** <https://meta.discourse.org/t/facebook-login-was-flagged-as-non-compliant-by-facebook-after-change-to-lets-encrypt-certificate-system/207253>\
**Category:** Product Support\
**Created:** [October 27, 2021, 1:23pm UTC](https://meta.discourse.org/t/facebook-login-was-flagged-as-non-compliant-by-facebook-after-change-to-lets-encrypt-certificate-system/207253 "2021-10-27T13:23:09Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)\
**Post date:** [October 27, 2021, 2:04pm UTC](https://meta.discourse.org/t/facebook-login-was-flagged-as-non-compliant-by-facebook-after-change-to-lets-encrypt-certificate-system/207253/9 "2021-10-27T14:04:58Z")

</div>

It’s not really an “alias” but a redirect. And you need to properly configure a redirect, which includes having a certificate in place for the place the redirect lives.

For example, our partners at communiteq provide a service for that at [https://www.forcewww.com/](https://www.forcewww.com/)

---

_[View the full topic](https://meta.discourse.org/t/facebook-login-was-flagged-as-non-compliant-by-facebook-after-change-to-lets-encrypt-certificate-system/207253)._