`ERR_INTERNAL_ASSERTION` with Strapi CLI

[nooritaki]

Version

Node.js v20.10.0

Platform

VSCode PowerShell Terminal

Subsystem

No response

What steps will reproduce the bug?

No response

How often does it reproduce? Is there a required condition?

No response

What is the expected behavior? Why is that the expected behavior?

No response

What do you see instead?

Error [ERR_INTERNAL_ASSERTION]: This is caused by either a bug in Node.js or incorrect usage of Node.js internals.
Please open an issue with this stack trace at https://github.com/nodejs/node/issues

    at assert (node:internal/assert:14:11)
    at internalConnectMultiple (node:net:1118:3)
    at Timeout.internalConnectMultipleTimeout (node:net:1687:3)
    at listOnTimeout (node:internal/timers:575:11)
    at process.processTimers (node:internal/timers:514:7) {
  code: 'ERR_INTERNAL_ASSERTION'
}

Additional information

I am reaching out to seek assistance regarding an issue I encountered after installing the Strapi CLI within the VSCode terminal and accessing the Strapi admin dashboard via http://localhost:1337/admin.

Issue Overview:
After successful installation of the Strapi CLI, I launched the Strapi admin dashboard on my local server at http://localhost:1337/admin. While navigating through the dashboard, I observed inconsistent behavior. I was able to create an account and occasionally create content titles. However, I faced recurring difficulties when attempting to upload image items. Upon refreshing the browser, the following error message was consistently displayed:

"This site can’t be reached - localhost refused to connect.
Try:

Checking the connection
Checking the proxy and the firewall
ERR_CONNECTION_REFUSED"
Moreover, the VSCode terminal generated an error message (as enclosed below) which I believe is associated with the issue:

Error Message in VSCode Terminal:

Error [ERR_INTERNAL_ASSERTION]: This is caused by either a bug in Node.js or incorrect usage of Node.js internals.
Please open an issue with this stack trace at https://github.com/nodejs/node/issues

at assert (node:internal/assert:14:11)
at internalConnectMultiple (node:net:1118:3)
at Timeout.internalConnectMultipleTimeout (node:net:1687:3)
at listOnTimeout (node:internal/timers:575:11)
at process.processTimers (node:internal/timers:514:7) {
  code: 'ERR_INTERNAL_ASSERTION'
}

Request for Assistance:
I have attempted troubleshooting steps, including reinstalling the Strapi CLI and checking for potential firewall or connectivity issues, but the problem persists. I am uncertain whether this issue is related to a bug in Node.js or if it pertains to incorrect usage of Node.js internals.

Could you kindly provide guidance or assistance to rectify this issue? Any insights, suggestions, or steps to further diagnose and resolve this matter would be greatly appreciated.

Thank you for your time and support. Please let me know if any additional information or logs are required to assist in troubleshooting this issue.

[aduh95]

There are a lot of similar looking reports at strapi/strapi#18084. It seems a workaround for Strapi users is to downgrade to Node.js 18.x or upgrade to 21.x until the fix is backported to 20.x.

[aduh95]

@ShogunPanda it looks like the failing assert was added in https://github.com/nodejs/node/pull/46587/files#diff-218c57e035f64b18af4db037c96f13014aeb40a1f783d4f52919e2075621da0cR1099

[Klaitos]

We encounter the same issue on every fastify servers we have on our side. The stack trace is exactly the same, happening on node 20.10 (not using Strapi CLI)

[aduh95]

Hopefully it's been fixed by #51045 already (which is on the 21.x release line, and should be in the next 20.x release).

[Klaitos]

I did not found it in 20.11 changelog, waiting for 20.12 I guess, thanks for pointing me the potential fix.

[tniessen]

Probably a duplicate of #51285.