Field guide to command line failures · reference only, nothing hosted here
CliHelper

Command line errors, explained

CliHelper is a troubleshooting notebook for the command line. Each entry starts from something that actually went wrong - a non-zero exit, a permission error, an empty result set - and works back to the cause and the fix. No package or archive is stored on this domain.

All twenty entries

permission denied
Exit code 13, and the variants that look like it.
command not found
Exit code 127, and the PATH problem behind it.
No such file or directory
Exit code 2, including the misleading CRLF case.
Killed
Exit code 137, and what actually consumed the memory.
Exit code 1
The catch-all failure, and how to stop guessing.
Segmentation fault
SIGSEGV from a shell script, and where to look.
Broken pipe
SIGPIPE when a pipeline consumer exits early.
certificate verify failed
TLS errors, and which hostname was actually checked.
Temporary failure in name resolution
Resolver problems versus a dead host.
Connection refused
Nothing is listening on that port.

CliHelper documents failure modes of third-party command line tools. No software is stored or distributed here.

Terms Privacy Contact support@clihelper.pro