All Errors

The SSH "Access denied" error occurs when the SSH server rejects your authentication attempt. This is usually due to incorrect credentials, misconfigured keys, disabled authentication methods, or account/group restrictions on the server.

The npm "spawn ENOENT" error means Node.js could not find an executable that an npm script tried to launch. Usually the command is missing from PATH or node_modules is broken.

The 'iptables failed' error occurs when Docker cannot configure network rules needed for container connectivity. This typically happens when iptables rules are flushed while Docker is running, the DOCKER chain is missing, or there are iptables version compatibility issues.

This error occurs on macOS when the Xcode Command Line Tools are missing, corrupted, or their path is invalid. It commonly appears after a macOS update and prevents Git and other development tools from working. The fix is straightforward: reinstall or reset the Command Line Tools.

The SSH client cannot reach the remote server on port 22 within the timeout period. The packet_write_poll error indicates the TCP connection attempt failed to establish. This typically means a firewall is blocking the connection, the SSH service isn't running, or there are network routing issues.

The 'docker exec' command fails because the target container has exited or stopped. This typically happens when containers exit immediately after starting due to missing long-running processes or when you attempt to execute commands in a stopped container.

The 'write: connection timed out' error occurs when Docker fails to complete a network write operation within the expected time. This typically happens during image push/pull operations, container-to-container communication, or when connecting to external services due to network congestion, firewall rules, or MTU mismatches.

The 'ssh: connect to host github.com port 22: Connection refused' error occurs when your SSH connection to GitHub is actively rejected. This typically happens when port 22 is blocked by a firewall, the SSH service is unavailable, or network issues prevent the connection. The most common fix is to use SSH over port 443.

The "Couldn't find any package by glob" error means apt cannot match the package name in any configured repository. Usual causes are typos, missing PPAs, or wrong naming.

Database corruption prevents all queries and operations. Use PRAGMA integrity_check to diagnose the issue, then recover data using the .recover command or dump-and-rebuild method to restore functionality.

This warning appears when SSH cannot find or access the identity file (private key) at the specified path. It typically indicates the key file doesn't exist, the path is incorrect, or the file has been moved.

This error occurs when a Docker container exceeds its memory limit and the Linux kernel's OOM (Out of Memory) killer terminates it. The fix involves setting appropriate memory limits, optimizing application memory usage, and configuring swap settings.

This error occurs when a transaction waits too long (default 50 seconds) to acquire a row lock. It happens due to uncommitted transactions holding locks, missing indexes, or high contention. You can fix it by increasing the timeout, identifying blocking sessions, or optimizing queries.

Context deadline exceeded occurs when a Terraform provider API call times out before receiving a response. This typically indicates the client timeout is shorter than the API operation duration, particularly common with large cloud resource deployments.

TypeScript lacks Node types. Fix: run npm i --save-dev @types/node and add "node" to types in tsconfig.json.

This error occurs when SSH authentication succeeds but the session is immediately terminated by the server after the user authenticates. It typically indicates file permission issues, configuration problems, or incompatible authentication settings between client and server.

This error occurs when Docker cannot execute a binary or script due to architecture mismatch, missing shebang line, or incorrect file format. Common causes include running amd64 images on ARM hosts, scripts with Windows line endings (CRLF), or entrypoint files missing the #!/bin/bash shebang.

This error occurs when pulling a Docker image that doesn't have a version compiled for your CPU architecture. Common on Apple Silicon Macs (M1/M2/M3) and ARM-based systems like Raspberry Pi when trying to use x86/amd64-only images. Fix by using the --platform flag, setting DOCKER_DEFAULT_PLATFORM, or finding multi-architecture images.

This error occurs when SSH clients exceed the server's maximum authentication attempts limit (default: 6). It's a security mechanism to prevent brute-force attacks. Resolve it by specifying the correct key, reducing failed attempts, or increasing MaxAuthTries on the server.

The Docker 'invalid reference format' error means Docker cannot parse your image name. Common causes include uppercase letters, spaces in paths, unset environment variables, or copy-pasted special characters. Fix it by using lowercase names, quoting paths, and verifying your image reference syntax.