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.

[rrraj]

I'm using Node.js v21.2.0, and still encountering this issue. Please suggest what can I do to resolve this issue. Thanks :)

#51487

[ShogunPanda]

It should have been fixed in Node 21.6.0.

[rrraj]

@ShogunPanda I'll check now, Thanks for your response !👍

[avinashmaurya86]

node:internal/assert:14
throw new ERR_INTERNAL_ASSERTION(message);
^

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'
}

This error occurs while uploading images in strapi admin dashboard.
and the Strapi localhost shutdown automatically

[ShogunPanda]

@avinashmaurya86 This should be fixed in 21.6.0, can you please check?

[malditogeek]

@ShogunPanda do you know if this will be backported to 20.x and if so, when 20.12.0 will be released?

[avinashmaurya86]

No sir it is well supported in Jode js version 18

…

On Sun, 28 Jan, 2024, 12:23 pm Paolo Insogna, ***@***.***> wrote: @avinashmaurya86 <https://github.com/avinashmaurya86> This should be fixed in 21.6.0, can you please check? — Reply to this email directly, view it on GitHub <#51354 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AWNTYZ4AW2GSRZBVKLFBANTYQXYVZAVCNFSM6AAAAABBMCTQVKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJTGQ3TONJRGA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[avinashmaurya86]

No sir it is well supported in Node js version 18

…

On Mon, 26 Feb, 2024, 7:25 pm Mauro Pompilio, ***@***.***> wrote: @ShogunPanda <https://github.com/ShogunPanda> do you know if this will be backported to 20.x and if so, when 20.12.0 will be released? — Reply to this email directly, view it on GitHub <#51354 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AWNTYZY3TCONPOSEKZVBAGTYVSH5PAVCNFSM6AAAAABBMCTQVKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRUGIYDINBRHE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[ShogunPanda]

@malditogeek Yes, it will be included in 20.12.0. Not sure about the release date tho.

[avinashmaurya86]

No sir I don't have any idea about this.

…

On Mon, 26 Feb, 2024, 7:25 pm Mauro Pompilio, ***@***.***> wrote: @ShogunPanda <https://github.com/ShogunPanda> do you know if this will be backported to 20.x and if so, when 20.12.0 will be released? — Reply to this email directly, view it on GitHub <#51354 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AWNTYZY3TCONPOSEKZVBAGTYVSH5PAVCNFSM6AAAAABBMCTQVKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRUGIYDINBRHE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[avinashmaurya86]

But my project of Strapi is perfectly running in Node version 18

…

On Mon, 26 Feb, 2024, 7:25 pm Mauro Pompilio, ***@***.***> wrote: @ShogunPanda <https://github.com/ShogunPanda> do you know if this will be backported to 20.x and if so, when 20.12.0 will be released? — Reply to this email directly, view it on GitHub <#51354 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AWNTYZY3TCONPOSEKZVBAGTYVSH5PAVCNFSM6AAAAABBMCTQVKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRUGIYDINBRHE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[ShogunPanda]

@avinashmaurya86 Because network family autoselection is disabled by default in 18. It was turned on by default in 20.

[avinashmaurya86]

Thank you for your response sir. It helps me better than before.

…

On Mon, 26 Feb, 2024, 9:55 pm Paolo Insogna, ***@***.***> wrote: @avinashmaurya86 <https://github.com/avinashmaurya86> Because network family autoselection is disabled by default in 18. It was turned on by default in 20. — Reply to this email directly, view it on GitHub <#51354 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AWNTYZ5XF3MGQYOTSRNT4OTYVSZQVAVCNFSM6AAAAABBMCTQVKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRUGU3TEMRTHA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[randomhash]

could you please backport it somehow into the 20.10.10? As lambda version affected also

[ShogunPanda]

There is no 20.10.10 version. Are you sure it's the right number?

[aduh95]

I think the fix has been backported to 20.12.0, we can probably close this now. If you're still experiencing this on Node.js 20.12.0 or later, please open a new issue.

[randomhash]

@ShogunPanda
Sorry, the version is 20.11.1
Still getting errors in it

[ShogunPanda]

I see.
I think Lambda will update the runtime in couple of months at most.
For the time being, you can set the NODE_OPTIONS environment variables to to include --no-network-family-autoselection to disable the offending behavior.