🐛GRPC connection failed with quic protocol
hezhijie0327 opened this issue · comments
Describe the bug
When run with --protocol auto or --protocol quic, and connecting to GRPC, got error message
2024-01-30T13:49:11Z ERR error="Incoming request ended abruptly: context canceled" cfRay=84da2cf27ef82aab-LAX event=1 ingressRule=1 originService=https://127.0.0.1:8443
2024-01-30T13:49:11Z ERR Request failed error="Incoming request ended abruptly: context canceled" connIndex=0 dest=https://subdomain.mydomain.com/gRPC/Tun event=0 ip=198.41.192.27 type=http
But after switch to --protocol http2, no issue
To Reproduce
Steps to reproduce the behavior:
- Set
--protocol autoor--protocol quic - Run with docker
- See error
If it's an issue with Cloudflare Tunnel:
4. Tunnel ID : 626ee7b1-b412-4b83-9ecd-1d84bb0e8b5a
5. cloudflared config:
Expected behavior
run with --protocol http2 can access GRPC
Environment and versions
- OS: [e.g. MacOS] Ubuntu 22.04 LTS
- Architecture: [e.g. AMD, ARM] AMD64
- Version: [e.g. 2022.02.0] 2024.1.5
Logs and errors
If applicable, add logs or errors to help explain your problem.
Additional context
Add any other context about the problem here.
This is not a bug. We officially don't support GRPC.
We did some work to have it working on HTTP2 for testing purposes, but due to prioritisation, this feature is not supported.
The main reason is because we don't really support HTTP trailers in QUIC (which is a requirement for gRPC).
So, I will close this for now, since there is already another issue open to track this.