© 2026 Hedgehog Software, LLC

TwitterGitHubDiscord
More
CommunitiesDocsAboutTermsPrivacy
Search
Star
Setup for Free
SupabaseS
Supabase•5mo ago•
1 reply
orb.nexus

Different Supabase URL for client side and server side breaks auth

I'm having serious problems trying to run supabase self hosted in docker compose. supabase itself works great but the server side code sets an auth cookie with the wrong name, since its supabase hostname is obviously a service, whereas for client side (testing in Chrome) it is obviously localhost.
@supabase/ssr
@supabase/ssr
automatically sets a client side cookie called
sb-localhost-auth-token
sb-localhost-auth-token
but is tying to read a cookie called
sb-kong-auth-token
sb-kong-auth-token
on the server side. Is this truly not supported, ie do I need to patch the official auth client to use supabase in docker with client side testing?
Supabase banner
SupabaseJoin
Supabase gives you the tools, documentation, and community that makes managing databases, authentication, and backend infrastructure a lot less overwhelming.
45,816Members
Resources

Similar Threads

Was this page helpful?
Recent Announcements

Similar Threads

Server side auth via the supabase React client
SupabaseSSupabase / help-and-questions
4y ago
Is it possible to have both server side auth and client side auth nextjs + supabase
SupabaseSSupabase / help-and-questions
4mo ago
supabase.auth logging out server-side
SupabaseSSupabase / help-and-questions
4y ago
SvelteKit and Authentication—server- or client-side?
SupabaseSSupabase / help-and-questions
4y ago