Problems with Edge Functions – no responses / gateway blocking (CORS/JWT)
edge functionsauthHello I have a critical issue with Edge Functions in my project
(Project ref: tucdbbfczjvxsdipzntx, region: eu-central-1).
Some requests from the browser never return a response. In Chrome DevTools → Network I see no response headers and “Provisional headers are shown”. No OPTIONS preflight appears. In Supabase Logs nothing is recorded, as if the request never reached the function.
From curl, the same function responds correctly with:
HTTP/2 401
{"code":401,"message":"Missing authorization header"}
So the gateway is reachable, but browser / SDK requests are blocked before runtime.
The “Verify JWT” toggle in Edge Function settings resets to ON after every deploy, even if I disable and save it.
Using supabase.functions.invoke() also fails: the request either hangs or returns 401, with no function logs.
As a control test, a simple SQL RPC (supabase.rpc) works every time, which proves auth, client, and network are fine. Only Edge Functions fail.
Could you please check:
if there is a known Edge issue in eu-central-1
if the gateway is dropping requests before runtime
why “Verify JWT” resets on deploy
This blocks my production payments flow.
(Project ref: tucdbbfczjvxsdipzntx, region: eu-central-1).
Some requests from the browser never return a response. In Chrome DevTools → Network I see no response headers and “Provisional headers are shown”. No OPTIONS preflight appears. In Supabase Logs nothing is recorded, as if the request never reached the function.
From curl, the same function responds correctly with:
HTTP/2 401
{"code":401,"message":"Missing authorization header"}
So the gateway is reachable, but browser / SDK requests are blocked before runtime.
The “Verify JWT” toggle in Edge Function settings resets to ON after every deploy, even if I disable and save it.
Using supabase.functions.invoke() also fails: the request either hangs or returns 401, with no function logs.
As a control test, a simple SQL RPC (supabase.rpc) works every time, which proves auth, client, and network are fine. Only Edge Functions fail.
Could you please check:
if there is a known Edge issue in eu-central-1
if the gateway is dropping requests before runtime
why “Verify JWT” resets on deploy
This blocks my production payments flow.
