我这边的弄的阿姆斯特丹的，cloudflare tunnel 经常掉线。查看日志是显示
Mar 02 17:19:57 AMS-v6 cloudflared[279]: 2023-03-02T17:19:57Z INF Retrying connection in up to 1m4s connIndex=3 ip=198.41.200.233
Mar 02 17:19:57 AMS-v6 cloudflared[279]: 2023-03-02T17:19:57Z ERR Failed to create new quic connection error="failed to dial to edge with quic: timeout: no recent network activity" connIndex=1 ip=198.41.200.33
Mar 02 17:19:57 AMS-v6 cloudflared[279]: 2023-03-02T17:19:57Z INF Retrying connection in up to 1m4s connIndex=1 ip=198.41.200.33
Mar 02 17:19:57 AMS-v6 cloudflared[279]: 2023-03-02T17:19:57Z ERR Failed to create new quic connection error="failed to dial to edge with quic: timeout: no recent network activity" connIndex=2 ip=198.41.192.67
Mar 02 17:19:57 AMS-v6 cloudflared[279]: 2023-03-02T17:19:57Z INF Retrying connection in up to 1m4s connIndex=2 ip=198.41.192.67
Mar 02 17:19:57 AMS-v6 cloudflared[279]: 2023-03-02T17:19:57Z ERR Connection terminated error="failed to dial to edge with quic: timeout: no recent network activity" connIndex=0
Mar 02 17:20:09 AMS-v6 cloudflared[279]: 2023-03-02T17:20:09Z WRN If this log occurs persistently, and cloudflared is unable to connect to Cloudflare Network with `quic` protocol, then most likely your machine/network is getting its egress UDP to port 7844 (or others) blocked or dropped. Make sure to allow egress connectivity as per
https://developers.cloudflare.com/cloudflare-one/connections/connect-apps/configuration/ports-and-ips/Mar 02 17:20:09 AMS-v6 cloudflared[279]: If you are using private routing to this Tunnel, then UDP (and Private DNS Resolution) will not work unless your cloudflared can connect with Cloudflare Network with `quic`. connIndex=3 ip=198.41.200.233
Mar 02 17:20:09 AMS-v6 cloudflared[279]: 2023-03-02T17:20:09Z INF Switching to fallback protocol http2 connIndex=3 ip=198.41.200.233
Mar 02 17:20:09 AMS-v6 cloudflared[279]: 2023-03-02T17:20:09Z ERR Connection terminated error="failed to dial to edge with quic: timeout: no recent network activity" connIndex=3
Select Language