Node.js error codes

Argon2 is not supported by the current version of OpenSSL being used.

An OpenSSL engine was requested (for example, through the clientCertEngine or privateKeyEngine TLS options) that is not supported by the version of OpenSSL being used, likely due to the compile-time flag OPENSSL_NO_ENGINE.

An invalid value for the format argument was passed to the crypto.ECDH() class getPublicKey() method.

An invalid value for the key argument has been passed to the crypto.ECDH() class computeSecret() method. It means that the public key lies outside of the elliptic curve.

An invalid crypto engine identifier was passed to require('node:crypto').setEngine().

The --force-fips command-line argument was used but there was an attempt to enable or disable FIPS mode in the node:crypto module.

An attempt was made to enable or disable FIPS mode, but FIPS mode was not available.

The UTF-16 encoding was used with hash.digest(). While the hash.digest() method does allow an encoding argument to be passed in, causing the method to return a string rather than a Buffer, the UTF-16 encoding (e.g. ucs or utf16le) is not supported.

hash.digest() was called multiple times. The hash.digest() method must be called no more than one time per instance of a Hash object.

hash.update() failed for an unspecified reason.

The given crypto keys are incompatible with the attempted operation.

The selected public or private key encoding is incompatible with other options.

Initialization of the crypto subsystem failed.

An invalid authentication tag was provided.

An invalid counter was provided for a counter-mode cipher.

An invalid elliptic-curve was provided.

An invalid crypto digest algorithm was specified.

An invalid initialization vector was provided.

An invalid JSON Web Key was provided.

An invalid key length was provided.

An invalid key pair was provided.

An invalid key type was provided.

The given crypto key object's type is invalid for the attempted operation.

An invalid MAC algorithm was specified.

An invalid message length was provided.

One or more crypto.scrypt() or crypto.scryptSync() parameters are outside their legal range.

A crypto method was used on an object that was in an invalid state. For instance, calling cipher.getAuthTag() before calling cipher.final().

An invalid authentication tag length was provided.

Initialization of an asynchronous crypto operation failed.

Key's Elliptic Curve is not registered for use in the JSON Web Key Elliptic Curve Registry.

Key's Asymmetric Key Type is not registered for use in the JSON Web Key Types Registry.

Attempted to use KEM operations while Node.js was not compiled with OpenSSL with KEM support.

An operation was attempted on a Mac object after finalization was attempted or an underlying MAC update failed.

Node.js was built without support for the OpenSSL EVP_MAC API.

mac.update() failed for an unspecified reason.

A crypto operation failed for an otherwise unspecified reason.

The PBKDF2 algorithm failed for unspecified reasons. OpenSSL does not provide more details and therefore neither does Node.js.

An incompatible combination of options was passed to crypto.scrypt() or crypto.scryptSync(). New versions of Node.js use the error code ERR_INCOMPATIBLE_OPTION_PAIR instead, which is consistent with other APIs.

Node.js was compiled without scrypt support. Not possible with the official release binaries but can happen with custom builds, including distro builds.

A signing key was not provided to the sign.sign() method.