Skip to content
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

fix about node:fetch? #637

Closed
hp8wvvvgnj6asjm7 opened this issue Jul 7, 2023 · 1 comment
Closed

fix about node:fetch? #637

hp8wvvvgnj6asjm7 opened this issue Jul 7, 2023 · 1 comment

Comments

@hp8wvvvgnj6asjm7
Copy link
Contributor

nodejs/undici#2170

@hp8wvvvgnj6asjm7 hp8wvvvgnj6asjm7 changed the title migrate to node:fetch? fix about node:fetch? Jul 7, 2023
@hp8wvvvgnj6asjm7
Copy link
Contributor Author

hp8wvvvgnj6asjm7 commented Jul 7, 2023

Any idea how to fix this?

Welcome to Node.js v20.2.0.
Type ".help" for more information.
> const res = await fetch('https://fapi.binance.com/fapi/v1/exchangeInfo', { method: 'GET' })
Uncaught TypeError: fetch failed
    at Object.fetch (node:internal/deps/undici/undici:11522:11)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async REPL1:1:37 {
  cause: Error [ERR_SOCKET_CONNECTION_TIMEOUT]: Socket connection timeout
      at new NodeError (node:internal/errors:399:5)
      at internalConnectMultiple (node:net:1099:20)
      at Timeout.internalConnectMultipleTimeout (node:net:1638:3)
      at listOnTimeout (node:internal/timers:575:11)
      at process.processTimers (node:internal/timers:514:7) {
    code: 'ERR_SOCKET_CONNECTION_TIMEOUT'
  }
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant