-
Notifications
You must be signed in to change notification settings - Fork 202
Open
Labels
bugSomething isn't workingSomething isn't working
Description
Bug report
when accessed realtime websocket gets 403 in kong
Describe the bug
In default config and deployment realtime functions end up with 403 in kong
for example:
172.30.0.5 - - [06/Nov/2024:22:01:41 +0000] "GET /realtime/v1/websocket?apikey=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyAgCiAgICAicm9sZSI6ICJhbm9uIiwKICAgICJpc3MiOiAic3VwYWJhc2UtZGVtbyIsCiAgICAiaWF0IjogMTY0MTc2OTIwMCwKICAgICJleHAiOiAxNzk5NTM1NjAwCn0.dc_X5iR_VP_qT0zsiyj_I_OZ2T9FtRU2BBNWN8Bu4GE&vsn=1.0.0 HTTP/1.1" 403 0 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/129.0.0.0 Safari/537.36"
Same config works with supabase docker example. Tried both with and without ingress.
omeroy and mattias-wiberg
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working