Supabase Configuration Debug

🔍 Debugging JWT Error

This page will help identify issues with your Supabase configuration.

Loading...

Checking configuration...

Debug Results

Common Solutions:

Problem: Your JWT token is malformed or corrupted.

Solution:

Go to your Supabase dashboard
Navigate to Settings → API
Copy fresh tokens (anon public and service_role)
Replace in your .env file
Restart your development server

Valid JWT format: eyJ... (starts with eyJ and has 3 parts separated by dots)

Problem: Required environment variables are missing.

Solution:


# Required for self-hosted Supabase

SUPABASE_URL=http://localhost:54321

SUPABASE_ANON_KEY=eyJ...

SUPABASE_SERVICE_ROLE_KEY=eyJ...
 

# Optional for cloud storage

SUPABASE_CLOUD_URL=https://xyz.supabase.co

SUPABASE_CLOUD_ANON_KEY=eyJ...

SUPABASE_CLOUD_SERVICE_ROLE_KEY=eyJ...

Problem: Cannot connect to your Supabase database.

Solution:

Check if your self-hosted Supabase is running
Verify the URL is correct (usually http://localhost:54321)
Run the database schemas: paquetes_schema.sql and blog_schema.sql
Check if the paquetes table exists