Sudarsan Reddy
Sudarsan Reddy
@rams3sh : the solution is to use --no-block in your cloud-init script.
> I am using the --protocol http2 flag because quic doesn't work Can you explain what you mean by `doesn't work`? We'll need a little more information to help you....
> it fails to connect using quic, I have tried everything, even setting up port triggering for it so now I force it to use HTTP2 before cloudflared use to...
> and even if it's slow, cloudflare tunnel shouldn't just crash ? Can you share crash logs? I only see ``` Jul 17 12:08:36 phoenix cloudflared[470354]: 2022-07-17T06:38:36Z ERR error="Incoming request...
That is expected behaviour since your bandwidth is shared.
> it fails to connect using quic, I have tried everything, even setting up port triggering for it Did you enable UDP egress in your firewall?
Nice! Are you still having these issues?
This is indicative of your clients closing these requests. What is the experience you get on the eyeball side?
@joliveirinha may have found a possible solution.
An explicit `--origincert` is very much possible. You can use this already. Also, if you don't want to bother about certs et all check out https://blog.cloudflare.com/ridiculously-easy-to-use-tunnels/ !