Common issues and their solutions. Can't find what you're looking for? Check our FAQ or contact support.
3 issues
This usually means your connection string is incorrect or your database is not accessible.
Solutions
Verify your connection string format: postgresql://postgres:[PASSWORD]@db.[PROJECT-REF].supabase.co:5432/postgres
Check that your password doesn't contain special characters that need URL encoding
Ensure your Supabase project is active and not paused
Check network/firewall settings in Supabase Dashboard → Settings → Database
Try testing the connection directly with a PostgreSQL client
Example
postgresql://postgres:your-password@db.xxxxx.supabase.co:5432/postgresThe connection is timing out, which could indicate network issues or database unavailability.
Solutions
Check if your Supabase database is paused (free tier)
Verify your database is accessible from the internet
Check Supabase status page for outages
Try increasing connection timeout in settings
Ensure your IP is not blocked by Supabase firewall
The credentials provided are incorrect or the user doesn't have proper permissions.
Solutions
Double-check your password in the connection string
Reset your database password in Supabase Dashboard if needed
Ensure you're using the correct database user (usually "postgres")
Check that your user has necessary permissions
Verify connection string encoding (special characters)
3 issues
The sync failed because of incompatible schema changes between source and target.
Solutions
Review the schema comparison before syncing
Fix incompatible changes in your source database first
Use dry-run mode to preview changes safely
Check for data type mismatches
Ensure foreign key constraints are compatible
Large tables or network issues can cause slow syncs or timeouts.
Solutions
Sync large tables in smaller batches
Schedule syncs during off-peak hours
Check your network connection stability
Consider syncing only necessary tables
Increase timeout settings if available
Data might not be syncing due to RLS policies, permissions, or data conflicts.
Solutions
Check Row Level Security (RLS) policies on both databases
Verify user permissions for read/write operations
Review sync logs for specific error messages
Ensure source and target schemas match
Check for unique constraint violations
3 issues
The schemas are incompatible and cannot be safely synced.
Solutions
Review the validation report for specific conflicts
Modify source schema to match target requirements
Use schema sync feature to align schemas first
Manually fix incompatible changes
Consider using migration scripts for complex changes
A column exists in both databases but with different data types.
Solutions
Identify the mismatched columns in the comparison view
Update source database column types to match target
Or update target to match source (if safe)
Be careful with data loss when changing types
Test changes in a development environment first
The target database is missing tables or columns that exist in the source.
Solutions
Use schema sync to create missing tables/columns
Or manually create them in the target database
Verify you've selected all tables for sync
Check if tables are filtered out by sync settings
2 issues
Your database is still pausing despite keep-alive being enabled.
Solutions
Verify keep-alive is enabled for the connection
Check keep-alive frequency settings
Ensure connection is active and testable
Check Supabase free tier status and limits
Review keep-alive logs for errors
You're approaching your monthly usage limits for syncs or connections.
Solutions
Review your usage in the dashboard
Optimize sync frequency (don't sync unnecessarily)
Combine multiple syncs into fewer operations
Remove unused connections
Contact support if you need higher limits
Can't find a solution? Check our FAQ, read the documentation, or contact our support team.