Proxychains Command Not Found: Check proxychains4 and PATH
Resolve a missing Proxychains wrapper command by checking the installed binary name and PATH before creating a compatibility alias.
proxychains-ng's upstream build names its wrapper proxychains4. A shell reporting proxychains: command not found may therefore be looking for a different name from the one installed.
command -v proxychains4
command -v proxychainsWhen proxychains4 exists, use that executable directly:
proxychains4 curl https://www.example.com/The proxy configuration still determines the route for this invocation. Resolving the command name does not establish that the endpoint works.
If neither command is found, inspect the installed package's file list or the prefix used by the existing installation. Its executable directory may be absent from PATH. Upstream's default prefix is not a guarantee about a distribution package or another machine.
A user-shell alias can preserve an old interactive spelling once the real command is known. Scripts do not necessarily load that alias. Use the actual executable name or an explicitly managed compatibility wrapper there.
A hard-coded symlink to /usr/bin/proxychains4 only helps when that target actually exists. Diagnose the binary name and path before adding one.