# Invalid Supabase Auth configuration after switching projects **URL:** \ **Category:** Ask us anything\ **Tags:** supabase\ **Created:** [June 24, 2024, 3:45pm UTC](https://community.weweb.io/t/invalid-supabase-auth-configuration-after-switching-projects/9303 "2024-06-24T15:45:59Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![cdev](https://avatars.discourse-cdn.com/v4/letter/c/8797f3/32.png) [@cdev](https://community.weweb.io/u/cdev)\ **Post date:** [June 24, 2024, 3:45pm UTC](https://community.weweb.io/t/invalid-supabase-auth-configuration-after-switching-projects/9303/1 "2024-06-24T15:45:59Z")
I am receiving an error when trying to switch projects from my production to staging instances in Supabase. I’ve tried copying the URL and both keys from my staging project on the API section of Supabase, and am receiving the error. It was working fine when I switched from production to staging last week. Any thoughts on what is going on? This is part of why switching projects in the plugins concerns me when going from Staging to Prod. ![supabasewweberror](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/1/1f15ef0005d812ab3ec085cb801de61df941b7f7.png) ---
**Author:** ![Broberto](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/broberto/32/5918_2.png) [@Broberto](https://community.weweb.io/u/Broberto)\ **Post date:** [June 24, 2024, 3:48pm UTC](https://community.weweb.io/t/invalid-supabase-auth-configuration-after-switching-projects/9303/2 "2024-06-24T15:48:03Z")
I’d make sure to “re-bind” the auth tables and make sure they’re present. It tends to throw errors otherwise. You also might want to check this out. > [@\[Supabase\] Switch between Production and Staging in one click](https://community.weweb.io/t/supabase-switch-between-production-and-staging-in-one-click/8972): > > Preface Since I kind of opened this discussion a few days ago, in this thread [[Chrome Extension] Supabase Live and Staging](https://community.weweb.io/t/chrome-extension-supabase-live-and-staging/8849) I actually found a really neat way of doing this, at least while WeWeb rolls out their own solution. This solution also doesn’t account for the part where WeWeb uses the Private - Secret keys to fetch things like fetching the users etc. What does this work on? Fetching the tables within your collections creating process a.k.a it can introspect your DB’s schema Changing th… This method doesn’t interfere with your project at all, so if it breaks/blocks something, you just turn it off. ---
**Author:** ![kanepaamauloa](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/kanepaamauloa/32/8944_2.png) [@kanepaamauloa](https://community.weweb.io/u/kanepaamauloa)\ **Post date:** [October 2, 2024, 5:41pm UTC](https://community.weweb.io/t/invalid-supabase-auth-configuration-after-switching-projects/9303/3 "2024-10-02T17:41:33Z")
What does “rebind” mean? How do you “rebind”? ---
**Author:** ![kanepaamauloa](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/kanepaamauloa/32/8944_2.png) [@kanepaamauloa](https://community.weweb.io/u/kanepaamauloa)\ **Post date:** [October 2, 2024, 6:01pm UTC](https://community.weweb.io/t/invalid-supabase-auth-configuration-after-switching-projects/9303/4 "2024-10-02T18:01:48Z")
I guess I figured it out. I re-entered the API key for the Supabase plugin. I also re-entered the API and Service keys for the Supabase Auth plugin. ---
**Author:** ![Broberto](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/broberto/32/5918_2.png) [@Broberto](https://community.weweb.io/u/Broberto)\ **Post date:** [October 2, 2024, 6:46pm UTC](https://community.weweb.io/t/invalid-supabase-auth-configuration-after-switching-projects/9303/5 "2024-10-02T18:46:44Z")
I think you might want to go to the tables as well and just hit the refresh button / save button and simply save. It should refresh “re-bind” the auth tables.