Skip to content

QUIC connection failed #1030

Closed as not planned
Closed as not planned
QUIC connection failed#1030

Description

@ramakrishnachillara
ramakrishnachillara
opened on Jun 28, 2026

The problem

2026-06-28T04:21:36Z INF precheck component="UDP Connectivity" details="QUIC connection failed" run_id=b81e9acd-b97d-4b1a-aa9d-ee1e31e798d8 status=fail target=region2.v2.argotunnel.com

What version of Cloudflared has the issue?

7.0.9

What was the last working version of Cloudflared?

No response

What type of installation are you running?

Home Assistant OS

App (Add-on) YAML Configuration

xternal_hostname: lab01
additional_hosts: []
tunnel_name: lab01
catch_all_service: catcha-all
tunnel_token: >-
  
log_level: debug
post_quantum: false

Anything in the logs that might be useful for us?



Steps to reproduce the issue


xternal_hostname: lab01

additional_hosts: []

tunnel_name: lab01

catch_all_service: catcha-all

tunnel_token: >-


log_level: debug

post_quantum: false


Additional information


No response


8Z ERR failed to serve tunnel connection error="accept stream listener encountered a failure while serving" connIndex=0 event=0 ip=198.41.192.27

2026-06-28T04:51:28Z ERR Serve tunnel error error="accept stream listener encountered a failure while serving" connIndex=0 event=0 ip=198.41.192.27

2026-06-28T04:51:28Z INF Retrying connection in up to 1s connIndex=0 event=0 ip=198.41.192.27

2026-06-28T04:51:28Z ERR Connection terminated connIndex=0

2026-06-28T04:51:28Z ERR failed to run the datagram handler error="context canceled" connIndex=1 event=0 ip=198.41.200.53

2026-06-28T04:51:28Z ERR failed to serve tunnel connection error="accept stream listener encountered a failure while serving" connIndex=1 event=0 ip=198.41.200.53

2026-06-28T04:51:28Z ERR Serve tunnel error error="accept stream listener encountered a failure while serving" connIndex=1 event=0 ip=198.41.200.53

2026-06-28T04:51:28Z INF Retrying connection in up to 1s connIndex=1 event=0 ip=198.41.200.53

2026-06-28T04:51:28Z ERR Connection terminated connIndex=1

2026-06-28T04:51:28Z ERR  error="stream 9 canceled by remote with error code 0" connIndex=3 event=1 ingressRule=0 originService=http://192.168.20.112:8123

2026-06-28T04:51:28Z ERR Request failed error="stream 9 canceled by remote with error code 0" connIndex=3 dest=https://lab01.infinitumtech.net/api/hassio/addons/9074a9fa_cloudflared/logs/follow?lines=100 event=0 ip=198.41.200.63 type=http

2026-06-28T04:51:28Z ERR failed to run the datagram handler error="context canceled" connIndex=3 event=0 ip=198.41.200.63

2026-06-28T04:51:28Z ERR failed to serve tunnel connection error="accept stream listener encountered a failure while serving" connIndex=3 event=0 ip=198.41.200.63

2026-06-28T04:51:28Z ERR Serve tunnel error error="accept stream listener encountered a failure while serving" connIndex=3 event=0 ip=198.41.200.63

2026-06-28T04:51:28Z INF Retrying connection in up to 1s connIndex=3 event=0 ip=198.41.200.63

2026-06-28T04:51:28Z ERR Connection terminated connIndex=3

2026-06-28T04:51:28Z INF Unregistered tunnel connection connIndex=2 event=0 ip=198.41.192.57


App: Cloudflared

Use a Cloudflare Tunnel to remotely connect to Home Assistant without opening any ports


App version: 7.0.9

You are running the latest version of this app.

System: Home Assistant OS 18.0  (amd64 / generic-x86-64)

Home Assistant Core: 2026.6.4

Home Assistant Supervisor: 2026.06.2


Please, share the above information when looking for help

or support in, e.g., GitHub, forums or the Discord chat.


Log level is set to DEBUG

[10:21:31] DEBUG: Cloudflared log level set to "info"

[10:21:31] DEBUG: Checking connectivity to Cloudflare

[10:21:31] DEBUG: Checking region1.v2.argotunnel.com TCP port 7844

[10:21:31] DEBUG: Checking region1.v2.argotunnel.com UDP port 7844

[10:21:32] DEBUG: Checking region2.v2.argotunnel.com TCP port 7844

[10:21:32] DEBUG: Checking region2.v2.argotunnel.com UDP port 7844

[10:21:34] DEBUG: Checking api.cloudflare.com TCP port 443

[10:21:34] INFO: Using Cloudflare Remote Management Tunnel

[10:21:34] INFO: All app (add-on) configuration options except tunnel_token will be ignored.

[10:21:34] INFO: Connecting Cloudflare Tunnel...

[10:21:34] DEBUG: cloudflared tunnel --no-autoupdate --metrics=0.0.0.0:36500 --post-quantum run --token=eyJhIjoiYTg1MGU3OTgwM2IwZjE4YTJlYjI3NTU3MDRhN2YwNWEiLCJ0IjoiYTk2MDZjMjYtZDhmNC00YjRiLWEyMDMtZGU3ZGM1MDdkZjk0IiwicyI6Ik1tVm1OV1ZoTmpRdE9HTTJNeTAwTURFNExUZzBNakl0T1RGak1tUTRZVFExTWpJeSJ9

2026-06-28T04:51:34Z INF Starting tunnel tunnelID=a9606c26-d8f4-4b4b-a203-de7dc507df94

2026-06-28T04:51:34Z INF Version 2026.6.1 (Checksum 5861a10a438fe8ddcfebb3b830f83966cbf193edafce0fe2eeb198fbae1f7a22)

2026-06-28T04:51:34Z INF GOOS: linux, GOVersion: go1.26.4, GoArch: amd64

2026-06-28T04:51:34Z INF Settings: map[metrics:0.0.0.0:36500 no-autoupdate:true post-quantum:true pq:true token:*****]

2026-06-28T04:51:34Z INF Generated Connector ID: cc363ed6-d9f0-4105-9dcd-43a988daf2b7

2026-06-28T04:51:34Z INF Initial protocol quic

2026-06-28T04:51:34Z INF ICMP proxy will use 172.30.33.3 as source for IPv4

2026-06-28T04:51:34Z INF ICMP proxy will use fd0c:ac1e:2100::a in zone eth0 as source for IPv6

2026-06-28T04:51:34Z INF ICMP proxy will use 172.30.33.3 as source for IPv4

2026-06-28T04:51:34Z INF ICMP proxy will use fd0c:ac1e:2100::a in zone eth0 as source for IPv6

2026-06-28T04:51:34Z INF Starting metrics server on [::]:36500/metrics

2026-06-28T04:51:34Z INF Tunnel connection curve preferences: [X25519MLKEM768 CurveID(65074)] connIndex=0 event=0 ip=198.41.192.77

2026-06-28T04:51:35Z INF Registered tunnel connection connIndex=0 connection=11026c13-9751-4b7b-9dc9-0830230b2f8d event=0 ip=198.41.192.77 location=hyd02 protocol=quic

2026-06-28T04:51:35Z INF Tunnel connection curve preferences: [X25519MLKEM768 CurveID(65074)] connIndex=1 event=0 ip=198.41.200.73

2026-06-28T04:51:35Z INF Updated to new configuration config="{"ingress":[{"hostname":"lab01.infinitumtech.net","service":"http://192.168.20.112:8123"},{"hostname":"lab01-mcp.infinitumtech.net","service":"http://192.168.20.112:9583"},{"service":"http_status:404"}],"warp-routing":{"enabled":false}}" version=6

2026-06-28T04:51:36Z INF Tunnel connection curve preferences: [X25519MLKEM768 CurveID(65074)] connIndex=2 event=0 ip=198.41.192.27

2026-06-28T04:51:36Z INF Registered tunnel connection connIndex=1 connection=e8148ea6-8c6f-4627-b683-c2d53349fb4a event=0 ip=198.41.200.73 location=bom12 protocol=quic

2026-06-28T04:51:36Z INF Registered tunnel connection connIndex=2 connection=56ea46f9-0fa3-417d-9695-6f71c90ad62c event=0 ip=198.41.192.27 location=hyd02 protocol=quic

2026-06-28T04:51:37Z INF Tunnel connection curve preferences: [X25519MLKEM768 CurveID(65074)] connIndex=3 event=0 ip=198.41.200.23

2026-06-28T04:51:37Z INF Registered tunnel connection connIndex=3 connection=bbdaaae3-db11-4521-a7f6-ebcb3d9bf6fa event=0 ip=198.41.200.23 location=bom09 protocol=quic

2026-06-28T04:51:44Z INF +-----------------------------------------------------------------------------------------------+

2026-06-28T04:51:44Z INF |                                    CONNECTIVITY PRE-CHECKS                                    |

2026-06-28T04:51:44Z INF +-----------------------------------------------------------------------------------------------+

2026-06-28T04:51:44Z INF |  COMPONENT         TARGET                     STATUS  DETAILS                                 |

2026-06-28T04:51:44Z INF |  DNS Resolution    region1.v2.argotunnel.com  PASS    DNS Resolved successfully               |

2026-06-28T04:51:44Z INF |  DNS Resolution    region2.v2.argotunnel.com  PASS    DNS Resolved successfully               |

2026-06-28T04:51:44Z INF |  UDP Connectivity  region1.v2.argotunnel.com  PASS    QUIC connection successful              |

2026-06-28T04:51:44Z INF |  UDP Connectivity  region2.v2.argotunnel.com  FAIL    QUIC connection failed                  |

2026-06-28T04:51:44Z INF |  TCP Connectivity  region1.v2.argotunnel.com  PASS    HTTP/2 connection successful            |

2026-06-28T04:51:44Z INF |  TCP Connectivity  region2.v2.argotunnel.com  PASS    HTTP/2 connection successful            |

2026-06-28T04:51:44Z INF |  Cloudflare API    api.cloudflare.com:443     PASS    API is reachable                        |

2026-06-28T04:51:44Z INF |  WARNING: Allow outbound QUIC traffic on port 7844 or use HTTP2.                              |

2026-06-28T04:51:44Z INF |                                                                                               |

2026-06-28T04:51:44Z INF |  SUMMARY: Environment ready with degraded transport. cloudflared will proceed using 'http2'.  |

2026-06-28T04:51:44Z INF +-----------------------------------------------------------------------------------------------+

2026-06-28T04:51:44Z INF precheck component="DNS Resolution" details="DNS Resolved successfully" run_id=191f5d21-d59c-4ab3-aa84-095a7051346d status=pass target=region1.v2.argotunnel.com

2026-06-28T04:51:44Z INF precheck component="DNS Resolution" details="DNS Resolved successfully" run_id=191f5d21-d59c-4ab3-aa84-095a7051346d status=pass target=region2.v2.argotunnel.com

2026-06-28T04:51:44Z INF precheck component="UDP Connectivity" details="QUIC connection successful" run_id=191f5d21-d59c-4ab3-aa84-095a7051346d status=pass target=region1.v2.argotunnel.com

2026-06-28T04:51:44Z INF precheck component="UDP Connectivity" details="QUIC connection failed" run_id=191f5d21-d59c-4ab3-aa84-095a7051346d status=fail target=region2.v2.argotunnel.com

2026-06-28T04:51:44Z INF precheck component="TCP Connectivity" details="HTTP/2 connection successful" run_id=191f5d21-d59c-4ab3-aa84-095a7051346d status=pass target=region1.v2.argotunnel.com

2026-06-28T04:51:44Z INF precheck component="TCP Connectivity" details="HTTP/2 connection successful" run_id=191f5d21-d59c-4ab3-aa84-095a7051346d status=pass target=region2.v2.argotunnel.com

2026-06-28T04:51:44Z INF precheck component="Cloudflare API" details="API is reachable" run_id=191f5d21-d59c-4ab3-aa84-095a7051346d status=pass target=api.cloudflare.com:443
Activity
  1. TUISTERa commented on Jun 28, 2026 
    @TUISTERa
    TUISTERa
    on Jun 28, 2026
    Same here, i added --protocol=http2 to be able to use the app.
  2. elcajon commented on Jun 29, 2026 
    @elcajon
    elcajon
    on Jun 29, 2026
    Collaborator
    

    Same here, i added --protocol=http2 to be able to use the app.
    

    

    That should help, otherwise, there isn't much we can do from the app's perspective, since we're just using the app as wrapper for Cloudflare to make it work with Home Assistant. If in doubt, please report any further errors directly to Cloudflare.
  3. elcajon
    closed this as not plannedon Jun 29, 2026
  4. github-actions
    locked and limited conversation to collaborators on Jul 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Metadata
Metadata
Assignees
No one assigned
    Labels
    No labels
    No labels
    Type
    No type
    Projects
    No projects
      Milestone
      No milestone
      Relationships
      None yet
      Development
      No branches or pull requests
      Issue actions