Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fetch failed: AggregateError [ETIMEDOUT] on Node.js 20 #70095

Closed
raky291 opened this issue Sep 14, 2024 · 0 comments
Closed

Fetch failed: AggregateError [ETIMEDOUT] on Node.js 20 #70095

raky291 opened this issue Sep 14, 2024 · 0 comments
Labels
bug Issue was opened via the bug report template. Output (export/standalone) Related to the the output option in `next.config.js`.

Comments

@raky291
Copy link

raky291 commented Sep 14, 2024

Link to the code that reproduces this issue

https://github.com/raky291/pokedex

To Reproduce

  1. Create a Next.js project with Docker (feel free to use my repo)
  2. Change Node version to 20 on Dockerfile
  3. Run the application and make fetch requests to an API

Current vs. Expected behavior

I'm expecting it to perform fetch requests correctly like it does in the development (next dev) or production (next start) environment but it throws errors.

image

Provide environment information

Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Pro
  Available memory (MB): 32525
  Available CPU cores: 20
Binaries:
  Node: 20.16.0
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.2.11 // Latest available version is detected (14.2.11).
  eslint-config-next: 14.2.11
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.5.4
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)

Output (export/standalone)

Which stage(s) are affected? (Select all that apply)

Other (Deployed)

Additional context

I have Node version 20 installed on my machine. In development (next dev) and production (next start) it works fine. But with Docker (standalone) it throws errors. It's weird because with version 20 in Docker if you make a single fetch request it works.

I had to downgrade the Node version to 18 to fix the issue.

@raky291 raky291 added the bug Issue was opened via the bug report template. label Sep 14, 2024
@github-actions github-actions bot added the Output (export/standalone) Related to the the output option in `next.config.js`. label Sep 14, 2024
@vercel vercel locked and limited conversation to collaborators Sep 24, 2024
@samcx samcx converted this issue into discussion #70423 Sep 24, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
bug Issue was opened via the bug report template. Output (export/standalone) Related to the the output option in `next.config.js`.
Projects
None yet
Development

No branches or pull requests

1 participant