Invoke an Edge Function shows: Error while requesting the supabase project

Hello,

I have self-hosted Supabase and i have succesfully added Supabase Data and Auth Pluggin. As you can see in picture it reeds profiles table:

Problem appear when i try to Invoke and Edge Function, in fact when i need to select Function from drop down. There is no function and when i hit refresh button next to drop down it gives error:

”Error while requesting the supabase project.”

Слика од екранот 2025-12-16 121516

The Supabase auth plugin work ok for everything that i tested: SignUp, Loggin, Reset password, Update metadata…

Anybody help with Invoke and Edge Funciton?

Thanks

Hi Zoran, I don’t know much about self hosted supabase, so I asked an AI to help with this answer.

Answer

The most likely issue is that the WeWeb Supabase plugin cannot access the self‑hosted Supabase project metadata (where Edge Functions are listed), even though basic Data/Auth calls work.

Likely root causes

  • Incorrect or incomplete Supabase project URL for self‑hosted setup
    WeWeb’s Supabase plugin expects a valid project URL (the SUPABASE_URL / API URL) that exposes the standard management endpoints used to list Edge Functions. If the user pointed to a different domain (e.g. only the REST endpoint, a proxy, or wrong port), table reads can still work but the “list functions” request can fail with “Error while requesting the supabase project.”
  • Missing service role key or wrong key type in plugin settings
    Listing Edge Functions often requires higher privileges than regular client operations. If the user configured only an anon/public key, the plugin may be able to query tables but fail when calling the admin endpoint to retrieve functions, leading to that specific error when refreshing the dropdown.
  • CORS / network access from WeWeb to the self‑hosted instance
    For self‑hosted Supabase, CORS, firewall, or reverse‑proxy rules may allow standard REST calls but block or misroute the edge‑functions or management path that WeWeb uses to fetch available functions. This would manifest exactly as “no functions in dropdown + error while requesting the supabase project” while Auth still works.
  • Functions deployed to the wrong project or non‑HTTP edge functions
    If the user deployed functions to another Supabase instance or did not deploy HTTP‑accessible Edge Functions on that specific project, the plugin’s request can succeed in structure but return nothing or error, again preventing the dropdown from listing any function.

I hope this guides you in the right direction

Hi Agustin,

Thanks for the answer. Supabase data source is reading data from my self-hosted Supabase, so connection is ok. However i was able to call my Edge Function with Rest API Request. If somebody need this here it is:

You need to only add Api link to your Edge Function and Heared with Key: Authorization and Bind Value to:

Hope this will help somebody.

Now i need to find out why my function is not working 100%. It write to public.profiles ok but do not Ban/Delete user.

2 Likes

It would be nice to make the field bindable, or make it a text field instead of select for people who don’t want to connect their Supabase account for some reason - e.g. in this case self-hosting, or something else like lack of trust.

1 Like

Yes. That will be excelent