cloudflared icon indicating copy to clipboard operation
cloudflared copied to clipboard
verified publisher icon cloudflare

🐛context canceled

Open JamCh01 opened this issue 11 months ago • 25 comments

Describe the bug A clear and concise description of what the bug is.

To Reproduce Steps to reproduce the behavior:

  1. Configure 'from zero trust web'
  2. Run 'cloudflared service install xxx'
  3. See error

If it's an issue with Cloudflare Tunnel: 4. Tunnel ID : 7780c9b2-6203-4019-80dd-5ebb036f9c01 5. cloudflared config:

Expected behavior A clear and concise description of what you expected to happen.

Environment and versions

  • OS: [e.g. MacOS] Linux Debian12
  • Architecture: [e.g. AMD, ARM] AMD
  • Version: [e.g. 2022.02.0] cloudflared version 2024.12.2 (built 2024-12-19-1724 UTC)

Logs and errors If applicable, add logs or errors to help explain your problem.

Dec 27 23:08:00 myhost cloudflared[514341]: 2024-12-27T23:08:00Z INF Starting tunnel tunnelID=7780c9b2-6203-4019-80dd-5ebb036f9c01
Dec 27 23:08:00 myhost cloudflared[514341]: 2024-12-27T23:08:00Z INF Version 2024.12.2 (Checksum 5237675a5e806120729acc78c5be02f9db5f406717699587abfa72b49b39fe40)
Dec 27 23:08:00 myhost cloudflared[514341]: 2024-12-27T23:08:00Z INF GOOS: linux, GOVersion: go1.22.5, GoArch: amd64
Dec 27 23:08:00 myhost cloudflared[514341]: 2024-12-27T23:08:00Z INF Settings: map[no-autoupdate:true token:*****]
Dec 27 23:08:00 myhost cloudflared[514341]: 2024-12-27T23:08:00Z INF cloudflared will not automatically update if installed by a package manager.
Dec 27 23:08:00 myhost cloudflared[514341]: 2024-12-27T23:08:00Z INF Generated Connector ID: 47572931-db89-4e43-a61c-88a6d6b7d792
Dec 27 23:08:00 myhost cloudflared[514341]: 2024-12-27T23:08:00Z INF Initial protocol quic
Dec 27 23:08:00 myhost cloudflared[514341]: 2024-12-27T23:08:00Z INF ICMP proxy will use 45.*.*.34 as source for IPv4
Dec 27 23:08:00 myhost cloudflared[514341]: 2024-12-27T23:08:00Z INF ICMP proxy will use fe80::6e92:bfff:fe66:f04d in zone ens33f1 as source for IPv6
Dec 27 23:08:00 myhost cloudflared[514341]: 2024-12-27T23:08:00Z WRN The user running cloudflared process has a GID (group ID) that is not within ping_group_range. You might need to add that user to a group within that range, or instead update the range to encompass a g>Dec 27 23:08:00 myhost cloudflared[514341]: 2024-12-27T23:08:00Z WRN ICMP proxy feature is disabled error="cannot create ICMPv4 proxy: Group ID 0 is not between ping group 1 to 0 nor ICMPv6 proxy: socket: permission denied"
Dec 27 23:08:00 myhost cloudflared[514341]: 2024-12-27T23:08:00Z INF ICMP proxy will use 45.*.*.34 as source for IPv4
Dec 27 23:08:00 myhost cloudflared[514341]: 2024-12-27T23:08:00Z INF ICMP proxy will use fe80::6e92:bfff:fe66:f04d in zone ens33f1 as source for IPv6
Dec 27 23:08:00 myhost cloudflared[514341]: 2024-12-27T23:08:00Z INF Starting metrics server on 127.0.0.1:20241/metrics
Dec 27 23:08:00 myhost cloudflared[514341]: 2024-12-27T23:08:00Z ERR Failed to serve tunnel connection error="context canceled" connIndex=0 event=0 ip=198.41.192.77
Dec 27 23:08:00 myhost cloudflared[514341]: 2024-12-27T23:08:00Z INF Retrying connection in up to 2s connIndex=0 event=0 ip=198.41.192.77
Dec 27 23:08:02 myhost cloudflared[514341]: 2024-12-27T23:08:02Z INF Tunnel server stopped
Dec 27 23:08:02 myhost cloudflared[514341]: 2024-12-27T23:08:02Z ERR Initiating shutdown error="context canceled"
Dec 27 23:08:02 myhost cloudflared[514341]: 2024-12-27T23:08:02Z INF Metrics server stopped
Dec 27 23:08:02 myhost cloudflared[514341]: context canceled

Additional context Add any other context about the problem here.

JamCh01 avatar Dec 27 '24 23:12 JamCh01

I've the same problem...

winefox avatar Jan 18 '25 23:01 winefox

I have the same issue. Did you ever resolve this?

paulmorabito avatar Jan 21 '25 15:01 paulmorabito

I don't remember why did it happen, but I googled this, and subscribed to this issue. And after rereading docs, and configuring it correctly to work with docker, problem was resolved. This answer might not be really helpful.

sequencerr avatar Jan 21 '25 20:01 sequencerr

I regenerated my token a few times and it worked. Random and weird.

paulmorabito avatar Jan 21 '25 20:01 paulmorabito

We are facing similar issue with Cloudflare Tunnel authentication in Kubernetes despite multiple attempts to refresh the tunnel token and redeploy cloudflared pods.

ERR Failed to serve tunnel connection error="context canceled" with latest cloudflared images

error="Unauthorized: Invalid tunnel secret" with older version of cloudflared images

We have refreshed the token, updated Kubernetes secrets, redeployed the pod, and restarted the deployment multiple times. However, the issue persists.

2025-02-20T22:51:13Z INF Starting tunnel tunnelID=b4678717-a506-447b-a969-cf47f37ffddb
2025-02-20T22:51:13Z INF Version 2025.2.0 (Checksum d7e573b235ef4a1cf45d6b837f61094e4a3403c4ef92e1281a8fec3f7f257691)
2025-02-20T22:51:13Z INF GOOS: linux, GOVersion: go1.22.5-devel-cf, GoArch: amd64
2025-02-20T22:51:13Z INF Settings: map[config:/opt/zt/config/config.yaml cred-file:/opt/zt/creds/creds.json credentials-file:/opt/zt/creds/creds.json metrics:0.0.0.0:8081 no-autoupdate:true]
2025-02-20T22:51:13Z INF Generated Connector ID: 7f3ce060-d6d2-4d90-8c5b-7fab25b114d8
2025-02-20T22:51:13Z WRN No ingress rules were defined in provided config (if any) nor from the cli, cloudflared will return 503 for all incoming HTTP requests
2025-02-20T22:51:13Z INF Initial protocol quic
2025-02-20T22:51:13Z INF ICMP proxy will use 192.168.87.84 as source for IPv4
2025-02-20T22:51:13Z INF ICMP proxy will use fe80::582f:bfff:fe14:6eb3 in zone eth0 as source for IPv6
2025-02-20T22:51:13Z WRN The user running cloudflared process has a GID (group ID) that is not within ping_group_range. You might need to add that user to a group within that range, or instead update the range to encompass a group the user is already in by modifying /proc/sys/net/ipv4/ping_group_range. Otherwise cloudflared will not be able to ping this network error="Group ID 65532 is not between ping group 1 to 0"
2025-02-20T22:51:13Z WRN ICMP proxy feature is disabled error="cannot create ICMPv4 proxy: Group ID 65532 is not between ping group 1 to 0 nor ICMPv6 proxy: socket: permission denied"
2025-02-20T22:51:13Z INF ICMP proxy will use 192.168.87.84 as source for IPv4
2025-02-20T22:51:13Z INF ICMP proxy will use fe80::582f:bfff:fe14:6eb3 in zone eth0 as source for IPv6
2025-02-20T22:51:13Z INF Starting metrics server on :8081/metrics
2025-02-20T22:51:13Z INF Using [CurveID(4588) CurveID(25497) CurveP256] as curve preferences connIndex=0 event=0 ip=198.41.192.227
2025-02-20T22:51:13Z ERR Failed to serve tunnel connection error="context canceled" connIndex=0 event=0 ip=198.41.192.227
2025-02-20T22:51:13Z INF Retrying connection in up to 2s connIndex=0 event=0 ip=198.41.192.227
2025-02-20T22:51:14Z INF Tunnel server stopped
2025-02-20T22:51:14Z ERR Initiating shutdown error="context canceled"
2025-02-20T22:51:14Z INF Metrics server stopped
context canceled
Stream closed EOF for zt/tunnel-api-zt-7565f9ccf4-6sbxq (tunnel)

When I check the tunnel status by running the command, the tunnel becomes active, but I am getting errors with the same token in Kubernetes.

sudo cloudflared service install <refreshed token>
Password:
2025-02-20T20:50:29Z INF Installing cloudflared client as a system launch daemon. cloudflared client will run at boot
2025-02-20T20:50:29Z INF Outputs are logged to /Library/Logs/com.cloudflare.cloudflared.err.log and /Library/Logs/com.cloudflare.cloudflared.out.log
2025-02-20T20:50:29Z INF MacOS service for cloudflared installed successfully

Deployment configuration as pper https://blog.cloudflare.com/kubectl-with-zero-trust/

apiVersion: apps/v1
kind: Deployment
metadata:
  labels:
    tunnel: api-zt
  name: tunnel-api-zt
  namespace: zt
spec:
  replicas: 3
  selector:
    matchLabels:
      tunnel: api-zt
  strategy:
    rollingUpdate:
      maxSurge: 0
      maxUnavailable: 1
  template:
    metadata:
      labels:
        tunnel: api-zt
    spec:
      containers:
        - args:
            - tunnel
            - --config
            - /opt/zt/config/config.yaml
            - run
          env:
            - name: GOMAXPROCS
              value: "2"
            - name: TZ
              value: UTC
          image: cloudflare/cloudflared:2022.5.3
          livenessProbe:
            failureThreshold: 1
            httpGet:
              path: /ready
              port: 8081
            initialDelaySeconds: 10
            periodSeconds: 10
          name: tunnel
          ports:
            - containerPort: 8081
              name: http-metrics
          resources:
            limits:
              cpu: "1"
              memory: 100Mi
          volumeMounts:
            - mountPath: /opt/zt/config
              name: config  
              readOnly: true
            - mountPath: /opt/zt/creds
              name: creds  
              readOnly: true
      volumes:
        - name: creds 
          secret:
            secretName: tunnel-creds
        - name: config 
          configMap:
            name: tunnel-zt

someshnesi avatar Feb 20 '25 12:02 someshnesi

I am also having the same issue running a Docker connector to my cloudflare tunnel. I've regenerated the token multiple times, am forcring http2 protocol, even tried setting up a new tunnel - all with the same results. And to note on the CloudFlare dashboard my tunnel will oscillate between Healthy -> Degraded -> Down and then back to Healthy again.

Image

Any update on this?

c00kiemonstr avatar Feb 24 '25 01:02 c00kiemonstr

Same issue here

2025-03-04T23:13:08Z ERR Failed to serve tunnel connection error="context canceled" connIndex=0 event=0 ip=198.41.200.193
2025-03-04T23:13:08Z INF Retrying connection in up to 1s connIndex=0 event=0 ip=198.41.200.193
[...]
2025-03-04T23:15:16Z ERR  error="context canceled" connIndex=3 event=1 ingressRule=0 originService=http://192.168.1.37:4533
2025-03-04T23:15:16Z ERR Request failed error="context canceled" connIndex=3 dest=https://xxx.mydomain.com/xxxx event=0 ip=198.41.192.77 type=http

Everything was working fine since 2 years, and I'm now facing connectivity issues using cloudflare tunnels

machintrucbidule avatar Mar 04 '25 23:03 machintrucbidule

I also noticed this error occurring, tested with the latest docker image and 2025.1.1 and both showed this error.
I regenerated my cloudflare token and restarted (on latest 2025.2.1) and still receive the error. Multiple connIndex's error the same:

cf  | 2025-03-06T13:50:32.044915305Z 2025-03-06T13:50:32Z ERR  error="context canceled" connIndex=3 event=1 ingressRule=0 originService=https://---------
cf  | 2025-03-06T13:50:32.044947649Z 2025-03-06T13:50:32Z ERR Request failed error="context canceled" connIndex=3 dest=https://example.com/path event=0 ip=--- type=http

timrettop avatar Mar 06 '25 13:03 timrettop

Multiple tunnel connections on multiple devices in multiple locations, tunnels running on hardware devices and VMs:

Image

All of my Cloudflare tunnels are down. HA included. No warning, and no amount of refreshing the token seems to fix the issue. This is now March 10 of 2025, using the latest (2025.2.1) pull of the tunnel connector and "cloudflare/cloudflared" as well. [Ignore the quic-go buffer issues, I'll get to that later (thanks, Linux, btw)]:

3051787e3bba: Pull complete Digest: sha256:03737f27c38ecfb257a55664953cac510727cf27052c51ddb7c8ff1a2b9969e1 Status: Downloaded newer image for cloudflare/cloudflared:latest 2025-03-10T06:49:46Z INF Starting tunnel tunnelID=5a5a30f4-c440-48f8-b1a4-ad58369c8196 2025-03-10T06:49:46Z INF Version 2025.2.1 (Checksum a08167aafc749f0c6dbdd0df3c82fc72f9de0d3e47a66959d7ed7a5d603a4a76) 2025-03-10T06:49:46Z INF GOOS: linux, GOVersion: go1.22.5-devel-cf, GoArch: arm64 2025-03-10T06:49:46Z INF Settings: map[no-autoupdate:true token:*****] 2025-03-10T06:49:46Z INF Generated Connector ID: e5933fea-5d2f-4939-a894-1d6325fa5d0c 2025-03-10T06:49:46Z INF Initial protocol quic 2025-03-10T06:49:46Z INF ICMP proxy will use 172.17.0.3 as source for IPv4 2025-03-10T06:49:46Z INF ICMP proxy will use ::1 in zone lo as source for IPv6 2025-03-10T06:49:46Z INF ICMP proxy will use 172.17.0.3 as source for IPv4 2025-03-10T06:49:46Z INF ICMP proxy will use ::1 in zone lo as source for IPv6 2025-03-10T06:49:46Z INF Starting metrics server on [::]:20241/metrics 2025-03-10T06:49:46Z INF Using [CurveID(4588) CurveID(25497) CurveP256] as curve preferences connIndex=0 event=0 ip=1 98.41.192.37 2025/03/10 06:49:46 failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 7168 kiB, got: 416 kiB ). See https://github.com/quic-go/quic-go/wiki/UDP-Buffer-Sizes for details. 2025-03-10T06:49:46Z ERR Failed to serve tunnel connection error="context canceled" connIndex=0 event=0 ip=198.41.192 .37 2025-03-10T06:49:46Z INF Retrying connection in up to 2s connIndex=0 event=0 ip=198.41.192.37 2025-03-10T06:49:47Z INF Tunnel server stopped 2025-03-10T06:49:47Z ERR Initiating shutdown error="context canceled" 2025-03-10T06:49:47Z INF Metrics server stopped 2025-03-10T06:49:47Z ERR icmp router terminated error="context canceled" context canceled

kuerious avatar Mar 10 '25 07:03 kuerious

I had this issue, my mistake was not updating the config.yml with the new UUID. Specifically, check the tunnel and credentials-file options and ensure they're correct.

2004seraph avatar Apr 11 '25 19:04 2004seraph

I had this issue, my mistake was not updating the config.yml with the new UUID. Specifically, check the tunnel and credentials-file options and ensure they're correct.

Would that be with a manual setup? I have not touched such files in my fresh configuration.

patriiiiiiiiiick avatar Apr 24 '25 18:04 patriiiiiiiiiick

I am getting this kind of error when trying to view the log of an add-on. Is this the same issue?

2025-04-24T15:38:05Z ERR error="context canceled" connIndex=1 event=1 ingressRule=0 originService=http://homeassistant:8123 2025-04-24T15:38:05Z ERR Request failed error="context canceled" connIndex=1 dest=https://prefix.domain.eu/api/hassio/addons/9074a9fa_cloudflared/logs/follow?lines=100 event=0 ip=198.41.200.233 type=http

patriiiiiiiiiick avatar Apr 24 '25 18:04 patriiiiiiiiiick

Same issue with me, cannot figure out what to. I am thinking of again making the tunnel after deleting the present one which is having issues. If anyone got any clue or a fix kindly let me know.

ShitijHalder avatar Jun 12 '25 08:06 ShitijHalder

I started getting the same error this morning after updating the Unraid docker container:

2025-06-12T12:13:11Z INF Starting tunnel tunnelID=2a38509f-4da5-4d59-a79f-188fb05a10eb 2025-06-12T12:13:11Z INF Version 2025.6.0 (Checksum 72f233bb55199093961bf099ad62d491db58819df34b071ab231f622deff33ce) 2025-06-12T12:13:11Z INF GOOS: linux, GOVersion: go1.24.2, GoArch: amd64 2025-06-12T12:13:11Z INF Settings: map[no-autoupdate:true token:*****] 2025-06-12T12:13:11Z INF Generated Connector ID: a1a77dc9-1ad1-4ce7-a239-81450b96c403 2025-06-12T12:13:11Z INF Initial protocol quic 2025-06-12T12:13:11Z INF ICMP proxy will use 172.17.0.19 as source for IPv4 2025-06-12T12:13:11Z INF ICMP proxy will use ::1 in zone lo as source for IPv6 2025-06-12T12:13:11Z INF ICMP proxy will use 172.17.0.19 as source for IPv4 2025-06-12T12:13:11Z INF ICMP proxy will use ::1 in zone lo as source for IPv6 2025-06-12T12:13:11Z INF Starting metrics server on [::]:20241/metrics 2025-06-12T12:13:11Z INF Tunnel connection curve preferences: [X25519MLKEM768 CurveID(25497) CurveP256] connIndex=0 event=0 ip=198.41.200.193 2025-06-12T12:13:11Z ERR Failed to serve tunnel connection error="context canceled" connIndex=0 event=0 ip=198.41.200.193 2025-06-12T12:13:11Z INF Retrying connection in up to 2s connIndex=0 event=0 ip=198.41.200.193 2025-06-12T12:13:12Z INF Tunnel server stopped 2025-06-12T12:13:12Z ERR Initiating shutdown error="context canceled" 2025-06-12T12:13:12Z ERR icmp router terminated error="context canceled" 2025-06-12T12:13:12Z INF Metrics server stopped context canceled

msobadger avatar Jun 12 '25 12:06 msobadger

I started getting the same error this morning after updating the Unraid docker container:

2025-06-12T12:13:11Z INF Starting tunnel tunnelID=2a38509f-4da5-4d59-a79f-188fb05a10eb 2025-06-12T12:13:11Z INF Version 2025.6.0 (Checksum 72f233bb55199093961bf099ad62d491db58819df34b071ab231f622deff33ce) 2025-06-12T12:13:11Z INF GOOS: linux, GOVersion: go1.24.2, GoArch: amd64 2025-06-12T12:13:11Z INF Settings: map[no-autoupdate:true token:*****] 2025-06-12T12:13:11Z INF Generated Connector ID: a1a77dc9-1ad1-4ce7-a239-81450b96c403 2025-06-12T12:13:11Z INF Initial protocol quic 2025-06-12T12:13:11Z INF ICMP proxy will use 172.17.0.19 as source for IPv4 2025-06-12T12:13:11Z INF ICMP proxy will use ::1 in zone lo as source for IPv6 2025-06-12T12:13:11Z INF ICMP proxy will use 172.17.0.19 as source for IPv4 2025-06-12T12:13:11Z INF ICMP proxy will use ::1 in zone lo as source for IPv6 2025-06-12T12:13:11Z INF Starting metrics server on [::]:20241/metrics 2025-06-12T12:13:11Z INF Tunnel connection curve preferences: [X25519MLKEM768 CurveID(25497) CurveP256] connIndex=0 event=0 ip=198.41.200.193 2025-06-12T12:13:11Z ERR Failed to serve tunnel connection error="context canceled" connIndex=0 event=0 ip=198.41.200.193 2025-06-12T12:13:11Z INF Retrying connection in up to 2s connIndex=0 event=0 ip=198.41.200.193 2025-06-12T12:13:12Z INF Tunnel server stopped 2025-06-12T12:13:12Z ERR Initiating shutdown error="context canceled" 2025-06-12T12:13:12Z ERR icmp router terminated error="context canceled" 2025-06-12T12:13:12Z INF Metrics server stopped context canceled

Well, I kind of figured out what's happening. This might be the recent update that cloudflared provided. Yesterday it was all fine but today at 4am, I tried to run my usual thing again and this exact same issue popped up. I tried going into support, forums and tried asking LLMs for this but nothing seemed to be working. From what I can figure I would say this recent update did some kind of thing with the tunnel id, my whole project seems to be working but this tunnel thing is making it all a mess. Tried and tired.

ShitijHalder avatar Jun 12 '25 16:06 ShitijHalder

For what it's worth, I ran into this problem a month or two ago, with 2025.5.0. Once I forced it to connect over http2 instead of quic, I haven't had a problem since.

This is what I added to config.yaml in my k8s cluster:

protocol: http2

DaemonDude23 avatar Jun 12 '25 22:06 DaemonDude23

For what it's worth, I ran into this problem a month or two ago, with 2025.5.0. Once I forced it to connect over http2 instead of quic, I haven't had a problem since.

This is what I added to config.yaml in my k8s cluster:

protocol: http2

Well, I tried this too, did not work for me actually, instead http2 increased the issue more, more errors. Now see, if you are seeing new lately, the whole cloudflare system is down, everything abut it - so I am assuming it's their side issue and not my code. I hope they fix it soon. 2 days has already passed and nothing seems to be working. Few other players like Google Cloud Platform, Amazon Web Services, Spotify and Shopify and many other are depended or co-dependent on cloudflare through various means, since cloudflare is down they aren't working as well.

ShitijHalder avatar Jun 13 '25 04:06 ShitijHalder

I'm on a fresh install on the latest, QUIC seems to work if I run the tunnel in a terminal. But when I run as a service in the background it crashes with the context cancelled error

forkitupforkitup avatar Jun 14 '25 23:06 forkitupforkitup

I'm encountering the same.

i noticed that the tunnel is going down when I'm trying to use *arr apps and add a download a torrent.

i have cloudflared running in compose. and another compose with the other apps (*arr + qbittorrent). when I'm adding something, cloudflared is crashing.

jochman avatar Jun 15 '25 10:06 jochman

I'm on a fresh install on the latest, QUIC seems to work if I run the tunnel in a terminal. But when I run as a service in the background it crashes with the context cancelled error

I recreated a new tunnel and everything works fine for me, cloudflare is up again. They were having issues. I deleted all the existing tunnels from my account and as well as from my laptop, now it all works just fine.

ShitijHalder avatar Jun 15 '25 10:06 ShitijHalder

I get the error too, but I can access it without any problems. But it's strange.

ampcpmgp avatar Aug 18 '25 05:08 ampcpmgp

Cloudflare acts weird sometimes so it's not that uncommon thing.

I get the error too, but I can access it without any problems. But it's strange.

ShitijHalder avatar Aug 18 '25 05:08 ShitijHalder

I'm seeing a very similarf issue.

If I run the same container version directly in podman it works fine.

But when I run in a kubernetes pod (k3s) it sees the error reported. I've tried running it with networkHost=true but that has no effect.

I'm using the very latest image on dockerhub.

2025-09-02T18:10:14Z INF Starting tunnel tunnelID=redacted
2025-09-02T18:10:14Z INF Version 2025.8.1 (Checksum 2c904eac894d6a53f096bd9ab77eb8782aa7324a68b9fea8910a4cc8d73ee28d)
2025-09-02T18:10:14Z INF GOOS: linux, GOVersion: go1.24.4, GoArch: amd64
2025-09-02T18:10:14Z INF Settings: map[config:/etc/cloudflared/config/config.yaml cred-file:/etc/cloudflared/creds/credentials.json credentials-file:/etc/cloudflared/creds/credentials.json metrics:0.0.0.0:2000 no-autoupdate:true]
2025-09-02T18:10:14Z INF Generated Connector ID: redacted
2025-09-02T18:10:14Z INF Initial protocol quic
2025-09-02T18:10:14Z INF ICMP proxy will use 192.168.1.91 as source for IPv4
2025-09-02T18:10:14Z INF ICMP proxy will use ::1 in zone lo as source for IPv6
2025-09-02T18:10:14Z WRN The user running cloudflared process has a GID (group ID) that is not within ping_group_range. You might need to add that user to a group within that range, or instead update the range to encompass a group the user is already in by modifying /proc/sys/net/ipv4/ping_group_range. Otherwise cloudflared will not be able to ping this network error="Group ID 65532 is not between ping group 1 to 0"
2025-09-02T18:10:14Z WRN ICMP proxy feature is disabled error="cannot create ICMPv4 proxy: Group ID 65532 is not between ping group 1 to 0 nor ICMPv6 proxy: socket: permission denied"
2025-09-02T18:10:14Z ERR Cannot determine default origin certificate path. No file cert.pem in [~/.cloudflared ~/.cloudflare-warp ~/cloudflare-warp /etc/cloudflared /usr/local/etc/cloudflared]. You need to specify the origin certificate path by specifying the origincert option in the configuration file, or set TUNNEL_ORIGIN_CERT environment variable originCertPath=
2025-09-02T18:10:14Z INF ICMP proxy will use 192.168.1.91 as source for IPv4
2025-09-02T18:10:14Z INF ICMP proxy will use ::1 in zone lo as source for IPv6
2025-09-02T18:10:14Z INF Starting metrics server on [::]:2000/metrics
2025-09-02T18:10:14Z INF Tunnel connection curve preferences: [X25519MLKEM768 CurveP256] connIndex=0 event=0 ip=198.41.200.193
2025-09-02T18:10:14Z ERR failed to run the datagram handler error="context canceled" connIndex=0 event=0 ip=198.41.200.193
2025-09-02T18:10:14Z ERR failed to serve tunnel connection error="control stream encountered a failure while serving" connIndex=0 event=0 ip=198.41.200.193
2025-09-02T18:10:14Z ERR Serve tunnel error error="control stream encountered a failure while serving" connIndex=0 event=0 ip=198.41.200.193
2025-09-02T18:10:14Z INF Retrying connection in up to 2s connIndex=0 event=0 ip=198.41.200.193
2025-09-02T18:10:15Z INF Tunnel connection curve preferences: [X25519MLKEM768 CurveP256] connIndex=0 event=0 ip=198.41.200.193
2025-09-02T18:10:15Z ERR failed to run the datagram handler error="context canceled" connIndex=0 event=0 ip=198.41.200.193
2025-09-02T18:10:15Z ERR failed to serve tunnel connection error="control stream encountered a failure while serving" connIndex=0 event=0 ip=198.41.200.193
2025-09-02T18:10:15Z ERR Serve tunnel error error="control stream encountered a failure while serving" connIndex=0 event=0 ip=198.41.200.193
2025-09-02T18:10:15Z INF Retrying connection in up to 4s connIndex=0 event=0 ip=198.41.200.193
2025-09-02T18:10:18Z INF Tunnel connection curve preferences: [X25519MLKEM768 CurveP256] connIndex=0 event=0 ip=198.41.200.193
2025-09-02T18:10:18Z ERR failed to run the datagram handler error="context canceled" connIndex=0 event=0 ip=198.41.200.193
2025-09-02T18:10:18Z ERR failed to serve tunnel connection error="control stream encountered a failure while serving" connIndex=0 event=0 ip=198.41.200.193
2025-09-02T18:10:18Z ERR Serve tunnel error error="control stream encountered a failure while serving" connIndex=0 event=0 ip=198.41.200.193
2025-09-02T18:10:18Z INF Retrying connection in up to 8s connIndex=0 event=0 ip=198.41.200.193
2025-09-02T18:10:22Z INF Tunnel connection curve preferences: [X25519MLKEM768 CurveP256] connIndex=0 event=0 ip=198.41.200.193
2025-09-02T18:10:22Z ERR failed to run the datagram handler error="context canceled" connIndex=0 event=0 ip=198.41.200.193
2025-09-02T18:10:22Z ERR failed to serve tunnel connection error="control stream encountered a failure while serving" connIndex=0 event=0 ip=198.41.200.193
2025-09-02T18:10:22Z ERR Serve tunnel error error="control stream encountered a failure while serving" connIndex=0 event=0 ip=198.41.200.193
2025-09-02T18:10:22Z INF Retrying connection in up to 16s connIndex=0 event=0 ip=198.41.200.193
2025-09-02T18:10:30Z INF Initiating graceful shutdown due to signal terminated ...
2025-09-02T18:10:30Z INF Tunnel server stopped
2025-09-02T18:10:30Z INF Metrics server stopped
```gg

gilesknap avatar Sep 02 '25 18:09 gilesknap

UPDATE: I should have mentioned that I'm using the official helm chart here https://github.com/cloudflare/helm-charts.

I was trying to use the cloudfare-tunnel helm chart and getting the above.

HOWEVER: I switched to the cloudflare-tunnel-remote chart and it is working fine. EDIT: although the remote chart does connect and I can see that the tunnel is healthy, it keeps exiting and restarting with no error and eventually goes into Crashloop Backoff.

gilesknap avatar Sep 02 '25 19:09 gilesknap