Issue with logging in using GitHub authentication in Sanity.io

27 replies
Last updated: Jan 28, 2021
I use github to login to all sanity projects i work on - today No logins are working. Is this a known issue?Same behavior across different versions of sanity studio.
AI Update

I understand how frustrating it is when authentication suddenly stops working! When GitHub login isn't working across all your Sanity projects, here's what to check:

First, check the official Sanity status page: Based on the Sanity status page, all systems are currently operational, including the Authentication component which shows 100% uptime. There are no reported incidents affecting GitHub logins today.

This could be a GitHub OAuth issue: Since you're using GitHub as your login provider, the problem might be on GitHub's side rather than Sanity's. Check GitHub's status page to see if they're experiencing any OAuth or authentication issues.

Common troubleshooting steps:

  • Try clearing your browser cache and cookies, then attempt to log in again
  • Try a different browser or incognito/private mode to rule out browser-specific issues
  • Check if you can log into GitHub directly to ensure your GitHub account is working
  • If you have access to other login methods (Google, email), try those to see if it's specific to GitHub authentication

If it's affecting multiple projects and Studio versions: This strongly suggests it's either a platform-wide issue (though none is currently reported) or a GitHub OAuth problem rather than something specific to your setup.

Where to get help: If the status pages don't show any issues and you're still blocked:

Given that you mentioned this is happening across different Studio versions and all your projects, I'd recommend checking GitHub's status first, then reaching out to the Sanity Community Slack to see if others are experiencing similar issues.

I just logged out and was able to log back in without issue. When you log in are you just getting returned to the auth screen? If you’re in Chrome, I’ve had that happen on multiple services in the past (though always with G Suite auth). Part of the reason I switched to Firefox.
user A
Yup - just a redirect straight to the auth screen each time. Also I am on Firefox already 🙂
A fun note - I can log into teams using github just fine, just not individual studios.
Interesting. FWIW, I get that test cookie warning too (even when successfully logged in).
hm. Going to check out chrome - see if I get a different.Just cleared everything - ran through the github auth again and same behavior.
Hm, works fine in chrome. Odd - literally was loggin in and working yesterday 🙂
(i really dont want to use chrome)
What if you revoke your Firefox session in GitHub then log back in?
Oh good point. Let me try that
I have no idea how to do that 😅
You’ll have to go in Chrome to revoke the Firefox session, I think.
👍 Unfortunately no change
I will begrugingly use chrome today
Shoot.
Appreciate the help 🙂
No problem. Hope it works itself out soon.
An idea from
user P
- have you recently installed any browser plugins like Privacy Badger that might be interfering?
Thanks
user M
I have not added anything new - I do run strict tracking and private windows by default on firefox - so that probably has something to do with it.Whats odd is I have not changed my setup for over a year and its been running the same until today.
Would be interesting to see if less strict tracking allows you to login successfully, if that's within scope to try I mean.
Oh yea 100%. I will give that a shot here.Whats interesting to me is I can get into the teams portal with github auth just fine, but not studios.
user M
Issue resolved. I’ll just switch to standard mode when Im accessing sanity. Would be interested to know what changed between yesterday / today though. I recognize this is more of an edge case.
Oh workaround - I just do custom and enable only cookies 🙂
Great! Thanks for confirming. Regarding the teams portal vs. studios, I think that's because they're not 3rd-party cookies on the teams portal.
Glad you found that workaround too. Would be handy if you could set that on a site-level?
🙂 We'll still look into this issue to figure out why it changed. Will share any additional info with you but may take some time if so.
Of course - and got it, that makes sense.
This is 100% not a blocker, I was more interested to see if / what had changed.
Thanks for checking in / providing feedback
Thanks for checking in / providing feedback

Sanity – Build the way you think, not the way your CMS thinks

Sanity is the developer-first content operating system that gives you complete control. Schema-as-code, GROQ queries, and real-time APIs mean no more workarounds or waiting for deployments. Free to start, scale as you grow.

Was this answer helpful?