All Errors

Git's "Proxy CONNECT aborted" error means a proxy rejected the HTTP CONNECT tunnel to the remote host. Fix it by correcting proxy auth, host allow-listing, or CA trust.

SSH fails when client and server share no common MAC algorithm during negotiation, usually because a modern client dropped the legacy MACs an old server or device still offers.

The Prisma P6005 error occurs when you provide invalid or incompatible parameters to Prisma Pulse operations, typically with transaction timeouts or configuration settings that exceed service limits. This usually happens with misconfigured transaction parameters or incompatible Prisma versions with Pulse.

This error occurs when Prisma tries to create foreign key constraints in your schema but the database doesn't support them (like PlanetScale). Resolve it by switching to emulated relations mode or enabling foreign key support in your database.

Supabase Auth restricts email sending to pre-authorized addresses when using the default email provider. This error occurs when trying to send authentication emails to addresses not in your project's authorized list.

Supabase requires reauthentication before allowing users to change their password or email address. This security measure prevents unauthorized account modifications when the Secure password change or Secure email change options are enabled.

OpenSSH prints "Load key: invalid format" when it cannot parse a private key file. This is usually caused by a mangled key (lost newlines from copy-paste or CI variables), or by passing a .pub file instead of the private key.

The Supabase API requires an Authorization header with a JWT token for authenticated requests. This error occurs when requests to protected endpoints, Edge Functions, or Row Level Security policies don't include a valid JWT token in the Authorization header.

Docker returns HTTP 407 "Proxy Authentication Required" when pulling images through a corporate proxy that needs credentials. Fix it by configuring authenticated proxy settings for the Docker daemon.

The Git server closed the SSH connection during the initial identification/banner exchange. On GitHub this is almost always IP-based rate limiting from a shared or NAT'd address, but blocked SSH ports can also cause it.

This error occurs when unlinking an identity would cause a user's account to switch to an email address that's already in use by another user. Supabase enforces unique email addresses across all user accounts.

Supabase returns "otp_expired: OTP has expired" when you attempt to verify a one-time password (OTP) that has exceeded its expiration window. By default, OTP codes are valid for 1 hour. The fix is to request a new OTP, check your configuration for timeout settings, or verify you are using the correct OTP type parameter in your authentication call.

The SSH daemon failed to launch the requested subsystem (usually SFTP). Common causes: wrong subsystem path in sshd_config, a missing sftp-server binary, or chroot misconfiguration.

This error occurs during Supabase OAuth authentication when the state parameter used for CSRF protection is missing, invalid, or doesn't match between the initial request and OAuth provider callback. It typically indicates a session mismatch, hostname misconfiguration, or cookie persistence issue.

The "mfa_challenge_expired: MFA challenge has expired" error occurs when you attempt to verify a multi-factor authentication challenge that has exceeded its validity window. Supabase challenges have a limited lifetime (typically 5-10 minutes), and verification requests submitted after expiration are rejected, requiring you to create a new challenge.

The "mfa_factor_not_found" error in Supabase occurs when attempting to challenge, verify, or manage an MFA factor that doesn't exist or is no longer available. This typically happens during incomplete enrollments, page refreshes before verification completes, or when trying to use an unenrolled factor ID.

This error occurs when using XREADGROUP on a Redis Stream consumer group that has not been created yet. Create the consumer group first with XGROUP CREATE before reading messages.

Redis Cluster mode only supports database 0 and disallows the SELECT command. This error occurs when your client attempts to switch databases in cluster mode, which is not supported by design.

This error occurs when attempting to use Redis Cluster commands on a standalone Redis instance. Enable cluster mode in your redis.conf configuration file and restart the instance to resolve it.

This error occurs when you attempt to insert or query a UUID column with a malformed value. PostgreSQL expects UUIDs in the standard 8-4-4-4-12 hexadecimal format, and will reject any value that doesn't match valid UUID syntax.