FAILED_TO_CREATE_USER - when trying to signup user and password #1511

New Issue

GiteaMirror · 2026-03-13T08:44:25-05:00

GiteaMirror commented

2026-03-13 08:44:25 -05:00

Originally created by @AceCodePt on GitHub (Jul 17, 2025).

Is this suited for github?

Yes, this is suited for github

To Reproduce

import { Pool } from "pg";
import logger from "@logger";
import { env } from "node:process";

const pool = new Pool({
  host: env.DATABASE_HOST,
  port: env.DATABASE_PORT,
  database: env.DATABASE_NAME,
  user: env.DATABASE_USER,
  password: env.DATABASE_PASSWORD,
  ssl: env.DATABASE_SSL === "require",
  max: 20,
  idleTimeoutMillis: 30000,
  connectionTimeoutMillis: 2000,
});

Ran the following schema to my neon db

create table "user" ("id" text not null primary key, "name" text not null, "email" text not null unique, "emailVerified" boolean not null, "image" text, "createdAt" timestamp not null, "updatedAt" timestamp not null);

create table "session" ("id" text not null primary key, "expiresAt" timestamp not null, "token" text not null unique, "createdAt" timestamp not null, "updatedAt" timestamp not null, "ipAddress" text, "userAgent" text, "userId" text not null references "user" ("id"));

create table "account" ("id" text not null primary key, "accountId" text not null, "providerId" text not null, "userId" text not null references "user" ("id"), "accessToken" text, "refreshToken" text, "idToken" text, "accessTokenExpiresAt" timestamp, "refreshTokenExpiresAt" timestamp, "scope" text, "password" text, "createdAt" timestamp not null, "updatedAt" timestamp not null);

create table "verification" ("id" text not null primary key, "identifier" text not null, "value" text not null, "expiresAt" timestamp not null, "createdAt" timestamp, "updatedAt" timestamp);

I don't think it matters but I run it against AstroJS with Neon as my DB

Current vs. Expected behavior

Expect Should just sign up the user.

The result is:
{"code":"FAILED_TO_CREATE_USER","message":"Failed to create user","details":{"length":303,"name":"error","severity":"ERROR","code":"23502","detail":"Failing row contains (sf7h5SO7TQ6EeV6k6QdMBSD73sQL8keN, null, ace@ace.com, f, null, 2025-07-17 08:22:26.854, 2025-07-17 08:22:26.854).","schema":"public","table":"user","column":"name","file":"execMain.c","line":"1982","routine":"ExecConstraints"}}

What version of Better Auth are you using?

11.2.12

Provide environment information

- OS Linux ubuntu
- Framework AstroJS
- DB postgres (with Neon)

Which area(s) are affected? (Select all that apply)

Backend

Auth config (if applicable)

export const auth = betterAuth({
  emailAndPassword: { enabled: true, autoSignIn: true },
  rateLimit: { enabled: import.meta.env.PROD },
  database: pool,
  logger: {
    log(level, message, ...args) {
      logger[level](message, args);
    },
  },
  socialProviders: {
    google: {
      clientId: env.GOOGLE_CLIENT_ID as string,
      clientSecret: env.GOOGLE_CLIENT_SECRET as string,
    },
    apple: {
      clientId: env.APPLE_CLIENT_ID as string,
      clientSecret: env.APPLE_CLIENT_SECRET as string,
    },
  },
})

Additional context

It is probably an issue with how the schema was created and how it is actually saved in the DB.

Originally created by @AceCodePt on GitHub (Jul 17, 2025). ### Is this suited for github? - [x] Yes, this is suited for github ### To Reproduce ```ts import { Pool } from "pg"; import logger from "@logger"; import { env } from "node:process"; const pool = new Pool({ host: env.DATABASE_HOST, port: env.DATABASE_PORT, database: env.DATABASE_NAME, user: env.DATABASE_USER, password: env.DATABASE_PASSWORD, ssl: env.DATABASE_SSL === "require", max: 20, idleTimeoutMillis: 30000, connectionTimeoutMillis: 2000, }); ``` Ran the following schema to my neon db ```sql create table "user" ("id" text not null primary key, "name" text not null, "email" text not null unique, "emailVerified" boolean not null, "image" text, "createdAt" timestamp not null, "updatedAt" timestamp not null); create table "session" ("id" text not null primary key, "expiresAt" timestamp not null, "token" text not null unique, "createdAt" timestamp not null, "updatedAt" timestamp not null, "ipAddress" text, "userAgent" text, "userId" text not null references "user" ("id")); create table "account" ("id" text not null primary key, "accountId" text not null, "providerId" text not null, "userId" text not null references "user" ("id"), "accessToken" text, "refreshToken" text, "idToken" text, "accessTokenExpiresAt" timestamp, "refreshTokenExpiresAt" timestamp, "scope" text, "password" text, "createdAt" timestamp not null, "updatedAt" timestamp not null); create table "verification" ("id" text not null primary key, "identifier" text not null, "value" text not null, "expiresAt" timestamp not null, "createdAt" timestamp, "updatedAt" timestamp); ``` I don't think it matters but I run it against AstroJS with Neon as my DB ### Current vs. Expected behavior Expect Should just sign up the user. The result is: {"code":"FAILED_TO_CREATE_USER","message":"Failed to create user","details":{"length":303,"name":"error","severity":"ERROR","code":"23502","detail":"Failing row contains (sf7h5SO7TQ6EeV6k6QdMBSD73sQL8keN, null, ace@ace.com, f, null, 2025-07-17 08:22:26.854, 2025-07-17 08:22:26.854).","schema":"public","table":"user","column":"name","file":"execMain.c","line":"1982","routine":"ExecConstraints"}} ### What version of Better Auth are you using? 11.2.12 ### Provide environment information ```bash - OS Linux ubuntu - Framework AstroJS - DB postgres (with Neon) ``` ### Which area(s) are affected? (Select all that apply) Backend ### Auth config (if applicable) ```typescript export const auth = betterAuth({ emailAndPassword: { enabled: true, autoSignIn: true }, rateLimit: { enabled: import.meta.env.PROD }, database: pool, logger: { log(level, message, ...args) { logger[level](message, args); }, }, socialProviders: { google: { clientId: env.GOOGLE_CLIENT_ID as string, clientSecret: env.GOOGLE_CLIENT_SECRET as string, }, apple: { clientId: env.APPLE_CLIENT_ID as string, clientSecret: env.APPLE_CLIENT_SECRET as string, }, }, }) ``` ### Additional context It is probably an issue with how the schema was created and how it is actually saved in the DB.

GiteaMirror closed this issue

2026-03-13 08:44:25 -05:00

GiteaMirror commented

2026-03-13 08:44:26 -05:00

@dosubot[bot] commented on GitHub (Jul 17, 2025):

The error happens because the Better Auth signup flow requires a non-null name field, but your signup request doesn't provide one, and your schema marks name as NOT NULL. This is a known issue: the CLI-generated schema and the signup endpoint are out of sync—signup doesn't send a name, but the DB expects it, so you get a NOT NULL constraint violation (source, source).

You have two options:

Change your schema to make name nullable if you don't want to collect it:
```
alter table "user" alter column "name" drop not null;
```
Auto-fill the name field with a placeholder during signup if you don't collect it from users. For example, in your signup handler, add:
```
const name = req.body.name || "Anonymous";
// pass `name` to the signup/createUser call
```

This mismatch is fixed in upcoming releases, so upgrading to the latest beta may resolve it without manual workarounds (source). If you want to keep the NOT NULL constraint, make sure your signup payload always includes a name value.

To reply, just mention @dosu.

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

@dosubot[bot] commented on GitHub (Jul 17, 2025):  The error happens because the Better Auth signup flow requires a non-null `name` field, but your signup request doesn't provide one, and your schema marks `name` as NOT NULL. This is a known issue: the CLI-generated schema and the signup endpoint are out of sync—signup doesn't send a name, but the DB expects it, so you get a NOT NULL constraint violation ([source](https://github.com/better-auth/better-auth/issues/3394), [source](https://github.com/better-auth/better-auth/discussions/3222)). You have two options: 1. Change your schema to make `name` nullable if you don't want to collect it: ```sql alter table "user" alter column "name" drop not null; ``` 2. Auto-fill the `name` field with a placeholder during signup if you don't collect it from users. For example, in your signup handler, add: ```ts const name = req.body.name || "Anonymous"; // pass `name` to the signup/createUser call ``` This mismatch is fixed in upcoming releases, so upgrading to the latest beta may resolve it without manual workarounds ([source](https://github.com/better-auth/better-auth/issues/3394)). If you want to keep the NOT NULL constraint, make sure your signup payload always includes a `name` value.  *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- How did I do? [Good](https://app.dosu.dev/response-feedback/bba2869e-cfaa-42b7-95ab-d8b587723d89?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/bba2869e-cfaa-42b7-95ab-d8b587723d89?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/bba2869e-cfaa-42b7-95ab-d8b587723d89?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/bba2869e-cfaa-42b7-95ab-d8b587723d89?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/bba2869e-cfaa-42b7-95ab-d8b587723d89?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/bba2869e-cfaa-42b7-95ab-d8b587723d89?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/bba2869e-cfaa-42b7-95ab-d8b587723d89?feedback_type=other)  [![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot) [![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/better-auth/better-auth/issues/3421)

GiteaMirror commented

2026-03-13 08:44:27 -05:00

@AceCodePt commented on GitHub (Jul 17, 2025):

@dosu It generates the name as not null. Does it need to be migrated or generated after I've made the change?

@AceCodePt commented on GitHub (Jul 17, 2025): @dosu It generates the name as not null. Does it need to be migrated or generated after I've made the change?

GiteaMirror commented

2026-03-13 08:44:27 -05:00

@dosubot[bot] commented on GitHub (Jul 17, 2025):

Yes, after you change the schema to make the name column nullable, you need to run a migration (like ALTER TABLE) to update the actual database structure. Just regenerating the schema or code isn’t enough—the migration is what applies the change to your live database. There’s no Better Auth-specific migration tool, so you can use standard tools (like manual SQL or something like Alembic) for this step. Once the migration runs, the change will take effect and you shouldn’t see the NOT NULL error anymore.
Reference

To reply, just mention @dosu.

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

@dosubot[bot] commented on GitHub (Jul 17, 2025):  Yes, after you change the schema to make the name column nullable, you need to run a migration (like ALTER TABLE) to update the actual database structure. Just regenerating the schema or code isn’t enough—the migration is what applies the change to your live database. There’s no Better Auth-specific migration tool, so you can use standard tools (like manual SQL or something like Alembic) for this step. Once the migration runs, the change will take effect and you shouldn’t see the NOT NULL error anymore. [Reference](https://github.com/better-auth/better-auth/issues/3394)  *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- How did I do? [Good](https://app.dosu.dev/response-feedback/902b93bf-2b87-4241-a780-50fd12c60ec2?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/902b93bf-2b87-4241-a780-50fd12c60ec2?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/902b93bf-2b87-4241-a780-50fd12c60ec2?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/902b93bf-2b87-4241-a780-50fd12c60ec2?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/902b93bf-2b87-4241-a780-50fd12c60ec2?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/902b93bf-2b87-4241-a780-50fd12c60ec2?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/902b93bf-2b87-4241-a780-50fd12c60ec2?feedback_type=other)  [![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot) [![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/better-auth/better-auth/issues/3421)

GiteaMirror commented

2026-03-13 08:44:27 -05:00

@AceCodePt commented on GitHub (Jul 17, 2025):

@dosu It for some reason also regenerate the name back without the default '' (which is what I've decided to do)
Any reason for that?

@AceCodePt commented on GitHub (Jul 17, 2025): @dosu It for some reason also regenerate the name back without the default '' (which is what I've decided to do) Any reason for that?

GiteaMirror commented

2026-03-13 08:44:28 -05:00

@dosubot[bot] commented on GitHub (Jul 17, 2025):

That's because the schema generator in Better Auth always reflects its internal model and overwrites manual changes—so any default value you add to the name column (like default '') gets removed on regeneration. There's currently no config option to persist a default value for name; you'll need to reapply your manual change after each regeneration, or upgrade to a newer (beta) release once the fix for this is published (details).

To reply, just mention @dosu.

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

@dosubot[bot] commented on GitHub (Jul 17, 2025):  That's because the schema generator in Better Auth always reflects its internal model and overwrites manual changes—so any default value you add to the name column (like default '') gets removed on regeneration. There's currently no config option to persist a default value for name; you'll need to reapply your manual change after each regeneration, or upgrade to a newer (beta) release once the fix for this is published ([details](https://github.com/better-auth/better-auth/issues/2674)).  *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- How did I do? [Good](https://app.dosu.dev/response-feedback/5807b76a-3a32-4447-9dc3-47f9ba50320d?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/5807b76a-3a32-4447-9dc3-47f9ba50320d?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/5807b76a-3a32-4447-9dc3-47f9ba50320d?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/5807b76a-3a32-4447-9dc3-47f9ba50320d?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/5807b76a-3a32-4447-9dc3-47f9ba50320d?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/5807b76a-3a32-4447-9dc3-47f9ba50320d?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/5807b76a-3a32-4447-9dc3-47f9ba50320d?feedback_type=other)  [![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot) [![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/better-auth/better-auth/issues/3421)

GiteaMirror referenced this issue

2026-03-13 11:16:41 -05:00

[PR #1511] [MERGED] fix(passkey): remove client export from the server plugin #3837

GiteaMirror referenced this issue

2026-04-13 08:10:08 -05:00

[PR #1511] [MERGED] fix(passkey): remove client export from the server plugin #12084

GiteaMirror referenced this issue

2026-04-15 19:53:52 -05:00

[PR #1511] [MERGED] fix(passkey): remove client export from the server plugin #20738

GiteaMirror referenced this issue

2026-04-17 20:46:20 -05:00

[PR #1511] [MERGED] fix(passkey): remove client export from the server plugin #29438

Sign in to join this conversation.

Branches Tags

changeset-release/main

main

feat/identity-provider-accounts

changeset-release/next

fix/oauth-provider-session-deletion

feat/scim-active-user-link

feat/sso-provider-user-resolution

feat/oauth-provider-remove-silence-warnings

dependabot/npm_and_yarn/undici-7.28.0

dependabot/npm_and_yarn/vite-7.3.5

dependabot/github_actions/github-actions-62954de4be

dependabot/npm_and_yarn/demo/electron/demo-minor-patch-4169bf3d8e

changeset-release/release/vercel-announcement

release/vercel-announcement

2026-06-29/docs/optimize-og-images

feat/yandex-social-provider

feat/ssrf-fetch-boundary

codex/issue-8116-siwe-analysis

codex/pr-10225-next-comments

fix/phone-number-disable-input

perf/router-build-once

fix/oauth-user-provisioning-fields

codex/ignore-compose-override-spellcheck

2026-06-19/fix/stripe-org-reference-scope

feat/webhooks

feat/baseurl-canonical-serving-split

feat/magic-link-expires-in

fix/esbuild-security-bump

chore/sync-main-to-next-20260615

chore/revert-10053

codex/fix-expo-sdk56-dynamic-import

refactor/oauth-provider-client-authentication-module

fix/oauth-no-store-headers

claude/slack-update-stripe-docs-consistency-8Sc0w

local/fix-invite-accept-idempotency

docs/beta-mdx-component-fallback

fix/dependabot-hono-shell-quote

codex/stateless-account-cookie-resolution

fix/admin-create-user-role-escalation

feat/oauth-provider-oidc-acr

refactor/sign-in-challenges

refactor/optional-kysely-dependency

2026-06-06/chore/kysely-changeset

copilot/fix-code-review-comment

starsling/prisma-migration-reset

2026-06-02/fix/next-cookies-defer-rsc

feat/oauth-contribution-protocol

ping-maxwell/c-ping-maxwell/fix-kysely-adapter-core-utils-string-resolution-68c5

temp/server-only-test

2026-05-31/refactor/kysely-joins-json-helpers

2026-04-29/feat/google-include-granted-scopes

2026-04-29/fix/oauth-account-scope-semantics

fix/oauth-callback-path-declarative

2026-05-31/fix/sqlite-dialect-affected-rows

fix/next-cookie-separator

2026-05-29/fix/last-login-method-cookie-prefix

feat/oauth-provider-custom-subject

ping-maxwell/c-ping-maxwell/fix-error-link-apostrophe-f89a

client-assertions-main

2026-05-15/ci/fix-sqlite-abi-mismatch

2026-05-15/fix/organization-team-add-cascade

2026-05-15/fix/parse-set-cookie-value-validation

2026-05-13/feat/captcha-wildcard-endpoints

fix/i18n-before-hook-translation

fix/disable-migration-generate

2026-05-10/fix/cookie-drain-order

2026-05-10/feat/hooks-finally

2026-05-09/fix/cookie-drain-order

2026-05-09/feat/hooks-finally

2026-05-08/feat/register-before-send

fix/stripe/subscription-data-merge

2026-05-01/chore/pnpm-v11-harden

chore/pnpm-v11

2026-04-27/fix/nextcookies-idempotent-writes

2026-04-26/fix/harden-proxy-host-validation

2026-04-26/refactor/stripe-callback-signature-cleanup

2026-04-26/fix/stripe-subscription-callback-timing

2026-04-11/fix/sveltekit-app-modules

feat/open-api-zod-contract

feat/oauth-idp-initiated-bounce

2026-04-21/fix/oauth-rfc-input-validation

fix/two-factor-identity-guard

fix/resource

feat/emailpassword-authorize

feat/oauth-provider-at-hash-v2

fix/release-grep-fallback

claude/address-review-comments-JhFLr

feat/async-auth

fix/two-factor-totp-verified-enrollment

feat/plugin-ui

codex/blog-1-6-release-post

2026-04-06/fix/type-any-guards

2026-04-05/chore/downgrade-better-call

2026-04-04/ci/skip-vercel-fork-prs

2026-03-28/ci/add-autofix-ci

chore/release-preview-script

himself65/2026/02/19/role

2026-03-20/docs/improve-website

2026-03-20/fix/anonymous-onlinkaccount-expo

2026-02-17/fix/anonymous-link-state

fix/8607-saml-inresponseto

fix/8549-scim-patch-noop

v1.4.x

refactor/migration-snapshot-tests

worktree-magic-link-additional-data

chore/migrate-build-to-rollup

worktree-fix-dynamic-baseurl-8447

2026-03-06/chore/public-api-check

fix/close-8156-regression-test

fix/secondary-storage-json-error-handling

himself65/verification-namespace

cursor/issue-8307-validation-79a3

himself65/2026/01/30/error-mdx

v1.4.x-staging

fix/email-otp-user

fix/restrict-full-organization-access-roles

himself65/2026/02/12/count

himself65/2026/02/04/define-plugin

2026-02-04/feat/add-pluralize

cursor/better-auth-js-integration-ec21

cursor/expo-state-mismatch-394c

2026-02-01/fix/org-update-role-sync-members

cursor/issue-7607-investigation-e146

cursor/email-generation-helper-0ff6

himself65/2026/01/21/avoid-spread-operator

himself65/2026/01/14/cli

claude/slack-add-docs-pr-NMvgO

claude/slack-add-advanced-useplural-WHKYL

feat/hooks-pos

feat/2fa-phone

feat/2fa

fix/rotation

fix/username-check

v1.3.x

refactor/organization

feat/multiple-client-ids-social-providers

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/better-auth#1511