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 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.

No, it’s simply: Haproxy -> Apache sites Or for the Discourse forums: Haproxy -> Discourse Docker

Why is this an unsupported install @Falco ? It is a Docker install as normal - the only difference is Haproy on the front (as there is no other way to run ‘normal’ websites on the same server - or do you know what the supported method is of running normal sites on a server as well?). Also is there a…

Github is back online and it’s set to https: [imagem]

I think that the call back should be: [imagem] 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…

[imagem] 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: …

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

Suporte Instalação

Falco (Falco) Outubro 21, 2016, 5:10pm 16

I think that the call back should be:

1 curtida

Tópico		Respostas	Visualizações
Avatar, Site Logos, and Cert Errors Self-hosting unsupported-install	61	3945	25 de Maio de 2020
Mixed SSL since upgrade Self-hosting	14	682	30 de Dezembro de 2022
Discourse lost the ability to login for all accounts Support	13	3756	8 de Junho de 2024
Login not possible (no SSO, no LDAP, etc.) Support	3	1631	25 de Outubro de 2016
Authentication not working after a recent update Support	3	1914	26 de Outubro de 2016

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

Tópicos relacionados