© 2026 Hedgehog Software, LLC

TwitterGitHubDiscord
More
CommunitiesDocsAboutTermsPrivacy
Search
Star
Setup for Free
SupabaseS
Supabase•6mo ago•
91 replies
BackTo1964Brazil

Errors after migrating supabase db (Clerk auth integration issues)

I'm currently resuming a project I worked on a year ago. Since the project was inactive for over 90 days, I migrated the DB to a new project. However, after I migrated the DB, I'm receiving this error:
Error in SELECT operation: {
  code: 'PGRST301',
  details: null,
  hint: null,
  message: 'No suitable key or wrong key type'
}
Error in SELECT operation: {
  code: 'PGRST301',
  details: null,
  hint: null,
  message: 'No suitable key or wrong key type'
}


I'm not sure if this is an issue with clerk + supabase integration because I read that there's a new way to integrate clerk into supabase. I tried changing the RLS according to https://clerk.com/docs/integrations/databases/supabase but it still gives me the same error. Can someone please help me with this? I'm not sure what might be causing this error.
Integrations: Integrate Supabase with Clerk
Learn how to integrate Clerk into your Supabase application.
Integrations: Integrate Supabase with Clerk
Supabase banner
SupabaseJoin
Supabase gives you the tools, documentation, and community that makes managing databases, authentication, and backend infrastructure a lot less overwhelming.
45,816Members
Resources
Was this page helpful?

Similar Threads

Recent Announcements

Similar Threads

Supabase-Clerk Integration JWT Expiry
SupabaseSSupabase / help-and-questions
2w ago
Clerk integration with supabase storage
SupabaseSSupabase / help-and-questions
2mo ago
Clerk/Supabase React-native Integration
SupabaseSSupabase / help-and-questions
8mo ago
Auth errors and db errors
SupabaseSSupabase / help-and-questions
3mo ago
Next page