All Errors

Firebase Cloud Functions throws an internal error when your function encounters an unhandled exception, timeout, permission issue, or returns invalid data. This generic error typically indicates a problem in your function code that needs debugging via console logs.

APT cannot read or parse package list files, preventing installations and updates. This happens when cache files become corrupted during failed downloads or system interruptions. Rebuild the package cache by removing corrupted files.

PostgreSQL idle session timeouts terminate inactive database connections to prevent lock accumulation and table bloat. Learn how to configure and troubleshoot idle_session_timeout and idle_in_transaction_session_timeout parameters.

A protocol mismatch occurs when your MySQL client cannot communicate with the server due to incompatible protocol versions. This typically happens after version upgrades, downgrades, or when connecting to the wrong port.

This error occurs when you try to TRUNCATE a table that is referenced by another table through a foreign key constraint. TRUNCATE is much faster than DELETE but cannot proceed if child tables have references. Use CASCADE to truncate all related tables together, truncate tables in dependency order, or temporarily disable constraints.

This warning appears when SSH detects that a remote server's host key has changed. It prevents connections as a security measure to detect potential man-in-the-middle attacks or legitimate server reinstallations. The fix involves removing the old key from your local known_hosts file.

PostgreSQL error 57P03 occurs when the server cannot accept connections because it is starting up, shutting down, or in recovery mode. This is typically temporary and resolves once the server completes its startup or recovery process.

This error occurs when your parameterized SQL query references a placeholder like $1 or $2, but the corresponding parameter value was not provided when executing the statement. This is typically a binding mismatch between your application code and the prepared statement.

When a query fails in a PostgreSQL transaction, all subsequent commands are rejected until the transaction is rolled back. This occurs by design to maintain data consistency and requires explicit recovery using ROLLBACK or SAVEPOINT.

This error occurs when email authentication is disabled in Supabase Auth settings, preventing new users from signing up with email/password. Enable email provider in your project dashboard to allow email-based signups.

This error occurs when you try to use a reserved system column name (like tableoid, ctid, xmin, or xmax) as a regular column name in PostgreSQL. System columns are automatically added to every table and cannot be redefined.

This error occurs when a Firebase session cookie has exceeded its expiration time, requiring the user to re-authenticate. Session cookies can be configured to last between 5 minutes and 2 weeks.

PostgreSQL transaction timeout occurs when a transaction exceeds the configured time limit. This error prevents long-running operations and helps manage resource consumption by automatically terminating idle or overly long transactions.

This error occurs when fs.watch() exceeds the operating system limit for file watchers. File system watchers consume limited system resources, and watching too many files simultaneously exhausts these limits.

This error occurs when code attempts to interact with a listener that was already invoked through the once() method. The once() method registers a one-time listener that automatically removes itself after the first event emission, causing issues if code tries to access it again.

This error occurs when attempting to use TRUNCATE ONLY on a partitioned table, which is not allowed because partitioned tables are logical containers that hold no data themselves—all data resides in their child partitions.

This error occurs in Express.js when middleware or a route handler calls the next() function more than once during a single request cycle. Calling next() twice causes Express to attempt to send the response multiple times, leading to unexpected behavior and cryptic errors.

CR_UNKNOWN_ERROR (2000) is a catch-all MySQL client error that fires before the connector can deliver a more specific message. It usually appears when the connection or authentication handshake is aborted early—for example, when TLS is required but the client and server cannot agree on a cipher stack or when an authentication plugin terminates the session without reporting a normal SQLSTATE. Because no additional diagnostics are printed, the client sees only "Unknown MySQL error" and the server log typically contains nothing more than a brief warning or a reverse DNS lookup entry.

This error occurs when attempting to execute write operations (INSERT, UPDATE, DELETE) on a read-only transaction. Common causes include connecting to a read-only replica, hot standby server, or default_transaction_read_only setting enabled.

DynamoDB returns TableInUseException when you try to modify a table while another operation is already in progress on that table. This error occurs during concurrent CreateTable, UpdateTable, or DeleteTable operations on the same DynamoDB table.