Supabase Auth Users page fails on fresh Coolify deployment (pg-meta 500 errors)

Hi Team, I’m facing an issue with Supabase deployed via Coolify on a **brand-new project**, even without running any custom SQL. ### Environment - Coolify: latest (tested after fresh redeploy) - Supabase: deployed using Coolify Supabase resource (default settings) - Deployment: fresh VPS, no previous data - No custom schema, no RLS, no triggers ### Issue Supabase Studio loads, but: - **Authentication → Users page fails** - UI shows error similar to: `Invalid input: expected string, received undefined` - SQL editor queries also return errors ### Observations - `supabase-auth` logs show: - GoTrue migrations applied successfully - API started on port 9999 - `supabase-studio` starts correctly (Next.js ready) - **However, pg-meta requests consistently return 500 errors** From `supabase-kong` logs: POST /api/platform/pg-meta/default/query?key=users-count → 500 POST /api/platform/pg-meta/default/query?key=index-statuses → 500 These 500 errors occur immediately when opening **Auth → Users** in Studio. ### What I’ve tried - Multiple fresh Supabase deployments - No environment variable changes - Restarted all containers together - Issue reproduces consistently on a brand-new project ### Conclusion It appears `supabase-pg-meta` is failing or misconfigured in the Coolify Supabase stack, which breaks: - Auth Users page - SQL editor queries - Studio error handling (shows `formattedError undefined`) This does **not** appear to be caused by user SQL or RLS. Happy to provide full logs if needed. Thanks for looking into this.