workers-sdk icon indicating copy to clipboard operation
workers-sdk copied to clipboard
verified publisher icon cloudflare

🐛 BUG: wrangler dev -> fetch failed

Open ashab96 opened this issue 2 years ago • 21 comments

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 avatar May 02 '23 11:05 ashab96

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

    #2847 #3129

AsathalMannan avatar May 06 '23 09:05 AsathalMannan

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`

AsathalMannan avatar May 06 '23 10:05 AsathalMannan 

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.

FantasqueX avatar May 06 '23 16:05 FantasqueX

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/[email protected]/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/[email protected]/node_modules/wrangler/wrangler-dist/cli.js:120876:10)
      at async fetchInternal
  (/Users/jbergstroem/wrk/enc/a/node_modules/.pnpm/[email protected]/node_modules/wrangler/wrangler-dist/cli.js:120886:20)
      at async fetchResult
  (/Users/jbergstroem/wrk/enc/a/node_modules/.pnpm/[email protected]/node_modules/wrangler/wrangler-dist/cli.js:121029:16)
      at async createPreviewSession
  (/Users/jbergstroem/wrk/enc/a/node_modules/.pnpm/[email protected]/node_modules/wrangler/wrangler-dist/cli.js:128422:28)
      at async start
  (/Users/jbergstroem/wrk/enc/a/node_modules/.pnpm/[email protected]/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] ]
    }
  }

jbergstroem avatar May 30 '23 16:05 jbergstroem

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?

admah avatar Jun 07 '23 20:06 admah

3.1.1 same error

zhiqingchen avatar Jun 27 '23 12:06 zhiqingchen

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.

jbergstroem avatar Jul 01 '23 13:07 jbergstroem

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

bcjordan avatar Jul 09 '23 15:07 bcjordan

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

Rhahkeem avatar Aug 22 '23 22:08 Rhahkeem

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

giorgiogross avatar Aug 30 '23 11:08 giorgiogross

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

bwkam avatar Sep 08 '23 20:09 bwkam

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

Rhahkeem avatar Sep 10 '23 22:09 Rhahkeem

maybe related: https://github.com/cloudflare/workers-sdk/issues/3925

205g0 avatar Sep 11 '23 13:09 205g0

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

lrapoport-cf avatar Sep 15 '23 18:09 lrapoport-cf

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 avatar Oct 02 '23 16:10 mrbbot

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

NachoVazquez avatar Oct 10 '23 16:10 NachoVazquez

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.

205g0 avatar Oct 17 '23 09:10 205g0

I got the same error in windows wsl2

maojindao55 avatar Oct 18 '23 15:10 maojindao55

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). 👍

mrbbot avatar Nov 16 '23 13:11 mrbbot

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

lrapoport-cf avatar Jan 29 '24 17:01 lrapoport-cf

We decided to implement https://github.com/cloudflare/workers-sdk/pull/5214 instead of https://github.com/cloudflare/workers-sdk/pull/4241. This is available behind a flag --x-registry. Can you give this a try or report whether you are still experiencing these issues?

petebacondarwin avatar Jul 01 '24 09:07 petebacondarwin

We haven't heard from you in while so I'm going to close this issue for now. If you're still running into problems feel free to comment with more details and we can investigate further.

penalosa avatar Oct 24 '24 11:10 penalosa

Same error for me. Started brand new project, deployed it and ran the command. Ubuntu 22.04.4 LTS. Node v20.12.2

npm create cloudflare@latest -- alpha
npx wrangler deploy
npx wrangler dev --remote

Did anyone find a fix for it?

zaharzagrava avatar Nov 27 '24 15:11 zaharzagrava

@zaharzagrava could you open a new issue with details? e.g. Wrangler version etc...

penalosa avatar Nov 27 '24 15:11 penalosa

@penalosa https://github.com/cloudflare/workers-sdk/issues/7371

zaharzagrava avatar Nov 27 '24 15:11 zaharzagrava