Error code search

This error represents a failed test. Additional information about the failure is available via the cause property. The failureType property specifies what the test was doing when the failure occurred.

A call was dropped because a throttled function could not invoke it immediately or its pending queue was full.

This error is thrown when an ALPNCallback returns a value that is not in the list of ALPN protocols offered by the client.

This error is thrown when creating a TLSServer if the TLS options include both ALPNProtocols and ALPNCallback. These options are mutually exclusive.

This error is thrown by checkServerIdentity if a user-supplied subjectaltname property violates encoding rules. Certificate objects produced by Node.js itself always comply with encoding rules and will never cause this error.

While using TLS, the host name/IP of the peer did not match any of the subjectAltNames in its certificate.

While using TLS, the parameter offered for the Diffie-Hellman (DH) key-agreement protocol is too small. By default, the key length must be greater than or equal to 1024 bits to avoid vulnerabilities, even though it is strongly recommended to use 2048 bits or larger for stronger security.

A TLS/SSL handshake timed out. In this case, the server must also abort the connection.

The context must be a SecureContext.

The specified secureProtocol method is invalid. It is either unknown, or disabled because it is insecure.

Valid TLS protocol versions are 'TLSv1', 'TLSv1.1', or 'TLSv1.2'.

The TLS socket must be connected and securely established. Ensure the 'secure' event is emitted before continuing.

Attempting to set a TLS protocol minVersion or maxVersion conflicts with an attempt to set the secureProtocol explicitly. Use one mechanism or the other.

Failed to set PSK identity hint. Hint may be too long.

An attempt was made to renegotiate TLS on a socket instance with renegotiation disabled.

Used when a TLS renegotiation request has failed in a non-specific way.

An attempt was made to renegotiate TLS, but the TLS implementation does not support caller-initiated renegotiation.

While using TLS, the server.addContext() method was called without providing a host name in the first parameter.

An excessive amount of TLS renegotiations is detected, which is a potential vector for denial-of-service attacks.

An attempt was made to issue Server Name Indication from a TLS server-side socket, which is only valid from a client.

The trace_events.createTracing() method requires at least one trace event category.

The node:trace_events module could not be loaded because Node.js was compiled with the --without-v8-platform flag, or because the process was initialized by an embedder that provides its own V8 platform.

Trailing junk found after the end of the compressed stream. This error is thrown when extra, unexpected data is detected after the end of a compressed stream (for example, in zlib or gzip decompression).

A SharedArrayBuffer whose memory is not managed by the JavaScript engine or by Node.js was encountered during serialization. Such a SharedArrayBuffer cannot be serialized. This can only happen when native addons create SharedArrayBuffers in "externalized" mode, or put existing SharedArrayBuffer into externalized mode.

A Transform stream finished while it was still transforming.

A Transform stream finished with data still in the write buffer.

The initialization of a TTY failed due to a system error.

Function was called within a process.on('exit') handler that shouldn't be called within process.on('exit') handler.

process.setUncaughtExceptionCaptureCallback() was called twice, without first resetting the callback to null. This error is designed to prevent accidentally overwriting a callback registered from another module.

A string that contained unescaped characters was received.

An unhandled error occurred (for instance, when an 'error' event is emitted by an EventEmitter but an 'error' handler is not registered).

Used to identify a specific kind of internal Node.js error that should not typically be triggered by user code. Instances of this error point to an internal bug within the Node.js binary itself.

A Unix group or user identifier that does not exist was passed.

An invalid or unknown encoding option was passed to an API.

An attempt was made to load a module with an unknown or unsupported file extension.

An attempt was made to load a module with an unknown or unsupported format.

An invalid or unknown process signal was passed to an API expecting a valid signal (such as subprocess.kill()).

An attempt was made to launch a Node.js process with an unknown stdin file type. This error is usually an indication of a bug within Node.js itself, although it is possible for user code to trigger it.

An attempt was made to launch a Node.js process with an unknown stdout or stderr file type. This error is usually an indication of a bug within Node.js itself, although it is possible for user code to trigger it.

import a directory URL is unsupported. Instead, self-reference a package using its name and define a custom subpath in the "exports" field of the package.json file.