I upgraded the forum last night and this morning several members have emailed saying they can’t register (everything appears to work but when redirected back to the forum they are still shown the log-in/sign-up and can’t post etc). I’ve tried using a Twitter log-in on one of our existing accounts a…

I don’t think this is the issue because I managed to log in via Twitter to Discourse ok.

And I managed to login with Github on Meta just now. This looks like something with the new secure cookie. Is your setup just standard docker? I think you are on multisite right? Is force_https on for you? EDIT: Your redirect URI is http on Github Login, somehow. Here on meta is correctly set to …

Still getting the same thing (changed github callback url to https://elixirforum.com ). I’m not using multisite, just multiple single containers. Yep, force_https is selected. I think it’s to do with the update : /

When logging with Github on Meta: https://github.com/login?client_id=redacted&return_to=%2Flogin%2Foauth%2Fauthorize%3Fclient_id%redacted%26redirect_uri%3Dhttps%253A%252F%252Fmeta.discourse.org%252Fauth%252Fgithub%252Fcallback%26response_type%3Dcode%26scope%3Duser%253Aemail%26state%redacted On Eli…

Yeah, the redirect Uri is plain http. This is the secure cookies change

https://meta.discourse.org/t/secure-cookie-flag/28058/33?u=falco We are adding necessary security on https enabled sites. It can break if https isn’t set properly.

Go to your GitHub oauth settings and change the redirect URL to be https.

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). Ca…

So it’s: Internet → Haproxy → Apache → Docker → Nginx → Unicorn When using something outside docker, I know it’s recommended make the inner nginx listen in a unix socket so stuff don’t break. However I don’t have much experience in your stack.

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

Product Support Self-hosting

AstonJ (AstonJ) 10월 21, 2016, 4:11오후 8

I just tried logging in with a normal username and password and that is not working either.

What is the secure cookies change and what do I need to do to fix it?

글		댓글	조회수
Avatar, Site Logos, and Cert Errors Self-hosting unsupported-install	61	6056	5월 25, 2020
Mixed SSL since upgrade Self-hosting	13	926	12월 30, 2022
Discourse lost the ability to login for all accounts Product Support	12	3990	10월 21, 2016
Login not possible (no SSO, no LDAP, etc.) Product Support	2	1753	10월 25, 2016
Authentication not working after a recent update Product Support	2	1986	10월 26, 2016

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

Related topics