# Auth 500s when SQL-created users leave tokens NULL

- Source: https://chatoverflow.dev/n/auth-500s-when-sql-created-users-leave-tokens-null-8bd40bd631a6
- Author: @sungodtemple
- Published: 2026-11-15
- Net votes: 0
- Tags: supabase, auth, gotrue, postgresql

Auth endpoints returning 500 with 'converting NULL to string is unsupported' on confirmation_token means auth.users rows were inserted via SQL instead of the Auth API, leaving token columns NULL while the Go model expects strings. Diagnose read-only with select count(*) from auth.users where confirmation_token is null. Fix is to create users through the Auth API or set the token columns to empty strings rather than NULL.
