🐛 BUG: `npx wrangler tail` Command Fails with ETIMEDOUT Errors

[laamalif]

Which Cloudflare product(s) does this pertain to?

Wrangler

What version(s) of the tool(s) are you using?

3.72.0

What version of Node are you using?

v20.16.0

What operating system and version are you using?

Debian GNU/Linux 12 (bookworm)

Describe the Bug

Observed behavior

When running the npx wrangler tail command using wrangler version 3.72.0, the command fails with an ETIMEDOUT error. The command initially starts successfully and creates a tail, but then immediately throws an error and terminates.

Expected behavior

The npx wrangler tail command should create a tail and allow monitoring of logs without errors.

Steps to reproduce

Please provide the following:

• Minimal Working Subset of Worker Code:

  // Example worker code
  export default {
    async fetch(request) {
      return new Response('Hello, world!');
    },
  };
  
  

Actual Behavior

Successfully created tail, expires at 2024-08-19T19:19:46Z
/home/user/project/node_modules/wrangler/wrangler-dist/cli.js:29768
           throw a;
           ^

AggregateError [ETIMEDOUT]: 
   at internalConnectMultiple (node:net:1118:18)
   at afterConnectMultiple (node:net:1685:7)
Emitted 'error' event on WebSocket instance at:
   at emitErrorAndClose (/home/user/project/node_modules/wrangler/wrangler-dist/cli.js:147568:17)
   at ClientRequest.<anonymous> (/home/user/project/node_modules/wrangler/wrangler-dist/cli.js:147462:9)
   at ClientRequest.emit (node:events:519:28)
   at ClientRequest.emit (node:domain:488:12)
   at TLSSocket.socketErrorListener (node:_http_client:500:9)
   at TLSSocket.emit (node:events:519:28)
   at TLSSocket.emit (node:domain:488:12)
   at emitErrorNT (node:internal/streams/destroy:169:8)
   at emitErrorCloseNT (node:internal/streams/destroy:128:3)
   at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
 code: 'ETIMEDOUT',
 [errors]: [
   Error: connect ETIMEDOUT 104.21.5.179:443
       at createConnectionError (node:net:1648:14)
       at Timeout.internalConnectMultipleTimeout (node:net:1707:38)
       at listOnTimeout (node:internal/timers:583:11)
       at process.processTimers (node:internal/timers:519:7) {
     errno: -110,
     code: 'ETIMEDOUT',
     syscall: 'connect',
     address: '104.21.5.179',
     port: 443
   },
   Error: connect ETIMEDOUT 2606:4700:3036::6815:5b3:443
       at createConnectionError (node:net:1648:14)
       at Timeout.internalConnectMultipleTimeout (node:net:1707:38)
       at listOnTimeout (node:internal/timers:583:11)
       at process.processTimers (node:internal/timers:519:7) {
     errno: -110,
     code: 'ETIMEDOUT',
     syscall: 'connect',
     address: '2606:4700:3036::6815:5b3',
     port: 443
   },
   Error: connect ETIMEDOUT 172.67.133.177:443
       at createConnectionError (node:net:1648:14)
       at Timeout.internalConnectMultipleTimeout (node:net:1707:38)
       at listOnTimeout (node:internal/timers:583:11)
       at process.processTimers (node:internal/timers:519:7) {
     errno: -110,
     code: 'ETIMEDOUT',
     syscall: 'connect',
     address: '172.67.133.177',
     port: 443
   },
   Error: connect ETIMEDOUT 2606:4700:3034::ac43:85b1:443
       at createConnectionError (node:net:1648:14)
       at afterConnectMultiple (node:net:1678:16) {
     errno: -110,
     code: 'ETIMEDOUT',
     syscall: 'connect',
     address: '2606:4700:3034::ac43:85b1',
     port: 443
   }
 ]
}

Node.js v20.16.0

The error appears to be related to timeouts while attempting to connect to various IP addresses. Any guidance or fixes for this issue would be greatly appreciated.

Please provide a link to a minimal reproduction

No response

Please provide any relevant error logs

No response

[penalosa]

Do you have a proxy/VPN set up? If so, could you try without, and see if it works then?

[laamalif]

No, I don't have a VPN or proxy set up. It was working flawlessly a few weeks ago, but now I'm encountering the same issue consistently. I've tried troubleshooting, but I keep getting the same error with the same IP and API token.

[RamIdeas]

Hi @laamalif! Can you please confirm whether you are able to hit the Cloudflare API from your network/machine? One way to confirm this would be to deploy a worker. This will narrow down whether it is a network issue or something else

[laamalif]

The deployment generally works fine, although it occasionally encounters errors. After a few tries, I'm usually able to deploy successfully. However, I'm experiencing issues with npx wrangler tail —it consistently fails for me.

[andyjessop]

Could you provide us with an example of the errors that you're seeing. This looks like network issues, but it would be good to make sure!

[laamalif]

I encountered a timeout error when attempting to use wrangler tail after successfully deploying a Cloudflare Worker with npx wrangler deploy. Below are the detailed steps and error logs.

Deployed the worker using the command npx wrangler deploy

wrangler@darkstar:~/cf-llama $ npx wrangler deploy
⛅️ wrangler 3.78.2 (update available 3.78.3)
-------------------------------------------------------

Total Upload: 5.96 KiB / gzip: 2.33 KiB
Your worker has access to the following bindings:
- AI:
  - Name: AI
Uploaded cf-llama (6.74 sec)
Deployed cf-llama triggers (0.83 sec)
  https://cf-llama.darkstar-997.workers.dev
Current Version ID: f1e20095-b8cc-4c58-970d-f36f411907c9

Immediately after running npx wrangler tail, I encountered the following error:

wrangler@darkstar:~/cf-llama $ npx wrangler tail

 ⛅️ wrangler 3.78.2 (update available 3.78.3)
-------------------------------------------------------

Successfully created tail, expires at 2024-09-17T19:35:39Z
/home/user/cf-llama/node_modules/wrangler/wrangler-dist/cli.js:29768
            throw a;
            ^

AggregateError [ETIMEDOUT]: 
    at internalConnectMultiple (node:net:1118:18)
    at afterConnectMultiple (node:net:1685:7)
Emitted 'error' event on WebSocket instance at:
    at emitErrorAndClose (/home/user/cf-llama/node_modules/wrangler/wrangler-dist/cli.js:147802:17)
    at ClientRequest.<anonymous> (/home/user/cf-llama/node_modules/wrangler/wrangler-dist/cli.js:147696:9)
    at ClientRequest.emit (node:events:519:28)
    at ClientRequest.emit (node:domain:488:12)
    at emitErrorEvent (node:_http_client:108:11)
    at TLSSocket.socketErrorListener (node:_http_client:511:5)
    at TLSSocket.emit (node:events:519:28)
    at TLSSocket.emit (node:domain:488:12)
    at emitErrorNT (node:internal/streams/destroy:169:8)
    at emitErrorCloseNT (node:internal/streams/destroy:128:3) {
  code: 'ETIMEDOUT',
  [errors]: [
    Error: connect ETIMEDOUT 104.21.5.179:443
        at createConnectionError (node:net:1648:14)
        at Timeout.internalConnectMultipleTimeout (node:net:1707:38)
        at listOnTimeout (node:internal/timers:583:11)
        at process.processTimers (node:internal/timers:519:7) {
      errno: -110,
      code: 'ETIMEDOUT',
      syscall: 'connect',
      address: '104.21.5.179',
      port: 443
    },
    Error: connect ETIMEDOUT 2606:4700:3036::6815:5b3:443
        at createConnectionError (node:net:1648:14)
        at Timeout.internalConnectMultipleTimeout (node:net:1707:38)
        at listOnTimeout (node:internal/timers:583:11)
        at process.processTimers (node:internal/timers:519:7) {
      errno: -110,
      code: 'ETIMEDOUT',
      syscall: 'connect',
      address: '2606:4700:3036::6815:5b3',
      port: 443
    },
    Error: connect ETIMEDOUT 172.67.133.177:443
        at createConnectionError (node:net:1648:14)
        at Timeout.internalConnectMultipleTimeout (node:net:1707:38)
        at listOnTimeout (node:internal/timers:583:11)
        at process.processTimers (node:internal/timers:519:7) {
      errno: -110,
      code: 'ETIMEDOUT',
      syscall: 'connect',
      address: '172.67.133.177',
      port: 443
    },
    Error: connect ETIMEDOUT 2606:4700:3034::ac43:85b1:443
        at createConnectionError (node:net:1648:14)
        at afterConnectMultiple (node:net:1678:16) {
      errno: -110,
      code: 'ETIMEDOUT',
      syscall: 'connect',
      address: '2606:4700:3034::ac43:85b1',
      port: 443
    }
  ]
}

Node.js v20.17.0

[penalosa]

I've forwarded this to the team responsible for the wrangler tail infrastructure to take a look

[Jaden024]

I've forwarded this to the team responsible for the wrangler tail infrastructure to take a look

I have the same issue and for me following that guide: https://developers.cloudflare.com/workers/get-started/guide/ Made a deployment that has errors in it.

[lrapoport-cf]

WC-2930 cc @korinne

[lrapoport-cf]

hi @laamalif :) in an effort to remove stale issues so we can have better signal on current friction points, we’re closing out issues that have not been updated within the last 6 months. if this is still a problem, please feel free to open a new issue referencing this one, and please be sure to include an updated summary and any additional context and we will review. thank you!