# 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:** [2016年十月21日 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:** 11

<div class="post-metadata">

### Author: ![AstonJ](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/astonj/32/215041_2.png) [@AstonJ](https://meta.discourse.org/u/AstonJ)
#### Post date: [2016年十月21日 16:19 UTC](https://meta.discourse.org/t/twitter-github-and-normal-username-and-password-logins-not-working-after-upgrade/51854/11 "2016-10-21T16:19:10Z")

</div>

I set it to https earlier. But still, why would it affect normal username and password logins (which isn’t working either). Or Twitter?

I also just tried to rebuild one of the other forums… and that failed cos `Could not resolve host: github.com;` (which I guess is due to their current problems).

Can we switch this secure cookie update off via ACP or revert to an older version for the time being?

**Edit** : My set-up is detailed in this How To: [Set up Discourse on a server with existing Apache sites](https://meta.discourse.org/t/how-to-set-up-discourse-on-a-server-with-existing-apache-sites/30013)

---

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