All Errors

The "REALTIME_TIMEOUT: Connection to Realtime server timed out" error occurs when Supabase Realtime cannot establish or maintain a WebSocket connection to the realtime server. This typically happens due to network issues, firewall restrictions, browser extensions, or server-side configuration problems. The error prevents realtime features like live subscriptions, presence, and broadcast channels from working.

This error occurs when Buffer.concat() receives arguments that are not Buffer or Uint8Array instances. The method expects an array containing only Buffer or Uint8Array objects, but receives strings, plain objects, or other incompatible types instead.

This error occurs when the .datetime() method in PostgreSQL jsonpath expressions receives a string that cannot be parsed as a valid date/time format. Fix it by ensuring ISO 8601 format, using the silent parameter, or specifying a datetime template.

The MaxTimeMSExpired error occurs when a MongoDB operation exceeds the maximum execution time limit specified by the maxTimeMS parameter. This server-side timeout mechanism prevents long-running queries from consuming excessive database resources and helps maintain overall system performance.

This error occurs when Elasticsearch puts an index into read-only mode, typically due to low disk space or cluster settings. The index blocks write operations but allows deletions to free up space. You need to address the underlying disk space issue or adjust cluster settings to restore write access.

PostgreSQL enforces a 268MB size limit on JSONB array elements to prevent memory issues. Split large arrays into multiple smaller arrays or normalize data into relational tables.

This Firebase Authentication error occurs when you try to update a user's 'disabled' property with a non-boolean value. The 'disabled' field must be either true or false, and this error appears when passing strings, numbers, null, or undefined instead. The fix involves ensuring you pass a proper boolean value when enabling or disabling user accounts.

The Prisma P1016 error occurs when using raw SQL queries with parameter placeholders that don't match the number of provided values. This happens when you have mismatched placeholders (like $1, $2) and the actual parameter array length. The fix involves carefully counting placeholders and ensuring each has a corresponding value.

This error occurs when you try to run Prisma migrations with an outdated schema format that uses arrays for datasource providers. Prisma migrated from array-based provider definitions to single provider strings, requiring schema updates before migrations can proceed.

This error occurs when using PostgreSQL SQL/JSON functions like JSON_VALUE() or JSON_QUERY() and attempting to cast a JSON value to an incompatible SQL type. It typically indicates a type mismatch between the JSON content and the target data type.

SQLSTATE 22010 occurs when PostgreSQL receives an invalid indicator parameter value in a prepared statement or function call. Indicator parameters are used to signal NULL values in parameterized queries, and this error means the indicator value provided does not conform to SQL standards.

This error occurs when a JSON_VALUE() or jsonb_path_query() call in strict mode tries to extract a numeric value from a JSON path that doesn't contain a number or doesn't exist. Use ON ERROR/ON EMPTY clauses or switch to lax mode to handle missing numeric values.

The "connection refused because too many open connections" error occurs when MongoDB or its client drivers cannot establish new connections due to hitting connection limits. This typically happens in high-traffic applications, misconfigured connection pools, or when connections are not properly closed. The error prevents new database operations until connections are freed up.

PostgreSQL raises the duplicate function error (code 42723) when you try to CREATE a function with the same name and parameter types as an existing function. Use CREATE OR REPLACE FUNCTION to update existing functions or DROP the old one first.

This error occurs when a SQLite trigger uses the RAISE function to abort an operation, typically for data validation or business rule enforcement. The trigger detects invalid data and prevents the INSERT, UPDATE, or DELETE operation from completing. Common causes include validation triggers, audit trails, and complex business logic enforcement.

Supabase (PostgREST) returns PGRST102 when the JSON payload sent to a REST endpoint is malformed, contains syntax errors, or violates schema constraints. This error prevents the request from reaching the database and requires fixing the JSON structure before resubmitting.

PostgreSQL error 3D000 means you specified a database name that doesn't exist or is misspelled. Fix it by verifying the database name exists and checking your connection string.

This error occurs when attempting to drop a PostgreSQL role that still has privileges granted on database objects. PostgreSQL prevents the role from being dropped to maintain security and ownership integrity.

The Prisma P5004 error occurs when you attempt to use a feature that is not yet supported in Prisma Accelerate. This typically happens when trying to use advanced database operations, specific query patterns, or newer Prisma features that haven't been implemented in the Accelerate service yet. The fix involves identifying the unsupported feature and using alternative approaches or waiting for Accelerate to support it.

This PostgreSQL error occurs when there's a conflict with escape characters in string literals, typically in COPY commands, E'...' strings, or when using backslashes as escape characters. The parser encounters ambiguous or conflicting escape sequences that it cannot resolve.