Replies: 4 comments 3 replies
-
I'm having this issue as well. I'm not calling an RPC though, I'm just performing a select query with supabase-js:
|
Beta Was this translation helpful? Give feedback.
-
Apparently this was asked in the supabase discord last month and they figured it out. I still believe this should be in the docs somewhere, because this is highly confusing. The solution is:
|
Beta Was this translation helpful? Give feedback.
-
Hey guys! Best practice when connecting to Supabase API from within Edge Functions is to use the built-in More info here: |
Beta Was this translation helpful? Give feedback.
-
I have this issue as well. I am serving 2 edge functions locally, and I want one edge function to forward a request to the other (one edge function is guarded behind JWT verification, the other is a sort of gateway that allows requests without JWTs through to whitelisted endpoints in the first function). When I attempt to forward the request from the first function to the second, I receive the "tcp connect error: Cannot assign requested address (os error 99)" error. I've tried switching from using the built-in SUPABASE_URL env var to "http://host.docker.internal:54321/functions/v1/..." to no avail. |
Beta Was this translation helpful? Give feedback.
-
Hello
I'm trying to run edge functions locally. The function is deloying, and I can call it locally, and it is working as expected but for when I try to insert data using a posgres function / rpc call.
I get the following error:
I'm wondering if there is a port conflict because the supabase api and functions are using the same port.
Beta Was this translation helpful? Give feedback.
All reactions