All Errors

Error 2 (EE_READ) occurs when MySQL cannot read a file it needs to access, typically due to file permissions, missing files, or filesystem issues. This error prevents database operations and requires checking file access rights and data integrity.

The "ERR Failed to resolve hostname" error occurs when Redis or a Redis client cannot resolve a hostname to its IP address through DNS. This is typically caused by DNS configuration issues, network connectivity problems, or incorrect hostname configuration.

PostgreSQL "certificate verify failed" is an SSL/TLS error that occurs when the client cannot verify the server's certificate. It usually means the root CA certificate is missing, outdated, or misconfigured.

This error occurs when PostgreSQL terminates the pg_dump connection mid-backup. Common causes are idle/statement timeouts, parallel-worker idling, and firewalls dropping idle TCP connections. Check server logs and adjust timeouts.

Firebase Hosting blocks cross-origin requests to Cloud Functions and APIs unless CORS headers are explicitly configured. Enable CORS by setting headers in firebase.json or adding CORS middleware to your Cloud Functions.

Firebase custom claims cannot use OIDC reserved names like "iss", "sub", "aud", "exp", "iat", or Firebase reserved names. This error occurs when you try to set custom user claims with these reserved keywords.

MySQL Error 2013 occurs when the connection between client and server is unexpectedly terminated mid-query. Fix it by tuning timeouts, max_allowed_packet, optimizing slow queries, and adding retry logic.

This MySQL client error occurs when attempting to call mysql_real_connect() on a connection handle that is already connected to a MySQL server. The error indicates that your code is reusing a connection handle without properly closing the previous connection first, or attempting to reconnect on an already-active connection.

This error occurs when a Firebase Callable Function rejects a request due to missing, invalid, or expired authentication credentials. The client must be signed in with Firebase Authentication, and the ID token must be valid and properly included in the request headers.

MySQL Error 2005 occurs when the client cannot resolve or reach the specified MySQL server hostname. This is typically caused by DNS resolution failures, incorrect hostnames, or network connectivity issues.

You exceeded Firebase Cloud Messaging's per-project rate limit by sending too many messages within a short time window. FCM enforces a default quota of 600,000 messages per minute across your entire project.

The DEPTH_ZERO_SELF_SIGNED_CERT error occurs when npm reaches a self-signed certificate at the root of the chain (depth zero). Fix it by trusting that certificate via npm's cafile or your OS trust store.

This MySQL client error occurs when the client process runs out of available memory while fetching or processing query results. The error typically appears when executing queries that return extremely large result sets, processing large BLOB columns, or when the client application has insufficient memory allocation. Breaking queries into smaller chunks, increasing memory limits, or using unbuffered result fetching resolves this issue.

This error occurs when you pass invalid parameters to Firebase Authentication methods. Common causes include empty strings, null values, wrong parameter types, or incorrect method syntax. Most fixes involve validating inputs before passing them to Firebase functions.

This error occurs when you enable TypeScript's 'allowImportingTsExtensions' option without also enabling 'noEmit' or 'emitDeclarationOnly'. The fix depends on whether you're using a bundler or TypeScript runtime.

The SSH server closed the connection before key exchange completed. Usually caused by IP blocking, fail2ban bans, MaxStartups limits, resource exhaustion, or a misbehaving sshd.

This Firebase Storage error occurs when you pass an unsupported data type to the upload function. Firebase Storage upload methods accept only Blob, File, Uint8Array, or ArrayBuffer types. Passing strings, objects, or other data types will trigger this validation error. The fix is to ensure your data is converted to one of the supported formats before uploading.

This error occurs when attempting to upload a file or access an object in Supabase Storage with an invalid file path. Common causes include special characters in the file name, empty path strings, non-ASCII characters that get URL-encoded, or structural issues in the path format.

npm can't find git on PATH when installing a git dependency. Fix: install Git and reopen your terminal so git is on PATH.

This error occurs when a scalar subquery in your SQL query returns multiple rows instead of the expected single row. In Supabase, this commonly happens during INSERT/UPDATE operations with triggers, RLS policies, or computed columns.