# Twitter, Github and normal username and password logins not working after upgrade

**URL:** <https://meta.discourse.org/t/twitter-github-and-normal-username-and-password-logins-not-working-after-upgrade/51854>\
**Category:** Self-hosting\
**Tags:** unsupported-install\
**Created:** [21. Oktober 2016 um 12:58 UTC](https://meta.discourse.org/t/twitter-github-and-normal-username-and-password-logins-not-working-after-upgrade/51854 "2016-10-21T12:58:57Z")\
**Posts on this page:** 1\
**Showing post:** 32

<div class="post-metadata">

**Author:** ![fefrei](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/fefrei/32/119538_2.png) [@fefrei](https://meta.discourse.org/u/fefrei)\
**Post date:** [21. Oktober 2016 um 19:26 UTC](https://meta.discourse.org/t/twitter-github-and-normal-username-and-password-logins-not-working-after-upgrade/51854/32 "2016-10-21T19:26:20Z")

</div>

The former is in the #howto, the second… was the culprit 🎉

Now I get a **secure** `_t` cookie.

I still think this is a bug: If Discourse doesn’t see that the request came via HTTPS, it shouldn’t just drop the cookie entirely, but either _still_ deliver the `secure` flag (it would have worked in my case!), or deliver the cookie without it.  
(I prefer blindly delivering the `secure` flag. That feels intuitive, and there already is a HUGE warning that the site will break without proper HTTPS, so Discourse should just trust the user that HTTPS is handled, somewhere, period.)

---

_[View the full topic](https://meta.discourse.org/t/twitter-github-and-normal-username-and-password-logins-not-working-after-upgrade/51854)._