# Weweb 3.0 Supabase Plugin config completely breaks self-hosted Supabase **URL:** \ **Category:** Ask us anything\ **Created:** [February 14, 2025, 1:18am UTC](https://community.weweb.io/t/weweb-3-0-supabase-plugin-config-completely-breaks-self-hosted-supabase/16477 "2025-02-14T01:18:25Z")\ **Posts on this page:** 15\ **Page:** 1
**Author:** ![AgentD](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/agentd/32/6331_2.png) [@AgentD](https://community.weweb.io/u/AgentD)\ **Post date:** [February 14, 2025, 1:18am UTC](https://community.weweb.io/t/weweb-3-0-supabase-plugin-config-completely-breaks-self-hosted-supabase/16477/1 "2025-02-14T01:18:25Z")
Hi @luka and @Raphael and @Joyce congratulations on the launch BUT THERE IS A HUGE PROBLEM FOR ME. The Weweb 3.0 update now uses Supabase personal access tokens for configuring the data plugin. But that does not work for Self-hosted Supabase projects. Supabase doesn’t generate personal access tokens for self-hosted projects because that is supposed to be used for accessing cloud projects. See [this resolved issue](https://github.com/supabase/supabase/issues/13508). So right now I cannot create any new projects on Weweb forever and ever. And I DARE NOT edit my current projects’ backends or else, they will stop working, THIS IS A BIG BIG ISSUE AND THE WORST POSSIBLE TIME FOR ME TO HAVE THIS. All my apps need HIPAA compliance AND data residency. So I cannot use Supabase Cloud but I must self host it. And this weweb 3.0 has put a stumbling block for me. So I am just stuck with my 2 existing projects. PLEASE PLEASE help. I have already combed through the Supabase docs tonight franctically, there is no way to create Personal Access Tokens. So how else does one use the weweb data plugin? Can we have both the URL and Public Access Token option back in addition to this personal access token?? ---
**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:** [February 14, 2025, 6:27am UTC](https://community.weweb.io/t/weweb-3-0-supabase-plugin-config-completely-breaks-self-hosted-supabase/16477/2 "2025-02-14T06:27:21Z")
You should simply be able to add the postgres connection string and the other credentials manually via the advanced tab instead of doing the link, right? There is an advanced tab where you can fill this out. ---
**Author:** ![AgentD](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/agentd/32/6331_2.png) [@AgentD](https://community.weweb.io/u/AgentD)\ **Post date:** [February 14, 2025, 9:19am UTC](https://community.weweb.io/t/weweb-3-0-supabase-plugin-config-completely-breaks-self-hosted-supabase/16477/3 "2025-02-14T09:19:22Z")
Hey man. What’s up. Thanks for stopping by. I can’t see any “Advanced” tab in the data plug-in configuration page. It just shows a single input field requesting for “Personal Access token”. I raised it with customer support and they said they are aware of the issue and will “fix it”. Could you shed more light on where I could find this “advanced tab”. Is it the data plug-in page. Or elsewhere? ---
**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:** [February 14, 2025, 9:25am UTC](https://community.weweb.io/t/weweb-3-0-supabase-plugin-config-completely-breaks-self-hosted-supabase/16477/4 "2025-02-14T09:25:11Z")
I see now what you mean. Yeah, I think it should be non mandatory then. In the following step you can specify the connection string and all the old stuff like the URL etc. ---
**Author:** ![emdiemeric](https://avatars.discourse-cdn.com/v4/letter/e/e9bcb4/32.png) [@emdiemeric](https://community.weweb.io/u/emdiemeric)\ **Post date:** [February 14, 2025, 9:40am UTC](https://community.weweb.io/t/weweb-3-0-supabase-plugin-config-completely-breaks-self-hosted-supabase/16477/5 "2025-02-14T09:40:55Z")
My supabase connection has broken this morning as well. The Plugins freez when I open and click continue on connection. When I open the editor I get Error while requesting the supabase project. Anyone else have this problem? ---
**Author:** ![pauldev](https://avatars.discourse-cdn.com/v4/letter/p/b5ac83/32.png) [@pauldev](https://community.weweb.io/u/pauldev)\ **Post date:** [February 17, 2025, 7:01am UTC](https://community.weweb.io/t/weweb-3-0-supabase-plugin-config-completely-breaks-self-hosted-supabase/16477/6 "2025-02-17T07:01:41Z")
Thanks for reporting this on the board. I was thinking of making a new project using supabase installed in self-hosted. When I encountered this issue, I had to reconsider. Luckily, the original project did not use any connection to the 3rd party plugin that weweb created because I was worried this problem would happen. If WEWEB cannot fix it, I recommend using an open source backend that creates an API to connect instead, such as Motoradmin, which can connect directly to supabase, or use another backend, such as Nocobase, Budibase. > **[Motor Admin | Supabase](https://www.getmotoradmin.com/supabase)** > > Create custom admin panel for your Supabase project. Build CRUD interface and custom actions without code with a free and open-source tool. > **[NocoBase - Open source, self-hosted, lightweight no-code & low-code...](https://www.nocobase.com/)** > > NocoBase is a lightweight, extremely extensible open source no-code and low-code development platform. Quickly deploy to gain a private, controllable no-code solution! > **[Budibase - Internal tools made easy](https://budibase.com/)** > > Budibase is an open source low-code platform and the easiest way to build, automate, and ship internal tools. Check it out. ---
**Author:** ![Alexis](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/alexis/32/13248_2.png) [@Alexis](https://community.weweb.io/u/Alexis)\ **Post date:** [February 17, 2025, 10:54am UTC](https://community.weweb.io/t/weweb-3-0-supabase-plugin-config-completely-breaks-self-hosted-supabase/16477/7 "2025-02-17T10:54:23Z")
Hi everyone, it has been fixed before the end of the last week, we added another connection mode that let you bypass the oauth connection so you can connect any supabase project (local, selfhost,…) without having to connect your account. ![CleanShot 2025-02-17 at 11.50.25](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/6/6ae653719ea7ec2755f53886dd00e5db9d9e08b1.png) If you still have any issue please do not hesitate to report it ---
**Author:** ![pauldev](https://avatars.discourse-cdn.com/v4/letter/p/b5ac83/32.png) [@pauldev](https://community.weweb.io/u/pauldev)\ **Post date:** [February 18, 2025, 9:45am UTC](https://community.weweb.io/t/weweb-3-0-supabase-plugin-config-completely-breaks-self-hosted-supabase/16477/8 "2025-02-18T09:45:57Z")
This is cool, Thanks Alexis adn Weweb teams for fixed ---
**Author:** ![Philibert](https://avatars.discourse-cdn.com/v4/letter/p/ee7513/32.png) [@Philibert](https://community.weweb.io/u/Philibert)\ **Post date:** [February 19, 2025, 8:05pm UTC](https://community.weweb.io/t/weweb-3-0-supabase-plugin-config-completely-breaks-self-hosted-supabase/16477/9 "2025-02-19T20:05:03Z")
Hey ! URGENT PLEASE I have this uissue that happened out of nowhere (i did not make the new supabase configuration before) 1. Can fetch collections and RLS crash (happened already) But now even from a fresh session I have a big problem : can’t fetch any collections =\> i tried using the new supabase connect from weweb last update =\> does not work ! =\> error : “invalid configuration” or “failed to load pluggins” This is really ennoying and urgent please help ! Thanks ---
**Author:** ![Philibert](https://avatars.discourse-cdn.com/v4/letter/p/ee7513/32.png) [@Philibert](https://community.weweb.io/u/Philibert)\ **Post date:** [February 19, 2025, 8:14pm UTC](https://community.weweb.io/t/weweb-3-0-supabase-plugin-config-completely-breaks-self-hosted-supabase/16477/10 "2025-02-19T20:14:08Z")
![bug--_](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/f/f9182cd051684b572fb7cbda27797b0568aadf36.png) Stuck here for minutes and then “invalid configuration” error (red alert in left bottom) Sorry but it really blocks all my service and my custommers are complaining a lot !! The weidest is that all is green and checked … on both supabase and supabase Auth Pluggins Also, I can access my Tables in the Backend tab !! and my users in the Auth tab … So strange ! (on reload page i have “failed to load pluggin supabase …)” ---
**Author:** ![Yaj](https://avatars.discourse-cdn.com/v4/letter/y/eb8c5e/32.png) [@Yaj](https://community.weweb.io/u/Yaj)\ **Post date:** [February 19, 2025, 9:58pm UTC](https://community.weweb.io/t/weweb-3-0-supabase-plugin-config-completely-breaks-self-hosted-supabase/16477/11 "2025-02-19T21:58:25Z")
You should be able to still connect by doing what Alexis has shown a couple of replies above. It’s the same as the previous way to do it. ---
**Author:** ![Philibert](https://avatars.discourse-cdn.com/v4/letter/p/ee7513/32.png) [@Philibert](https://community.weweb.io/u/Philibert)\ **Post date:** [February 19, 2025, 10:31pm UTC](https://community.weweb.io/t/weweb-3-0-supabase-plugin-config-completely-breaks-self-hosted-supabase/16477/12 "2025-02-19T22:31:59Z")
Thanks for your answer ! However even the old method detailed by Alexis was not working anymore I just solved it by : =\> Upgraded Supabase to PRO that triggered a “Project Restart” **Anyway, could I get some help to make sure this does not happend anymore ? I have a ton of unhappy custommers I have to answer to 🙃** Not saying it’s weweb’s fault or whatever, it is just something that cannot happend anymore 😉 Some more info to unserstand the bug : instead of error fetching, it would fetch for a while then timeout ! Have a good evening ---
**Author:** ![Alexis](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/alexis/32/13248_2.png) [@Alexis](https://community.weweb.io/u/Alexis)\ **Post date:** [February 21, 2025, 1:27pm UTC](https://community.weweb.io/t/weweb-3-0-supabase-plugin-config-completely-breaks-self-hosted-supabase/16477/13 "2025-02-21T13:27:57Z")
If it was solved after upgrading I guess you reached a limit or your instance was put in pause maybe ? I don’t think it’s related to our integration if it was solved by a project restart If it happen again please open a ticket on [support.weweb.io](http://support.weweb.io) and we will take a look asap! ---
**Author:** ![Philibert](https://avatars.discourse-cdn.com/v4/letter/p/ee7513/32.png) [@Philibert](https://community.weweb.io/u/Philibert)\ **Post date:** [February 21, 2025, 2:14pm UTC](https://community.weweb.io/t/weweb-3-0-supabase-plugin-config-completely-breaks-self-hosted-supabase/16477/14 "2025-02-21T14:14:19Z")
Thanks for the answer. I think you are right and that it comes from Supabase However : the database size was already updated to PRO (a week ago) and what I actually upgraded later to resolve is the “Compute and Disk” that does not automatically upgrades on the free to Pro update ([Compute and Disk | Supabase Docs](https://supabase.com/docs/guides/platform/compute-and-disk)) In the link i provided, there is a “max DB size (recommended)” for the compute discs, that’s what may have gone wrong … If it is the case, It would be appreciated from Supabase to send an email in these situations or raise an error on their dashboard … I’ll contact them. Note that the bug happened at a “peak” of the app usage so … I hope it wont happen again and if it does I’ll definitely open a ticket. Thank you and have a good day ! ---
**Author:** ![Antiokh](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/antiokh/32/2794_2.png) [@Antiokh](https://community.weweb.io/u/Antiokh)\ **Post date:** [July 17, 2025, 4:02pm UTC](https://community.weweb.io/t/weweb-3-0-supabase-plugin-config-completely-breaks-self-hosted-supabase/16477/15 "2025-07-17T16:02:06Z")
I’m trying to connect a self-hosted Supabase. ![image](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/d/d7f2905257c7ab65967e85691b70b337d388e815.png) The “connect” button is disabled. Postman works (with apikey & Authorization: bearer).