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 and I get the same thing. Anyone know how to troubleshoot this? There are no errors in the error log. The forum is at https://elixirforum.com Edit: Normal username and password logins are not working either.

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

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 any way I can roll back the discourse version to before these new secure cookies were introduced? (Without reverting to an older database).

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

I think that the call back should be: [imagen]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 (http) “2222:22” # fwd host port 2222 to container port 22 (ssh) Full file here: (I think all of this was set-up in this manner after the advice I got here on Meta.)

[imagen] 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: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 17584 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;github.com. IN A ;; Query time: 5003 msec ;; SERVER: 8.8.8.8#53(8.8.8.8) ;; WHEN: Fri Oct 21 14:13:00 EDT 2016 ;; MSG SIZE rcvd: 39 root@forum:/var/discourse# Right this minute 8.8.8.8 and 8.8.4.4 don’t find github and the ones of github’s DNS servers that I checked are unreachable. I’d wait a while before debugging this further Tech Email: hostmaster@github.com Name Server: ns2.p16.dynect.net Name Server: ns3.p16.dynect.net Name Server: ns4.p16.dynect.net Name Server: ns1.p16.dynect.net

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

Product Support Self-hosting

Falco (Falco) 21 Octubre, 2016 17:10 16

I think that the call back should be:

Tema		Respuestas	Vistas
Avatar, Site Logos, and Cert Errors Self-hosting unsupported-install	61	6347	25 Mayo 2020
Mixed SSL since upgrade Self-hosting	13	970	30 Diciembre 2022
Discourse lost the ability to login for all accounts Product Support	12	4027	21 Octubre 2016
Login not possible (no SSO, no LDAP, etc.) Product Support	2	1761	25 Octubre 2016
Authentication not working after a recent update Product Support	2	1994	26 Octubre 2016

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

Temas relacionados