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

🐛 BUG: wrangler dev -> fetch failed #3121

Open
ashab96 opened this issue May 2, 2023 · 21 comments
Open

🐛 BUG: wrangler dev -> fetch failed #3121

ashab96 opened this issue May 2, 2023 · 21 comments
Assignees
Labels
bug Something that isn't working quick win Potentially easy/straightforward issue to tackle

Comments

@ashab96
Copy link

ashab96 commented May 2, 2023

Which Cloudflare product(s) does this pertain to?

Workers/Other, Wrangler

What version of Wrangler are you using?

2.18.0

What operating system are you using?

Windows

Describe the Bug

Whenever I run "wrangler dev" I get the following error:

[ERROR] Error while creating remote dev session: TypeError: fetch failed

at fetch
(\my-test-api\node_modules\wrangler\wrangler-dist\cli.js:16584:17)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async createPreviewSession
(\my-test-api\node_modules\wrangler\wrangler-dist\cli.js:132585:28)
at async start
(\my-test-api\node_modules\wrangler\wrangler-dist\cli.js:151229:9)
{
cause: ConnectTimeoutError: Connect Timeout Error
at onConnectTimeout
(\my-test-api\node_modules\wrangler\wrangler-dist\cli.js:7185:29)
at
\my-test-api\node_modules\wrangler\wrangler-dist\cli.js:7141:51
at Immediate._onImmediate
(\my-test-api\node_modules\wrangler\wrangler-dist\cli.js:7171:37)
at process.processImmediate (node:internal/timers:476:21) {
code: 'UND_ERR_CONNECT_TIMEOUT'
}
}

This is a brand new project with wrangler init, but when I ran wrangler dev it had the same error.
Project has only the initial project changes nothing has been modified after the project is created .
with -l local run is fine.

@ashab96 ashab96 added the bug Something that isn't working label May 2, 2023
@ashab96 ashab96 changed the title 🐛 BUG: 🐛 BUG: wrangler dev -> fetch failed May 2, 2023
@AsathalMannan
Copy link

AsathalMannan commented May 6, 2023

Same Error, stopping me..!
Tried in, Windows 10 and Fedora, same error
Wrangler installed using Volta

` ⛅️ wrangler 2.19.0

Using vars defined in .dev.vars
Your worker has access to the following bindings:

  • Vars:

    • COSMOS_ENDPOINT: "(hidden)"
    • COSMOS_KEY: "(hidden)"
    • PRIVKEY: "(hidden)"
      ⬣ Listening at https://0.0.0.0:8787
  • https://192.168.29.145:8787

  • https://127.0.0.1:8787
    X [ERROR] Error while creating remote dev session: TypeError: fetch failed

    at fetch
    

    (C:\Users\mannan\AppData\Local\Volta\tools\image\packages\wrangler\node_modules\wrangler\wrangler-dist\cli.js:16584:17)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async createPreviewSession
    (C:\Users\mannan\AppData\Local\Volta\tools\image\packages\wrangler\node_modules\wrangler\wrangler-dist\cli.js:132590:28)
    at async start
    (C:\Users\mannan\AppData\Local\Volta\tools\image\packages\wrangler\node_modules\wrangler\wrangler-dist\cli.js:151632:9)
    {
    cause: ConnectTimeoutError: Connect Timeout Error
    at onConnectTimeout
    (C:\Users\mannan\AppData\Local\Volta\tools\image\packages\wrangler\node_modules\wrangler\wrangler-dist\cli.js:7185:29)
    at
    C:\Users\mannan\AppData\Local\Volta\tools\image\packages\wrangler\node_modules\wrangler\wrangler-dist\cli.js:7141:51
    at Immediate._onImmediate
    (C:\Users\mannan\AppData\Local\Volta\tools\image\packages\wrangler\node_modules\wrangler\wrangler-dist\cli.js:7171:37)
    at process.processImmediate (node:internal/timers:476:21) {
    code: 'UND_ERR_CONNECT_TIMEOUT'
    }
    }`

    🐛 BUG: TypeError: fetch failed  #2847
    🐛 BUG: #3129

@AsathalMannan
Copy link

Same "wrangler tail" command also failing.
tried re-installing wrangler, but still error throwing..!

` ⛅️ wrangler 2.19.0

Successfully created tail, expires at 2023-05-06T15:47:28Z
C:\Users\mannan\AppData\Local\Volta\tools\image\packages\wrangler\node_modules\wrangler\wrangler-dist\cli.js:30488
throw a;
^

Error: connect ETIMEDOUT 2606:4700:9c6e:c702:81dd:2d8:7328:5b4d:443
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1494:16)
Emitted 'error' event on WebSocket instance at:
at emitErrorAndClose (C:\Users\mannan\AppData\Local\Volta\tools\image\packages\wrangler\node_modules\wrangler\wrangler-dist\cli.js:102732:17)
at ClientRequest. (C:\Users\mannan\AppData\Local\Volta\tools\image\packages\wrangler\node_modules\wrangler\wrangler-dist\cli.js:102637:9) at ClientRequest.emit (node:events:513:28)
at TLSSocket.socketErrorListener (node:_http_client:502:9)
at TLSSocket.emit (node:events:513:28)
at emitErrorNT (node:internal/streams/destroy:151:8)
at emitErrorCloseNT (node:internal/streams/destroy:116:3)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
errno: -4039,
code: 'ETIMEDOUT',
syscall: 'connect',
address: '2606:4700:9c6e:c702:81dd:2d8:7328:5b4d',
port: 443
}

Node.js v18.16.0`

@FantasqueX
Copy link

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)
Emitted 'error' event on ClientHttp2Session instance at:
    at emitClose (node:internal/http2/core:1086:10)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  code: 'ERR_SOCKET_CONNECTION_TIMEOUT'
}

Node.js v20.1.0
 ELIFECYCLE  Command failed with exit code 7.

Failed with nodejs v20.

@jbergstroem
Copy link

I get this multiple times a day when doing remote workers. I have to restart a few times for it to work. It's been around for a while.

✘ [ERROR] Error while creating remote dev session: TypeError: fetch failed

      at fetch
  (/Users/jbergstroem/wrk/enc/a/node_modules/.pnpm/wrangler@3.0.1/node_modules/wrangler/wrangler-dist/cli.js:16584:17)
      at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
      at async performApiFetch
  (/Users/jbergstroem/wrk/enc/a/node_modules/.pnpm/wrangler@3.0.1/node_modules/wrangler/wrangler-dist/cli.js:120876:10)
      at async fetchInternal
  (/Users/jbergstroem/wrk/enc/a/node_modules/.pnpm/wrangler@3.0.1/node_modules/wrangler/wrangler-dist/cli.js:120886:20)
      at async fetchResult
  (/Users/jbergstroem/wrk/enc/a/node_modules/.pnpm/wrangler@3.0.1/node_modules/wrangler/wrangler-dist/cli.js:121029:16)
      at async createPreviewSession
  (/Users/jbergstroem/wrk/enc/a/node_modules/.pnpm/wrangler@3.0.1/node_modules/wrangler/wrangler-dist/cli.js:128422:28)
      at async start
  (/Users/jbergstroem/wrk/enc/a/node_modules/.pnpm/wrangler@3.0.1/node_modules/wrangler/wrangler-dist/cli.js:147762:9)
  {
    cause: AggregateError
        at internalConnectMultiple (node:net:1103:18)
        at internalConnectMultiple (node:net:1161:5)
        at internalConnectMultiple (node:net:1161:5)
        at Timeout.internalConnectMultipleTimeout (node:net:1638:3)
        at listOnTimeout (node:internal/timers:575:11)
        at process.processTimers (node:internal/timers:514:7) {
      code: 'EHOSTUNREACH',
      [errors]: [ [Error], [Error] ]
    }
  }

@admah
Copy link
Contributor

admah commented Jun 7, 2023

Hello. PM for the Wrangler team 👋 I have a few questions about this issue that would be really helpful to get answers to:

  • Does this happen on never versions of Wrangler as well? Could you try with a more recent version than 2.19?
  • Does this happen only when using wrangler dev for remote development?
  • Has anyone seen these issues in v3?

@1000hz 1000hz added awaiting reporter response Needs clarification or followup from OP and removed bucket:avocado labels Jun 26, 2023
@zhiqingchen
Copy link

3.1.1 same error

@jbergstroem
Copy link

jbergstroem commented Jul 1, 2023

Has anyone seen these issues in v3?

My traceback above your comment shows me using wrangler 3.0.1. I see this in 3.1.0 occasionally too. Yet to try 3.1.1.

Does this happen only when using wrangler dev for remote development?

This mostly happens when I am in local development and switching to remote.

@bcjordan
Copy link

bcjordan commented Jul 9, 2023

Seeing this both running deploy or dev/switching to remote. Was deploying multiple projects for an hour perfectly fine

@lrapoport-cf lrapoport-cf added awaiting Cloudflare response Awaiting response from workers-sdk maintainer team and removed awaiting reporter response Needs clarification or followup from OP labels Jul 31, 2023
@Rhahkeem
Copy link

Rhahkeem commented Aug 22, 2023

So I suddenly started getting this which is weird because I dont recall changing anything. One second it wasn't there and suddenly it was

$ npx wrangler dev
wrangler dev now uses local mode by default, powered by 🔥 Miniflare and 👷 workerd.
To run an edge preview session for your Worker, use wrangler dev --remote
Using vars defined in .dev.vars
Your worker has access to the following bindings:
- Vars:
  - WISE_TOKEN: "(hidden)"
  - VERBOSE: "(hidden)"
⎔ Starting local server...
[mf:inf] Ready on http://127.0.0.1:8787/
✘ [ERROR] Failed to register worker in local service registry TypeError: fetch failed

      at fetch
  (/home/rhahkeem/Code/wrangler/lifestuff-web/node_modules/wrangler/wrangler-dist/cli.js:16584:17)
      at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
      at async registerWorker
  (/home/rhahkeem/Code/wrangler/lifestuff-web/node_modules/wrangler/wrangler-dist/cli.js:126327:12)
      at async MiniflareServer.<anonymous>
  (/home/rhahkeem/Code/wrangler/lifestuff-web/node_modules/wrangler/wrangler-dist/cli.js:127987:9) {
    cause: ConnectTimeoutError: Connect Timeout Error
        at onConnectTimeout
  (/home/rhahkeem/Code/wrangler/lifestuff-web/node_modules/wrangler/wrangler-dist/cli.js:7185:29)
        at
  /home/rhahkeem/Code/wrangler/lifestuff-web/node_modules/wrangler/wrangler-dist/cli.js:7141:51
        at Immediate._onImmediate
  (/home/rhahkeem/Code/wrangler/lifestuff-web/node_modules/wrangler/wrangler-dist/cli.js:7173:13)
        at process.processImmediate (node:internal/timers:476:21) {
      code: 'UND_ERR_CONNECT_TIMEOUT'
    }
  }


▲ [WARNING] Failed to get worker definitions TypeError: fetch failed

      at fetch
  (/home/rhahkeem/Code/wrangler/lifestuff-web/node_modules/wrangler/wrangler-dist/cli.js:16584:17)
      at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
      at async getRegisteredWorkers
  (/home/rhahkeem/Code/wrangler/lifestuff-web/node_modules/wrangler/wrangler-dist/cli.js:126361:22)
      at async getBoundRegisteredWorkers
  (/home/rhahkeem/Code/wrangler/lifestuff-web/node_modules/wrangler/wrangler-dist/cli.js:126380:29)
  {
    cause: ConnectTimeoutError: Connect Timeout Error
        at onConnectTimeout
  (/home/rhahkeem/Code/wrangler/lifestuff-web/node_modules/wrangler/wrangler-dist/cli.js:7185:29)
        at
  /home/rhahkeem/Code/wrangler/lifestuff-web/node_modules/wrangler/wrangler-dist/cli.js:7141:51
        at Immediate._onImmediate
  (/home/rhahkeem/Code/wrangler/lifestuff-web/node_modules/wrangler/wrangler-dist/cli.js:7173:13)
        at process.processImmediate (node:internal/timers:476:21) {
      code: 'UND_ERR_CONNECT_TIMEOUT'
    }
  }

Using ⛅️ wrangler 3.5.1

@giorgiogross
Copy link

giorgiogross commented Aug 30, 2023

Same here, happens when starting, reloading and exiting, with ⛅️ wrangler 3.6.0:

Start

✘ [ERROR] Failed to register worker in local service registry TypeError: fetch failed

      at fetch
  (/Users/giorgio/Projects/BB/backend/cloudflare/functions/create-resource/node_modules/wrangler/wrangler-dist/cli.js:16584:17)
      at process.processTicksAndRejections
  (node:internal/process/task_queues:95:5)
      at async registerWorker
  (/Users/giorgio/Projects/BB/backend/cloudflare/functions/create-resource/node_modules/wrangler/wrangler-dist/cli.js:126327:12)
      at async MiniflareServer.<anonymous>
  (/Users/giorgio/Projects/BB/backend/cloudflare/functions/create-resource/node_modules/wrangler/wrangler-dist/cli.js:127987:9)
  {
    cause: ConnectTimeoutError: Connect Timeout Error
        at onConnectTimeout
  (/Users/giorgio/Projects/BB/backend/cloudflare/functions/create-resource/node_modules/wrangler/wrangler-dist/cli.js:7185:29)
        at
  /Users/giorgio/Projects/BB/backend/cloudflare/functions/create-resource/node_modules/wrangler/wrangler-dist/cli.js:7141:51
        at Immediate._onImmediate
  (/Users/giorgio/Projects/BB/backend/cloudflare/functions/create-resource/node_modules/wrangler/wrangler-dist/cli.js:7173:13)
        at process.processImmediate (node:internal/timers:476:21) {
      code: 'UND_ERR_CONNECT_TIMEOUT'
    }
  }

▲ [WARNING] Failed to get worker definitions TypeError: fetch failed

      at fetch
  (/Users/giorgio/Projects/BB/backend/cloudflare/functions/create-resource/node_modules/wrangler/wrangler-dist/cli.js:16584:17)
      at process.processTicksAndRejections
  (node:internal/process/task_queues:95:5)
      at async getRegisteredWorkers
  (/Users/giorgio/Projects/BB/backend/cloudflare/functions/create-resource/node_modules/wrangler/wrangler-dist/cli.js:126361:22)
      at async getBoundRegisteredWorkers
  (/Users/giorgio/Projects/BB/backend/cloudflare/functions/create-resource/node_modules/wrangler/wrangler-dist/cli.js:126380:29)
  {
    cause: ConnectTimeoutError: Connect Timeout Error
        at onConnectTimeout
  (/Users/giorgio/Projects/BB/backend/cloudflare/functions/create-resource/node_modules/wrangler/wrangler-dist/cli.js:7185:29)
        at
  /Users/giorgio/Projects/BB/backend/cloudflare/functions/create-resource/node_modules/wrangler/wrangler-dist/cli.js:7141:51
        at Immediate._onImmediate
  (/Users/giorgio/Projects/BB/backend/cloudflare/functions/create-resource/node_modules/wrangler/wrangler-dist/cli.js:7173:13)
        at process.processImmediate (node:internal/timers:476:21) {
      code: 'UND_ERR_CONNECT_TIMEOUT'
    }
  }

Reload:

[mf:inf] Updated and ready on http://127.0.0.1:8787/
✘ [ERROR] Failed to register worker in local service registry TypeError: fetch failed

      at fetch
  (/Users/giorgio/Projects/BB/backend/cloudflare/functions/create-resource/node_modules/wrangler/wrangler-dist/cli.js:16584:17)
      at process.processTicksAndRejections
  (node:internal/process/task_queues:95:5)
      at async registerWorker
  (/Users/giorgio/Projects/BB/backend/cloudflare/functions/create-resource/node_modules/wrangler/wrangler-dist/cli.js:126327:12)
      at async MiniflareServer.<anonymous>
  (/Users/giorgio/Projects/BB/backend/cloudflare/functions/create-resource/node_modules/wrangler/wrangler-dist/cli.js:127987:9)
  {
    cause: ConnectTimeoutError: Connect Timeout Error
        at onConnectTimeout
  (/Users/giorgio/Projects/BB/backend/cloudflare/functions/create-resource/node_modules/wrangler/wrangler-dist/cli.js:7185:29)
        at
  /Users/giorgio/Projects/BB/backend/cloudflare/functions/create-resource/node_modules/wrangler/wrangler-dist/cli.js:7141:51
        at Immediate._onImmediate
  (/Users/giorgio/Projects/BB/backend/cloudflare/functions/create-resource/node_modules/wrangler/wrangler-dist/cli.js:7173:13)
        at process.processImmediate (node:internal/timers:476:21) {
      code: 'UND_ERR_CONNECT_TIMEOUT'
    }
  }

Exiting:

✘ [ERROR] Failed to unregister worker TypeError: fetch failed

      at fetch
  (/Users/giorgio/Projects/BB/backend/cloudflare/functions/create-resource/node_modules/wrangler/wrangler-dist/cli.js:16584:17)
      at process.processTicksAndRejections
  (node:internal/process/task_queues:95:5)
      at async unregisterWorker
  (/Users/giorgio/Projects/BB/backend/cloudflare/functions/create-resource/node_modules/wrangler/wrangler-dist/cli.js:126347:5)
      at async Promise.allSettled (index 0) {
    cause: ConnectTimeoutError: Connect Timeout Error
        at onConnectTimeout
  (/Users/giorgio/Projects/BB/backend/cloudflare/functions/create-resource/node_modules/wrangler/wrangler-dist/cli.js:7185:29)
        at
  /Users/giorgio/Projects/BB/backend/cloudflare/functions/create-resource/node_modules/wrangler/wrangler-dist/cli.js:7141:51
        at Immediate._onImmediate
  (/Users/giorgio/Projects/BB/backend/cloudflare/functions/create-resource/node_modules/wrangler/wrangler-dist/cli.js:7173:13)
        at process.processImmediate (node:internal/timers:476:21) {
      code: 'UND_ERR_CONNECT_TIMEOUT'
    }
  }

@bwkam
Copy link

bwkam commented Sep 8, 2023

same, and it's so damn annoying. I have to restart the server endless times until I finally get it working.
wrangler 3.6.0

@admah admah removed the awaiting Cloudflare response Awaiting response from workers-sdk maintainer team label Sep 8, 2023
@Rhahkeem
Copy link

As quickly as it's come it's somehow gone. I havent done anything (possibly a restart?) but now I no longer get the trace

@205g0
Copy link

205g0 commented Sep 11, 2023

maybe related: #3925

@lrapoport-cf
Copy link
Contributor

hi @ashab96 :) are you using a VPN or proxy when you encounter the issue?

@lrapoport-cf lrapoport-cf added the awaiting reporter response Needs clarification or followup from OP label Sep 15, 2023
@mrbbot
Copy link
Contributor

mrbbot commented Oct 2, 2023

Hey everyone! 👋 As an update, we've identified a potential cause for the errors that are coming from the service registry (Failed to register worker in local service registry, Failed to get worker definitions, Failed to unregister worker) and will aim to get a fix out in the next few weeks. 👍

@mrbbot mrbbot added the quick win Potentially easy/straightforward issue to tackle label Oct 2, 2023
@lrapoport-cf lrapoport-cf removed the awaiting reporter response Needs clarification or followup from OP label Oct 2, 2023
@NachoVazquez
Copy link

Thanks, @mrbbot. I'm getting this now after updating to version 3.11.0.

I'm a library maintainer providing a plugin that gives Cloudflare (Wrangler) support to Nx monorepos.

Is this a problem all users are facing or only a few? I'm asking if it is safe to update my package to the latest version of Wrangler.

Thanks

@205g0
Copy link

205g0 commented Oct 17, 2023

FWIW, I just got following multiple times after setting up a new dev machine:

✘ [ERROR] Error: Could not proxy request: TypeError: fetch failed

      at
  /home/user/.nvm/versions/node/v18.18.2/lib/node_modules/wrangler/wrangler-dist/cli.js:110586:29
      at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
      at async #handleLoopbackCustomService
  (/home/user/.nvm/versions/node/v18.18.2/lib/node_modules/wrangler/node_modules/miniflare/dist/src/index.js:7560:24)
      at async #handleLoopback
  (/home/user/.nvm/versions/node/v18.18.2/lib/node_modules/wrangler/node_modules/miniflare/dist/src/index.js:7604:20)

I have WSL2, latest wrangler and...

After I did a manual DNS setting (either 1.1.1.1 or 8.8.8.8), a wsl --shutdown and restart, the error went away:

Don't have this problem with any other service.

@maojindao55
Copy link

I got the same error in windows wsl2

@lrapoport-cf lrapoport-cf added the blocked Blocked on other work label Nov 10, 2023
@mrbbot
Copy link
Contributor

mrbbot commented Nov 16, 2023

As a quick update for people following this issue, we have a PR that could fix this problem in most cases (#4241), but we're going to hold off merging it until some other work to rearchitect Wrangler-as-a-library is complete (#4413). 👍

@lrapoport-cf lrapoport-cf removed the blocked Blocked on other work label Nov 27, 2023
@lrapoport-cf lrapoport-cf added the start-dev-worker Relating to the startDevWorker API label Jan 29, 2024
@lrapoport-cf
Copy link
Contributor

per @mrbbot 's previous comment, moved this to backlog to revisit later

@lrapoport-cf lrapoport-cf removed the start-dev-worker Relating to the startDevWorker API label Feb 1, 2024
@petebacondarwin
Copy link
Contributor

We decided to implement #5214 instead of #4241. This is available behind a flag --x-registry.
Can you give this a try or report whether you are still experiencing these issues?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something that isn't working quick win Potentially easy/straightforward issue to tackle
Projects
Status: Backlog
Development

No branches or pull requests