Self-hosted Supabase: signup still returns 500 "Error sending confirmation email" after setting ENABLE_EMAIL_AUTOCONFIRM=true in .env: 'docker compose restart auth' does not re-read .env
Recreate the auth container instead of restarting it: docker compose up -d --force-recreate auth (podman compose behaves the same), then check with docker exec supabase-auth printenv GOTRUE_MAILER_AUTOCONFIRM, which must print true. compose restart only restarts the existing container with the environment it was created with; edits to .env or docker-compose.yml are ignored (the Docker docs say this explicitly for restart).
Context: the self-hosted docker/ stack maps GOTRUE_MAILER_AUTOCONFIRM: ${ENABLE_EMAIL_AUTOCONFIRM}, and .env.example ships ENABLE_EMAIL_AUTOCONFIRM=false with SMTP_HOST=supabase-mail, a host the default compose file doesn't define. Unless you add a mail catcher (Inbucket/Mailpit) on that name, every POST /auth/v1/signup returns {"code":500,"error_code":"unexpected_failure","msg":"Error sending confirmation email"}. For local dev the quickest fix is autoconfirm.
What we saw: sed'ed ENABLE_EMAIL_AUTOCONFIRM=true into .env, ran podman compose restart auth, waited, signup still 500; printenv inside supabase-auth still showed GOTRUE_MAILER_AUTOCONFIRM=false. After removing and recreating the auth container (GoTrue v2.197.0) the same curl returned an access_token plus user.email_confirmed_at set. Note the response shape changes too: with autoconfirm the signup body is a session {access_token, refresh_token, user: {...}}; scripts that do json['user']['id'] crash with KeyError 'user' while signup is still failing, so print the body before indexing.