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 think that the call back should be: [immagine] Configure GitHub login for Discourse Be sure to set the Callback URL to use the path /auth/github/callback at your site domain. e.g., http://discuss.example.com/auth/github/callback

I’ve done that but it’s still http in the url :confused: Btw, I’m not using web.ssl.template.yml as I thought there was no need if you are using something like nginix or haproxy on the front end (which handles the https side of things).

So you are terminating HTTPS at haproxy then right? And then sending HTTP to Discourse Docker?

Yes @cpradio This is in my haproxy config (when it matches the url of my first Discourse forum): backend discourse_docker server server2 127.0.0.1:8888 cookie A check cookie JSESSIONID prefix no cache And in my container: expose: “8888:80” # fwd host port 80 to container port 80 (htt…

[immagine] AstonJ: I don’t think this is the issue because I managed to log in via Twitter to Discourse ok. If you log in to your host and type dig github.com does it resolve? It’s not resolving anywhere that I can find. ; <<>> DiG 9.9.5-3ubuntu0.9-Ubuntu <<>> github.com ;; global options…

One thing you can try, while you debug further: Disable force_ssl

[immagine] AstonJ: I’m not sure why GH being down would affect our normal username/password login tho? Oops. Yes. I missed that part, yes, it would seem that local logins should still work. Anything that you need to do that involves a rebuild, though, will likely fail. If you do need to reb…

I’m having the same issue, affecting both SSO and /users/admin-login logins. I’m not sure what’s happening here. This is how things go: I hit / via HTTPS without any cookies. I am given a cookie like this: _forum_session=bVd; path=/; HttpOnly, and redirected to /session/sso. Makes sense! I hit /s…

[immagine] fefrei: My install is also behind an nginx proxy. And you use the socketed template?

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

Supporto Installazione

AstonJ (AstonJ) 21 Ottobre 2016, 6:23pm 21

I get:

I’m not sure why GH being down would affect our normal username/password login tho?

Argomento		Risposte	Visualizzazioni
Avatar, Site Logos, and Cert Errors Self-hosting unsupported-install	61	4068	Maggio 25, 2020
Mixed SSL since upgrade Self-hosting	14	736	Dicembre 30, 2022
Discourse lost the ability to login for all accounts Support	13	3760	Giugno 8, 2024
Login not possible (no SSO, no LDAP, etc.) Support	3	1631	Ottobre 25, 2016
Authentication not working after a recent update Support	3	1929	Ottobre 26, 2016

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

Argomenti correlati