Describe the bug
Tunnel updated to 2024.1.3 and similar to 2024.1.1 broke the quic protocol
To Reproduce
Steps to reproduce the behavior:
- Run 2024.1.3 tunnel in a kubernetes cluster
If it's an issue with Cloudflare Tunnel:
5. cloudflared config:
https://github.com/cloudflare/helm-charts/blob/main/charts/cloudflare-tunnel-remote/templates/deployment.yaml
Expected behavior
A clear and concise description of what you expected to happen.
Tunnel should function without error.
Environment and versions
- k8s version: 1.27.7
- node image: AKSUbuntu-2204gen2containerd-202401.03.0
- kernel version: 5.15.0-1053-azure
Logs and errors
2024-01-17T18:58:20Z INF Starting tunnel tunnelID=xxxxxx-xxxx-xxxx-xxxx-xxxxxxx
2024-01-17T18:58:20Z INF Version 2024.1.2
2024-01-17T18:58:20Z INF GOOS: linux, GOVersion: go1.21.5-devel-cf, GoArch: amd64
2024-01-17T18:58:20Z INF Settings: map[metrics:0.0.0.0:2000]
2024-01-17T18:58:20Z INF Environmental variables map[TUNNEL_TOKEN:*****]
2024-01-17T18:58:20Z INF Autoupdate frequency is set autoupdateFreq=86400000
2024-01-17T18:58:20Z INF Generated Connector ID: xxxxxx-xxxx-xxxx-xxxx-xxxxxxx
2024-01-17T18:58:21Z INF Initial protocol quic
2024-01-17T18:58:21Z INF ICMP proxy will use 10.30.0.210 as source for IPv4
2024-01-17T18:58:21Z INF ICMP proxy will use xxx::xxxx::xxxx::xxxx::xxxxx in zone eth0 as source for IPv6
2024-01-17T18:58:21Z 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"
2024-01-17T18:58:21Z 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"
2024-01-17T18:58:22Z INF Starting metrics server on [::]:2000/metrics
2024/01/17 18:58:22 failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See https://github.com/quic-go/quic-go/wiki/UDP-Buffer-Sizes for details.
2024-01-17T18:58:22Z INF cloudflared has been updated version=2024.1.3
2024-01-17T18:58:22Z INF Restarting service managed by SysV...
2024-01-17T18:58:22Z INF PID of the new process is 16
2024-01-17T18:58:22Z ERR Initiating shutdown error="cloudflared has been updated to version 2024.1.3"
2024-01-17T18:58:22Z ERR writing release: Application error 0x0 (local)
2024-01-17T18:58:22Z ERR Failed to serve quic connection error="context canceled" connIndex=0 event=0 ip=xxx.xxx.xxx.xxx
2024-01-17T18:58:22Z INF Tunnel server stopped
2024-01-17T18:58:22Z INF Starting tunnel tunnelID=xxxxxx-xxxx-xxxx-xxxx-xxxxxxx
2024-01-17T18:58:22Z INF Version 2024.1.3
2024-01-17T18:58:22Z INF GOOS: linux, GOVersion: go1.21.5, GoArch: amd64
2024-01-17T18:58:22Z INF Settings: map[metrics:0.0.0.0:2000]
2024-01-17T18:58:22Z INF Environmental variables map[TUNNEL_TOKEN:*****]
2024-01-17T18:58:22Z INF Autoupdate frequency is set autoupdateFreq=86400000
2024-01-17T18:58:22Z INF Generated Connector ID: xxxxxx-xxxx-xxxx-xxxx-xxxxxxx
2024-01-17T18:58:22Z INF Initial protocol quic
2024-01-17T18:58:22Z INF ICMP proxy will use 10.30.0.210 as source for IPv4
2024-01-17T18:58:22Z INF ICMP proxy will use xxxx::xxxx::xxxx::xxxx::xxxx in zone eth0 as source for IPv6
2024-01-17T18:58:22Z 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"
2024-01-17T18:58:22Z 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"
2024-01-17T18:58:22Z INF Starting metrics server on [::]:2000/metrics
2024/01/17 18:58:22 failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See https://github.com/quic-go/quic-go/wiki/UDP-Buffer-Sizes for details.
2024-01-17T18:58:22Z INF Registered tunnel connection connIndex=0 connection=xxxxxx-xxxx-xxxx-xxxx-xxxxxxx event=0 ip=xxx.xxx.xxx.xxx location=iad05 protocol=quic
2024-01-17T18:58:22Z INF Metrics server stopped
cloudflared has been updated to version 2024.1.3
Additional context
The --no-autoupdate flag was also ignored in the deployment.yaml but that's another issue.
Describe the bug
Tunnel updated to 2024.1.3 and similar to 2024.1.1 broke the quic protocol
To Reproduce
Steps to reproduce the behavior:
If it's an issue with Cloudflare Tunnel:
5. cloudflared config:
https://github.com/cloudflare/helm-charts/blob/main/charts/cloudflare-tunnel-remote/templates/deployment.yaml
Expected behavior
A clear and concise description of what you expected to happen.
Tunnel should function without error.
Environment and versions
Logs and errors
Additional context
The --no-autoupdate flag was also ignored in the deployment.yaml but that's another issue.