Replies: 2 comments 3 replies
-
I'm affected by this issue as well. I'd like to provide some more insight about it. I'm running Supabase CLI from WSL2, Arch Linux. When I started the local instance (after initializing) and opened the studio, I could get access to everything but the API section. I've done no changes to the instance at all. Here's what the page looks like: Here are the console logs of the error:
Another point of concern is the button to submit a support request. It presents me with a nice form to write about my issue, but when I actually click on it, a huge error toast pops up on the screen, listing some raw HTML:
|
Beta Was this translation helpful? Give feedback.
-
Did you find a solution? |
Beta Was this translation helpful? Give feedback.
-
Hello! I want to ask why I couldn't access http://localhost:54323/project/default/api (Supabase studio API menu).
It try to call http://supabase_kong_service:8000/rest/v1/?apikey=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyAgCiAgICAicm9sZSI6ICJhbm9uIiwKICAgICJpc3MiOiAic3VwYWJhc2UtZGVtbyIsCiAgICAiaWF0IjogMTY0MTc2OTIwMCwKICAgICJleHAiOiAxNzk5NTM1NjAwCn0.dc_X5iR_VP_qT0zsiyj_I_OZ2T9FtRU2BBNWN8Bu4GE with no luck (500). Any ideas ? I want to see the json web token secret so I can do some jwt creation without sign in via supabase.
Beta Was this translation helpful? Give feedback.
All reactions