Errors
Error reference
Find the cause and fix for Nuxt Better Auth module setup and schema generation errors.
Use the diagnostic code from your terminal to find its cause, a fix example, and a way to check the result. These codes describe module setup and schema generation. Sign-in errors retain Better Auth's codes, and session authorization failures retain their HTTP 401 or 403 status.
- NUXT_AUTH_MISSING_CONFIG: Missing auth configuration
- NUXT_AUTH_NO_DATABASE_PROVIDER: No database provider is enabled
- NUXT_AUTH_MISSING_HUB_DB: NuxtHub database alias is missing
- NUXT_AUTH_INVALID_PLUGIN_SOURCE: Auth plugin path must be absolute
- NUXT_AUTH_STORAGE_CLIENT_ONLY: Secondary storage in client-only mode
- NUXT_AUTH_SCHEMA_STORAGE_REQUIRED: Custom session storage is missing
- NUXT_AUTH_UNSUPPORTED_DIALECT: Unsupported database dialect
- NUXT_AUTH_INVALID_CONFIG_EXPORT: Invalid server auth config export
- NUXT_AUTH_CONFIG_LOAD_FAILED: Auth configuration failed to load
- NUXT_AUTH_CLI_MISSING: Better Auth CLI is not installed
- NUXT_AUTH_CLI_VERSION_MISMATCH: Better Auth CLI version does not match better-auth
- NUXT_AUTH_EMPTY_SCHEMA: Schema generator returned no code
- NUXT_AUTH_SCHEMA_GENERATION_FAILED: Auth schema generation failed
If a config cannot load during development, the module skips schema regeneration and preserves the existing schema. Production builds fail on the same config error. Read the specific diagnostic before creating a database migration.