I’ll take a quick look and see if there’s anything going on.
EDIT:
I tried a whole bunch of times, and on the VERY FIRST it failed with bad gateway. Then every single time it worked, both in incognito and in my normal browser.
Haven’t been able to make it fail again.
I do see these in the logs and I’m wondering if they have anything to do with it, but I doubt it. Still, it’s noise.
ActionController::RoutingError (No route matches [HEAD] "/auth/yahoo")
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/middleware/debug_exceptions.rb:63:in `call'
{"method":"HEAD","path":"/404","format":"html","controller":"ExceptionsController","action":"not_found","status":404,"duration":15.89,"view":0.16,"db":4.64,"params":"","database":"default","@timestamp":"2017-11-14T16:25:15.404Z","@version":"1","message":"[404] HEAD /404 (ExceptionsController#not_found)"}
Also, I’m seeing this in many places:
2017/11/14 08:40:21 [error] 10747#10747: *932261555 upstream sent too big header while reading response header from upstream, client: [proxy], server: *.discourse.org, request: "GET /auth/yahoo HTTP/2.0", upstream: "http://[internal-server]:444/auth/yahoo", host: "try.discourse.org", referrer: "https://try.discourse.org/t/testing-a-topic/892"
2017/11/14 05:43:31 [error] 2021#2021: *760816468 upstream sent too big header while reading response header from upstream, client: [proxy], server: community.[customer].com, request: "GET /auth/yahoo HTTP/2.0", upstream: "http://[internal-server]:444/auth/yahoo", host: "community.[customer].com", referrer: "https://community.[customer].com/c/tutorials"
I don’t have a smoking gun - this could just be the “usual temperment of yahoo logins” but I’ll check.
EDIT again:
Visiting https://try.discourse.org/auth/yahoo while logged in was causing the 502 errors for a while, but now it’s not.