Spectrum: Signup at spectrum.chat fails.

[rhalff]

When I try to register with github the process succeeds, but then brings me back to the frontpage without being logged in. (Sign In is still shown)

When I try to register again it says previously logged in with github at the github button.

When I then try to register with twitter the auth/twitter/callback shows:
Ooops, something went wrong! Our engineers have been altered and will fix this asap.

Going back to sign in it now shows Previously signed in with twitter.

When I try to login with google it gives a google api key error.

Facebook seems to succeed but also just brings me back to the login page.

[mxstbr]

That's very very weird. Which browser are you using? I don't think we touched that code at all recently

[mxstbr]

The only log that looks even remotely related was this one 34 minutes ago:

04/03 01:00 PM (34m)

Error: Failed to find request token in session
    at SessionStore.get (/home/nowuser/src/node_modules/passport-oauth1/lib/requesttoken/session.js:13:44)
    at Strategy.OAuthStrategy.authenticate (/home/nowuser/src/node_modules/passport-oauth1/lib/strategy.js:214:33)
    at Strategy.authenticate (/home/nowuser/src/node_modules/passport-twitter/lib/strategy.js:87:40)
    at attempt (/home/nowuser/src/node_modules/passport/lib/middleware/authenticate.js:348:16)
    at authenticate (/home/nowuser/src/node_modules/passport/lib/middleware/authenticate.js:349:7)
    at Layer.handle [as handle_request] (/home/nowuser/src/node_modules/express/lib/router/layer.js:95:5)
    at next (/home/nowuser/src/node_modules/express/lib/router/route.js:137:13)
    at Route.dispatch (/home/nowuser/src/node_modules/express/lib/router/route.js:112:3)
    at Layer.handle [as handle_request] (/home/nowuser/src/node_modules/express/lib/router/layer.js:95:5)
    at /home/nowuser/src/node_modules/express/lib/router/index.js:281:22
    at Function.process_params (/home/nowuser/src/node_modules/express/lib/router/index.js:335:12)
    at next (/home/nowuser/src/node_modules/express/lib/router/index.js:275:10)
    at Function.handle (/home/nowuser/src/node_modules/express/lib/router/index.js:174:3)
    at router (/home/nowuser/src/node_modules/express/lib/router/index.js:47:12)
    at Layer.handle [as handle_request] (/home/nowuser/src/node_modules/express/lib/router/layer.js:95:5)
    at trim_prefix (/home/nowuser/src/node_modules/express/lib/router/index.js:317:13)
    at /home/nowuser/src/node_modules/express/lib/router/index.js:284:7
    at Function.process_params (/home/nowuser/src/node_modules/express/lib/router/index.js:335:12)
    at next (/home/nowuser/src/node_modules/express/lib/router/index.js:275:10)
    at Function.handle (/home/nowuser/src/node_modules/express/lib/router/index.js:174:3)
    at router (/home/nowuser/src/node_modules/express/lib/router/index.js:47:12)
    at Layer.handle [as handle_request] (/home/nowuser/src/node_modules/express/lib/router/layer.js:95:5)
    at trim_prefix (/home/nowuser/src/node_modules/express/lib/router/index.js:317:13)
    at /home/nowuser/src/node_modules/express/lib/router/index.js:284:7
    at Function.process_params (/home/nowuser/src/node_modules/express/lib/router/index.js:335:12)
    at Immediate.next (/home/nowuser/src/node_modules/express/lib/router/index.js:275:10)
    at Immediate._onImmediate (/home/nowuser/src/node_modules/express/lib/router/index.js:635:15)
    at runCallback (timers.js:796:20)
    at tryOnImmediate (timers.js:752:5)
    at processImmediate [as _immediateCallback] (timers.js:729:5)

That doesn't look like it was you though, given the timing and that all the login methods fail. 🤔 Do you see any cookie set in your browser at all when using either provider?

[kmelve]

I have the same problem. Tried both Github and Google, in multiple browsers including incognito mode. Here's a screen dump demonstrating the problem.

[mxstbr]

I can replicate this, actually. Digging further into this, sorry for the troubles!

[rhalff]

For what it's worth, Google sign-in gives this error:

[mxstbr]

Yeah we need to update those secrets apparently, /cc @brianlovin who has access to that.

I don't understand why all of these are just suddenly failing out of the blue. What's happening?

[mxstbr]

No update here, still not sure what's going on. I'm getting 0 helpful logs from anything.

[rhalff]

The first signup with github did give me a welcome email, so that part of the registration did work.

[mxstbr]

It appears like the websocket connection wipes out the session with a garbage cookie value? The authentication callback (at least for GitHub) works correctly, but then the websocket client connects and the server responds with a garbage, incorrect cookie value

[mxstbr]

(I think)

[mxstbr]

We're definitely getting new signups in our db, and it looks like they all come from different providers, so I'm really unsure what's happening here 😕 Does anybody have any clues?

[mxstbr]

I'm seeing some logs in Sentry from the Twitter passport strategy (https://sentry.io/space-program/spectrum/issues/491462221/), but that doesn't explain why y'all are unable to log in with GitHub either!

[kdichev]

I am experiencing the same issue.

What I have noticed that I received an email about a new github oauth registration even tho I am registered into Spectrum and have given access.(I think)

email came at 1:20 PM CET

[mxstbr]

I've been trying to fix this for two hours now, but can't seem to replicate it locally or fix it in production. No useful logs whatsoever.

I'm taking a break, trying to get a fresh mind on this. Sorry for the troubles folks 💜

[mxstbr]

This seems to be an issue with our deployment provider Zeit, who have started routing requests through Brussels then to San Francisco today, which is breaking signins for european users. If you're not in Europe speak now or hold your peace forever because that would indicate that it's a different issue!

We're investigating together, will keep you updated!

[mxstbr]

This was fixed by forcing the connection to always route through SFO—as soon as the DNS changes have propagated y'all should be able to log in again!

Super sorry about the troubles, I hope you stick with us 💜