-
Notifications
You must be signed in to change notification settings - Fork 22
Unable to login on staging. #7438
Comments
My staging user reliably gets the above error message when trying to log in. I checked out that user's fields in Sequel Pro & my |
I also checked the logs and this error has occurred 10 times in production over the last week, so it's not necessarily a new bug... although weird to surface now. We haven't made any changes to Northstar or Phoenix's authentication implementation lately either. |
I just did a fresh build from the latest dev branch, and pulled down a copy of the current staging database and I still can't reproduce on my local. Not sure what else would be different. 😕 |
Confirmed that And just confirming I'm not crazy, the data for user 18 (me) in Will continue investigating this 👻 tomorrow. |
I'm now unable to reproduce this on staging (returning to the borked session above now works fine, and so does logging out/in). Never fear though, it's now happening to me and @chloealee on Thor. |
Not sure if this helps or not but I am seeing this issue on Thor now. Except it didn't show when I first logged in on Thor. Overview of what happened to me:
|
Interesting… thanks for the detailed write up @sbsmith86! |
And seeing those same field errors now on Thor for me and @chloealee: |
I was testing at the same time as @sbsmith86 (sorry I should have waited until you were done!) and flushed cache. Right when I did that, I got the error page and Thor broke. I'm not sure if this matters either but I flushed cache by going up to the home screen at the top left corner and pushed the button Flush all cache instead of |
Here's a Drupal.org thread discussing the |
And another Drupal StackExchange question with the same suggestion. For what it's worth, it looks like we're pinned to an alpha version. Let's try updating that? /cc @mirie for Drupal smarts |
INVESTIGATION
Current Behavior
It seems like people are unable to login on staging, and same has been reported on Thor as well. It's coming from this line, which checks if the current access token has expired (and if it has, then fetches a new one & updates the user's "last accessed" time in Northstar).
Desired Behavior
Logging in should work!
🕵️
The text was updated successfully, but these errors were encountered: