🐛 `2024.1.0` → CurvePreferences includes unsupported curve
buroa opened this issue · comments
Describe the bug
Failed to create new quic connection error="failed to dial to edge with quic: INTERNAL_ERROR (local): tls: CurvePreferences includes unsupported curve" connIndex=0 event=0 ip=198.41.200.193
To Reproduce
Steps to reproduce the behavior:
- Run
cloudflared: https://github.com/buroa/k8s-gitops/blob/master/kubernetes/apps/networking/cloudflared/app/helmrelease.yaml#L38-L42
If it's an issue with Cloudflare Tunnel:
- Tunnel ID:
bfb3d448-8db6-4dda-b84f-11822e0fc62f - cloudflared config: https://github.com/buroa/k8s-gitops/blob/master/kubernetes/apps/networking/cloudflared/app/configs/config.yaml
Expected behavior
Doesn't crash.
Environment and versions
- OS:
Linux - Architecture:
AMD64 - Version:
2024.1.0
related #1132
Thanks @kznrluk!
Hi,
We are aware that the docker image is currently broken. We are fixing it and will provide a new release with all binaries and docker images fixed ASAP.
2024.1.0 has a serious issue/bug, so it's been unreleased; it will be back soon.
Hi fellow developers,
if you're using brew and are stuck with this faulty version, here is how to unblock:
## remove faulty version
brew uninstall cloudflared
## update everything else
brew update
brew upgrade
## install last known working version
curl https://raw.githubusercontent.com/Homebrew/homebrew-core/08b1d877b616312f844957a35bb37ffdfc849c75/Formula/c/cloudflared.rb --location --output ~/cloudflared.rb
brew install ~/cloudflared.rbCredits to https://stackoverflow.com/a/7787703/587407
Sorry for the trouble. We have released 2024.1.1 to fix the issue.
Thanks @chungthuang :)
@chungthuang I built 2024.1.1, but bug from this issue is present for me, it not fixed.
@chungthuang I built 2024.1.1, but bug from this issue is present for me, it not fixed.
Ok, I found message about new patched go toolchain. After build with it all ok, but I think it need to be referenced in readme.
Still having that issue on the Homebrew MacOS/ARM64 2024.1.1 version
+1 same; Still having issue
+1 same. Create new issue #1148
Hi,
We realized that the release 2024.1.1 generated a binary in homebrew that didn't used the right go toolchain. We will be releasing 2024.1.2 today which should fix that.