Dito Windyaksa
Dito Windyaksa
engage.cloudflareclient.com resolving to ipv4 or ipv6 can change the data center you're connected to
Looks more of an ISP issue to me. Maybe your ISP doesn't peer v6 with CF locally in Hawaii.
engage.cloudflareclient.com resolving to ipv4 or ipv6 can change the data center you're connected to
yeah, still looks like an isp issue for me. doesn't make sense for cloudflare to deploy v4/v6 warp seperately. i think the client will prioritize v6 > v4 to connect...
can confirm this still happens. running cloudflared v2022.10.3 in kubernetes setup w/ http2 protocol set. can send some CF-rays through ticket or here if needed.
@pirate can you try running cloudflared in host level and not docker? just to check whether it's a docker issue or not. talking about tunnels, I have no issue running...
> 2023-03-20T13:29:17Z WRN Connection terminated error="DialContext error: dial tcp 198.41.200.13:7844: i/o timeout" connIndex=2 2023-03-20T13:29:34Z WRN Connection terminated error="DialContext error: dial tcp 198.41.192.227:7844: i/o timeout" connIndex=0 is that running under docker?...
This have something to do with cloudflared -> local service. cloudflared received incoming requests but for some reason it is unable to forward it to the local service. might want...
Expected curl response (running cloudflared tcp service): ``` > * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4): * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4): * old SSL session ID...
@iicdev you have an interesting use-case. have you tried switching between quic & http2 protocols and see the difference? also might be off-topic, but have you considered other solutions too...
@DentonGentry stupid noob question here, but does Tailscale bind on network iface directly instead of following the routing table? When WARP is enabled: ``` LinkChange: major, rebinding. New state: interfaces.State{defaultRoute=en0...
Experiencing similar error messages on 2022.10.3, lost all 4 HAs within 10 seconds. Running in kubernetes setup. ``` 2022-11-11T21:10:53Z ERR error="Incoming request ended abruptly: context canceled" cfRay=768a04610c4fa089-SIN ingressRule=2 originService=http://kong-proxy.kong.svc.cluster.local:8080 2022-11-12T00:00:22Z...