search

brenner-tobias / addon-cloudflared

Connect remotely to your Home Assistant instance without opening any ports using Cloudflared.
MIT License
846 stars 54 forks source link

cloudflare tunnel status goes up and down #419

Closed tivo65 closed 1 year ago

tivo65 commented 1 year ago

The problem

in the last few days my cloudflare tunnel goes up and down causing loss of remote access. I deleted the cloudflared addon, reinstalled, and this time configured it as a remote managed tunnel. started working, then same result, tunnel goes up and down.

What version of Cloudflared has the issue?

4.1.7

What was the last working version of Cloudflared?

4.1.6

What type of installation are you running?

Home Assistant Supervised

Add-on YAML Configuration

#cloudflared trust docker network
http:
  use_x_forwarded_for: true
  trusted_proxies:
    - 172.30.33.0/24

Anything in the logs that might be useful for us?

2023-06-14T02:12:05Z INF Unregistered tunnel connection connIndex=3 event=0 ip=198.41.200.193
2023-06-14T02:12:05Z ERR  error="timeout: no recent network activity" cfRay=7d6f0b5c394b1020-LAX event=1 ingressRule=0 originService=http://homeassistant:8123
2023-06-14T02:12:05Z ERR Request failed error="timeout: no recent network activity" connIndex=3 dest=https://xx.xxx.xxx/api/hassio/addons/e33666f6_rtsp_simple_server/icon event=0 ip=198.41.200.193 type=http
2023-06-14T02:12:05Z INF Unregistered tunnel connection connIndex=1 event=0 ip=198.41.200.63
2023-06-14T02:12:05Z WRN Failed to serve quic connection error="failed to accept QUIC stream: timeout: no recent network activity" connIndex=1 event=0 ip=198.41.200.63
2023-06-14T02:12:05Z WRN Serve tunnel error error="failed to accept QUIC stream: timeout: no recent network activity" connIndex=1 event=0 ip=198.41.200.63
2023-06-14T02:12:05Z INF Retrying connection in up to 1s connIndex=1 event=0 ip=198.41.200.63
2023-06-14T02:12:05Z ERR  error="timeout: no recent network activity" cfRay=7d6f0b5dcac41020-LAX event=1 ingressRule=0 originService=http://homeassistant:8123
2023-06-14T02:12:05Z ERR Request failed error="timeout: no recent network activity" connIndex=3 dest=https://xx.xxx.xxx/api/hassio/app/frontend_latest/7021-KX4kgoN8iAQ.js event=0 ip=198.41.200.193 type=http
2023-06-14T02:12:05Z WRN Failed to serve quic connection error="timeout: no recent network activity" connIndex=3 event=0 ip=198.41.200.193
2023-06-14T02:12:05Z WRN Serve tunnel error error="timeout: no recent network activity" connIndex=3 event=0 ip=198.41.200.193
2023-06-14T02:12:05Z INF Retrying connection in up to 1s connIndex=3 event=0 ip=198.41.200.193
2023-06-14T02:12:05Z WRN Connection terminated error="timeout: no recent network activity" connIndex=3
2023-06-14T02:12:05Z WRN Connection terminated error="failed to accept QUIC stream: timeout: no recent network activity" connIndex=1
2023-06-14T02:12:11Z INF Unregistered tunnel connection connIndex=0 event=0 ip=198.41.192.227
2023-06-14T02:12:11Z WRN Failed to serve quic connection error="failed to accept QUIC stream: timeout: no recent network activity" connIndex=0 event=0 ip=198.41.192.227
2023-06-14T02:12:11Z WRN Serve tunnel error error="failed to accept QUIC stream: timeout: no recent network activity" connIndex=0 event=0 ip=198.41.192.227
2023-06-14T02:12:11Z INF Retrying connection in up to 1s connIndex=0 event=0 ip=198.41.192.227
2023-06-14T02:12:11Z INF Unregistered tunnel connection connIndex=2 event=0 ip=198.41.192.47
2023-06-14T02:12:11Z WRN Failed to serve quic connection error="failed to accept QUIC stream: timeout: no recent network activity" connIndex=2 event=0 ip=198.41.192.47
2023-06-14T02:12:11Z WRN Serve tunnel error error="failed to accept QUIC stream: timeout: no recent network activity" connIndex=2 event=0 ip=198.41.192.47
2023-06-14T02:12:11Z INF Retrying connection in up to 1s connIndex=2 event=0 ip=198.41.192.47
2023-06-14T02:12:11Z ERR Connection terminated error="failed to accept QUIC stream: timeout: no recent network activity" connIndex=2
2023-06-14T02:12:12Z ERR Connection terminated error="failed to accept QUIC stream: timeout: no recent network activity" connIndex=0
2023-06-14T02:12:21Z INF Registered tunnel connection connIndex=1 connection=bd19ca9b-985b-494b-825d-3c8a8299395f event=0 ip=198.41.200.63 location=SLC protocol=quic
2023-06-14T02:12:21Z INF Registered tunnel connection connIndex=2 connection=3b4cb42e-0729-4ae2-9a5a-2acd22d69f14 event=0 ip=198.41.192.47 location=DEN protocol=quic
2023-06-14T02:12:21Z INF Registered tunnel connection connIndex=3 connection=5b5bd2be-1081-4518-a761-1430ab6c720e event=0 ip=198.41.200.113 location=SLC protocol=quic
2023-06-14T02:12:21Z INF Registered tunnel connection connIndex=0 connection=7ed9dbbc-7401-4ef1-9217-130f0299e65b event=0 ip=198.41.192.227 location=DEN protocol=quic
2023-06-14T02:13:05Z ERR  error="stream 193 canceled by remote with error code 0" cfRay=7d6f0d556fb30906-LAX event=1 ingressRule=0 originService=http://homeassistant:8123
2023-06-14T02:13:05Z ERR Request failed error="stream 193 canceled by remote with error code 0" connIndex=3 dest=https://xx.xxx.xxx/api/hls/97383cb6c7a94eb6be0015ea0205f9dfa67e6129d1153f3fa333c7778fe11f96/segment/0.5.m4s event=0 ip=198.41.200.113 type=http
2023-06-14T02:13:51Z ERR  error="Incoming request ended abruptly: context canceled" cfRay=7d6f0d831ad40906-LAX event=1 ingressRule=0 originService=http://homeassistant:8123
2023-06-14T02:13:51Z ERR Request failed error="Incoming request ended abruptly: context canceled" connIndex=1 dest=https://xx.xxx.xxx/api/hls/a7e71c685c040d2b1f756d301395528b75f6ed0be8b000d6ec82d3ea43fb3cef/playlist.m3u8 event=0 ip=198.41.200.63 type=http
2023-06-14T02:13:51Z ERR  error="Incoming request ended abruptly: context canceled" cfRay=7d6f0d831ad60906-LAX event=1 ingressRule=0 originService=http://homeassistant:8123
2023-06-14T02:13:51Z ERR Request failed error="Incoming request ended abruptly: context canceled" connIndex=1 dest=https://xx.xxx.xxx/api/hls/97383cb6c7a94eb6be0015ea0205f9dfa67e6129d1153f3fa333c7778fe11f96/playlist.m3u8 event=0 ip=198.41.200.63 type=http
2023-06-14T02:13:51Z INF Unregistered tunnel connection connIndex=1 event=0 ip=198.41.200.63
2023-06-14T02:13:51Z ERR  error="context canceled" cfRay=7d6f0d0cb9c50906-LAX event=1 ingressRule=0 originService=http://homeassistant:8123
2023-06-14T02:13:51Z ERR Request failed error="context canceled" connIndex=3 dest=https://xx.xxx.xxx/api/camera_proxy_stream/camera.front_door?token=cd38fbad7015999791d38d8204477f483b802910b14df732974b7a9a0bb1418c event=0 ip=198.41.200.113 type=http
2023-06-14T02:13:51Z ERR  error="Incoming request ended abruptly: context canceled" cfRay=7d6f0d831ad40906-LAX event=1 ingressRule=0 originService=http://homeassistant:8123
2023-06-14T02:13:51Z WRN Failed to serve quic connection error="failed to accept QUIC stream: timeout: no recent network activity" connIndex=1 event=0 ip=198.41.200.63
2023-06-14T02:13:51Z ERR Request failed error="Incoming request ended abruptly: context canceled" connIndex=2 dest=https://xx.xxx.xxx/api/hls/a7e71c685c040d2b1f756d301395528b75f6ed0be8b000d6ec82d3ea43fb3cef/playlist.m3u8 event=0 ip=198.41.192.47 type=http
2023-06-14T02:13:51Z WRN Serve tunnel error error="failed to accept QUIC stream: timeout: no recent network activity" connIndex=1 event=0 ip=198.41.200.63
2023-06-14T02:13:51Z INF Retrying connection in up to 1s connIndex=1 event=0 ip=198.41.200.63
2023-06-14T02:13:51Z ERR  error="Incoming request ended abruptly: context canceled" cfRay=7d6f0d831ad60906-LAX event=1 ingressRule=0 originService=http://homeassistant:8123
2023-06-14T02:13:51Z ERR Request failed error="Incoming request ended abruptly: context canceled" connIndex=2 dest=https://xx.xxx.xxx/api/hls/97383cb6c7a94eb6be0015ea0205f9dfa67e6129d1153f3fa333c7778fe11f96/playlist.m3u8 event=0 ip=198.41.192.47 type=http
2023-06-14T02:13:51Z ERR  error="context canceled" cfRay=7d6f0d0cb9b00906-LAX event=1 ingressRule=0 originService=http://homeassistant:8123
2023-06-14T02:13:51Z ERR Request failed error="context canceled" connIndex=3 dest=https://xx.xxx.xxx/api/camera_proxy_stream/camera.back_door?token=c5bd757962e822e6e98ddbdef541695ad2e6ef8cef638817a6577150c7c3af32 event=0 ip=198.41.200.113 type=http
2023-06-14T02:13:51Z INF Unregistered tunnel connection connIndex=2 event=0 ip=198.41.192.47
2023-06-14T02:13:51Z ERR  error="Incoming request ended abruptly: context canceled" cfRay=7d6f0d970b2a0906-LAX event=1 ingressRule=0 originService=http://homeassistant:8123
2023-06-14T02:13:51Z WRN Failed to serve quic connection error="failed to accept QUIC stream: timeout: no recent network activity" connIndex=2 event=0 ip=198.41.192.47
2023-06-14T02:13:51Z ERR Request failed error="Incoming request ended abruptly: context canceled" connIndex=2 dest=https://xx.xxx.xxx/api/hls/97383cb6c7a94eb6be0015ea0205f9dfa67e6129d1153f3fa333c7778fe11f96/segment/1.2.m4s event=0 ip=198.41.192.47 type=http
2023-06-14T02:13:51Z WRN Serve tunnel error error="failed to accept QUIC stream: timeout: no recent network activity" connIndex=2 event=0 ip=198.41.192.47
2023-06-14T02:13:51Z INF Retrying connection in up to 1s connIndex=2 event=0 ip=198.41.192.47
2023-06-14T02:13:51Z ERR  error="Incoming request ended abruptly: context canceled" cfRay=7d6f0d831ad60906-LAX event=1 ingressRule=0 originService=http://homeassistant:8123
2023-06-14T02:13:51Z ERR  error="Incoming request ended abruptly: context canceled" cfRay=7d6f0d970b2a0906-LAX event=1 ingressRule=0 originService=http://homeassistant:8123
2023-06-14T02:13:51Z ERR Request failed error="Incoming request ended abruptly: context canceled" connIndex=0 dest=https://xx.xxx.xxx/api/hls/97383cb6c7a94eb6be0015ea0205f9dfa67e6129d1153f3fa333c7778fe11f96/playlist.m3u8 event=0 ip=198.41.192.227 type=http
2023-06-14T02:13:51Z ERR Request failed error="Incoming request ended abruptly: context canceled" connIndex=0 dest=https://xx.xxx.xxx/api/hls/97383cb6c7a94eb6be0015ea0205f9dfa67e6129d1153f3fa333c7778fe11f96/segment/1.2.m4s event=0 ip=198.41.192.227 type=http
2023-06-14T02:13:51Z ERR  error="Incoming request ended abruptly: context canceled" cfRay=7d6f0d831ad40906-LAX event=1 ingressRule=0 originService=http://homeassistant:8123
2023-06-14T02:13:51Z ERR  error="Incoming request ended abruptly: context canceled" cfRay=7d6f0d96d9f652c5-LAX event=1 ingressRule=0 originService=http://homeassistant:8123
2023-06-14T02:13:51Z ERR Request failed error="Incoming request ended abruptly: context canceled" connIndex=0 dest=https://xx.xxx.xxx/api/hls/a7e71c685c040d2b1f756d301395528b75f6ed0be8b000d6ec82d3ea43fb3cef/playlist.m3u8 event=0 ip=198.41.192.227 type=http
2023-06-14T02:13:51Z ERR Request failed error="Incoming request ended abruptly: context canceled" connIndex=0 dest=https://xx.xxx.xxx/api/websocket event=0 ip=198.41.192.227 type=ws
2023-06-14T02:13:51Z INF Unregistered tunnel connection connIndex=0 event=0 ip=198.41.192.227
2023-06-14T02:13:51Z INF Unregistered tunnel connection connIndex=3 event=0 ip=198.41.200.113
2023-06-14T02:13:51Z ERR Failed to serve quic connection error="failed to accept QUIC stream: timeout: no recent network activity" connIndex=0 event=0 ip=198.41.192.227
2023-06-14T02:13:51Z ERR Failed to serve quic connection error="failed to accept QUIC stream: timeout: no recent network activity" connIndex=3 event=0 ip=198.41.200.113
2023-06-14T02:13:51Z ERR Serve tunnel error error="failed to accept QUIC stream: timeout: no recent network activity" connIndex=0 event=0 ip=198.41.192.227
2023-06-14T02:13:51Z ERR Serve tunnel error error="failed to accept QUIC stream: timeout: no recent network activity" connIndex=3 event=0 ip=198.41.200.113
2023-06-14T02:13:51Z INF Retrying connection in up to 1s connIndex=0 event=0 ip=198.41.192.227
2023-06-14T02:13:51Z INF Retrying connection in up to 1s connIndex=3 event=0 ip=198.41.200.113
2023-06-14T02:13:51Z ERR  error="context canceled" cfRay=7d6f0d0cb9ab0906-LAX event=1 ingressRule=0 originService=http://homeassistant:8123
2023-06-14T02:13:51Z ERR  error="Incoming request ended abruptly: context canceled" cfRay=7d6f0d831ad60906-LAX event=1 ingressRule=0 originService=http://homeassistant:8123
2023-06-14T02:13:51Z ERR Request failed error="context canceled" connIndex=3 dest=https://xx.xxx.xxx/api/camera_proxy_stream/camera.mud_door?token=e346a04e764a4558150af76b686e671ecc4dc0983e661327877233854e39083e event=0 ip=198.41.200.113 type=http
2023-06-14T02:13:51Z ERR Request failed error="Incoming request ended abruptly: context canceled" connIndex=3 dest=https://xx.xxx.xxx/api/hls/97383cb6c7a94eb6be0015ea0205f9dfa67e6129d1153f3fa333c7778fe11f96/playlist.m3u8 event=0 ip=198.41.200.113 type=http
2023-06-14T02:13:51Z ERR  error="context canceled" cfRay=7d6f0d0cb9c80906-LAX event=1 ingressRule=0 originService=http://homeassistant:8123
2023-06-14T02:13:51Z ERR  error="timeout: no recent network activity" cfRay=7d6f0d717cef0906-LAX event=1 ingressRule=0 originService=http://homeassistant:8123
2023-06-14T02:13:51Z ERR Request failed error="context canceled" connIndex=3 dest=https://xx.xxx.xxx/api/camera_proxy_stream/camera.mud_entry?token=e06ea4fd2e4de1733f53a815ef188e28242316ddac66d148d9b29f2a5b4062e4 event=0 ip=198.41.200.113 type=http
2023-06-14T02:13:51Z ERR Request failed error="timeout: no recent network activity" connIndex=3 dest=https://xx.xxx.xxx/api/hls/97383cb6c7a94eb6be0015ea0205f9dfa67e6129d1153f3fa333c7778fe11f96/segment/1.2.m4s event=0 ip=198.41.200.113 type=http
2023-06-14T02:13:52Z ERR Connection terminated error="failed to accept QUIC stream: timeout: no recent network activity" connIndex=2
2023-06-14T02:13:52Z ERR Connection terminated error="failed to accept QUIC stream: timeout: no recent network activity" connIndex=1
2023-06-14T02:13:52Z ERR Connection terminated error="failed to accept QUIC stream: timeout: no recent network activity" connIndex=3
2023-06-14T02:14:12Z ERR Connection terminated error="failed to accept QUIC stream: timeout: no recent network activity" connIndex=0
2023-06-14T02:14:12Z INF Registered tunnel connection connIndex=1 connection=ecaab329-8a41-4844-8a4b-ba4eb5e820fc event=0 ip=198.41.200.63 location=SLC protocol=quic
2023-06-14T02:14:12Z INF Registered tunnel connection connIndex=3 connection=1cc7e0c4-ea59-459c-99ea-810799f67cb8 event=0 ip=198.41.200.113 location=SLC protocol=quic
2023-06-14T02:14:12Z INF Registered tunnel connection connIndex=2 connection=f72f7c92-bfea-47f6-8a96-7e492b34c5e7 event=0 ip=198.41.192.47 location=DEN protocol=quic
2023-06-14T02:14:16Z ERR  error="stream 21 canceled by remote with error code 0" cfRay=7d6f0f0b7c590906-LAX event=1 ingressRule=0 originService=http://homeassistant:8123
2023-06-14T02:14:16Z ERR Request failed error="stream 21 canceled by remote with error code 0" connIndex=2 dest=https://xx.xxx.xxx/api/hls/97383cb6c7a94eb6be0015ea0205f9dfa67e6129d1153f3fa333c7778fe11f96/segment/1.3.m4s event=0 ip=198.41.192.47 type=http
2023-06-14T02:14:19Z INF Unregistered tunnel connection connIndex=1 event=0 ip=198.41.200.63
2023-06-14T02:14:19Z WRN Failed to serve quic connection error="failed to accept QUIC stream: Application error 0x0 (remote)" connIndex=1 event=0 ip=198.41.200.63
2023-06-14T02:14:19Z WRN Serve tunnel error error="failed to accept QUIC stream: Application error 0x0 (remote)" connIndex=1 event=0 ip=198.41.200.63
2023-06-14T02:14:19Z INF Retrying connection in up to 1s connIndex=1 event=0 ip=198.41.200.63
2023-06-14T02:14:21Z WRN Connection terminated error="failed to accept QUIC stream: Application error 0x0 (remote)" connIndex=1
2023-06-14T02:14:34Z INF Registered tunnel connection connIndex=1 connection=0613b45b-af2f-4aca-b8f9-d99b7e7e9ceb event=0 ip=198.41.200.63 location=SLC protocol=quic
2023-06-14T02:14:34Z INF Registered tunnel connection connIndex=0 connection=8883d3ae-0491-4df1-ba17-842eeb7f0fc2 event=0 ip=198.41.192.227 location=DEN protocol=quic
2023-06-14T02:15:58Z ERR  error="context canceled" cfRay=7d6f0f1dad350906-LAX event=1 ingressRule=0 originService=http://homeassistant:8123
2023-06-14T02:15:58Z ERR Request failed error="context canceled" connIndex=2 dest=https://xx.xxx.xxx/api/camera_proxy_stream/camera.back_door?token=5fd8964971f31a55cf5d3ae04861b5fb724ba304df14741eabf9cccb49af4204 event=0 ip=198.41.192.47 type=http
2023-06-14T02:15:58Z ERR  error="context canceled" cfRay=7d6f0f1dad340906-LAX event=1 ingressRule=0 originService=http://homeassistant:8123
2023-06-14T02:15:58Z ERR Request failed error="context canceled" connIndex=3 dest=https://xx.xxx.xxx/api/camera_proxy_stream/camera.mud_door?token=cf8ff776599111ba7c4c31458916f0fb5072f4e7766207dfe58965439d7bdecc event=0 ip=198.41.200.113 type=http
2023-06-14T02:15:59Z ERR  error="context canceled" cfRay=7d6f0f1dad370906-LAX event=1 ingressRule=0 originService=http://homeassistant:8123
2023-06-14T02:15:59Z ERR Request failed error="context canceled" connIndex=2 dest=https://xx.xxx.xxx/api/camera_proxy_stream/camera.front_door?token=741c5cae21a2c0afbc503531fef48274fa3208613e9ce4c71831e945f1926db5 event=0 ip=198.41.192.47 type=http
2023-06-14T02:15:59Z ERR  error="context canceled" cfRay=7d6f0f1dbd390906-LAX event=1 ingressRule=0 originService=http://homeassistant:8123
2023-06-14T02:15:59Z ERR Request failed error="context canceled" connIndex=2 dest=https://xx.xxx.xxx/api/camera_proxy_stream/camera.mud_entry?token=ecbdf59a68f38258260bdc648f5bc1e0fab17f67d9f006fb01f78e89444f47db event=0 ip=198.41.192.47 type=http

Steps to reproduce the issue

fresh install works, then tunnel starts to go up and down as I access HA via the tunnel.

Additional information

No response

brenner-tobias commented 1 year ago

Thanks for raising. Since nothing tunnel / Cloudflared related changed with 4.1.7 (only documentation), this cannot be caused by the update. It fells like a temporary problem with Cloudfalred, so it would be great if you could check for some days, how this evolves (also if you are able to connect or not, not just the logs). I also do have some connection drops from time to time, so if you can connect it's ok.

tivo65 commented 1 year ago

I can connect, but it was dropping so often it was not very functional. i rolled back to 2023.5.4 (still running 4.1.7 of cloudflared) and it is much better (fewer disconnects). from reading other posts https://github.com/cloudflare/cloudflared/issues sounds like others are having the same problem. hopefully the just released 2023.6.2 addresses the issue.

2023-06-15T19:51:10Z INF Unregistered tunnel connection connIndex=1 event=0 ip=198.41.200.23 2023-06-15T19:51:10Z WRN Failed to serve quic connection error="failed to accept QUIC stream: Application error 0x0 (remote)" connIndex=1 event=0 ip=198.41.200.23 2023-06-15T19:51:10Z WRN Serve tunnel error error="failed to accept QUIC stream: Application error 0x0 (remote)" connIndex=1 event=0 ip=198.41.200.23 2023-06-15T19:51:10Z INF Retrying connection in up to 1s connIndex=1 event=0 ip=198.41.200.23 2023-06-15T19:51:12Z WRN Connection terminated error="failed to accept QUIC stream: Application error 0x0 (remote)" connIndex=1 2023-06-15T19:51:33Z INF Registered tunnel connection connIndex=1 connection=9b50c91e-5ac3-43e8-bdd7-9fecfa2d3b3b event=0 ip=198.41.200.23 location=SLC protocol=quic

brenner-tobias commented 1 year ago

@tivo65 Please check with the newest version released yesterday and let us know

Dutchy-79 commented 1 year ago

I have the same issue, just installed latest version and deleted tunnel. Uninstalled addon an reinstall, created tunnel and after a few minutes the tunnel shows down again.

Cloudflare zero tier shows the tunnel is down.

brenner-tobias commented 1 year ago

Unfortunately, I cannot reproduce this. Can you share your addon logs and any special network config or setup that you might have?

Dutchy-79 commented 1 year ago

Sure https://pastebin.com/M0Q33Vtw

Screenshot_20230623_055027_Chrome Screenshot_20230622_071341_Chrome

Dutchy-79 commented 1 year ago

Fresh install full log https://pastebin.com/tPmEjhsW

Dutchy-79 commented 1 year ago

Changed domain and same problem.

brenner-tobias commented 1 year ago

Which Top Level Domain and registrar are you using?

Dutchy-79 commented 1 year ago

One I have from cloudflare, thought I'd get everything at the same place.

tielen.cc

tivo65 commented 1 year ago

i have updated home assistant to the latest patches including cloudflared. i am running on a cloudflare tunnel I created on the cloudflare site. my domain is with omnis. my HA is running on debian in a vm guest on macos host. since the update it is running better, but I still get an occasional reconnecting message - "connection lost. Reconnecting..." Interesting, it generally happens when I am loading node-red. when I do get the reconnecting message it will load after about 30-60 seconds. here are the logs when that happens. the error always references "failed to accept QUIC stream"

2023-06-25T21:44:26Z WRN Serve tunnel error error="timeout: no recent network activity" connIndex=3 event=0 ip=198.41.200.53 2023-06-25T21:44:26Z INF Retrying connection in up to 1s connIndex=3 event=0 ip=198.41.200.53 2023-06-25T21:44:27Z ERR error="timeout: no recent network activity" cfRay=7dd0641acbf4533d-LAX event=1 ingressRule=0 originService=http://homeassistant:8123 2023-06-25T21:44:27Z ERR Request failed error="timeout: no recent network activity" connIndex=0 dest=https://xxxx/api/hassio_ingress/iwUCOPVYCQeCL8JdifRj3nei0F8pobiDV3cM86moXtM/vendor/monaco/dist/editor.js event=0 ip=198.41.192.27 type=http 2023-06-25T21:44:27Z INF Unregistered tunnel connection connIndex=0 event=0 ip=198.41.192.27 2023-06-25T21:44:27Z WRN Failed to serve quic connection error="failed to accept QUIC stream: timeout: no recent network activity" connIndex=0 event=0 ip=198.41.192.27 2023-06-25T21:44:27Z WRN Serve tunnel error error="failed to accept QUIC stream: timeout: no recent network activity" connIndex=0 event=0 ip=198.41.192.27 2023-06-25T21:44:27Z INF Retrying connection in up to 1s connIndex=0 event=0 ip=198.41.192.27 2023-06-25T21:44:27Z INF Unregistered tunnel connection connIndex=1 event=0 ip=198.41.200.113 2023-06-25T21:44:27Z WRN Failed to serve quic connection error="timeout: no recent network activity" connIndex=1 event=0 ip=198.41.200.113 2023-06-25T21:44:27Z WRN Serve tunnel error error="timeout: no recent network activity" connIndex=1 event=0 ip=198.41.200.113 2023-06-25T21:44:27Z INF Retrying connection in up to 1s connIndex=1 event=0 ip=198.41.200.113 2023-06-25T21:44:28Z ERR Connection terminated error="timeout: no recent network activity" connIndex=3 2023-06-25T21:44:28Z ERR Connection terminated error="timeout: no recent network activity" connIndex=1 2023-06-25T21:44:28Z ERR Connection terminated error="failed to accept QUIC stream: timeout: no recent network activity" connIndex=0 2023-06-25T21:44:28Z INF Registered tunnel connection connIndex=2 connection=63731ffb-8a93-423b-a425-b6ba24f8e193 event=0 ip=198.41.192.227 location=DEN protocol=quic 2023-06-25T21:44:28Z INF Registered tunnel connection connIndex=0 connection=5f620907-6abb-4a31-bc5a-f068ad885b17 event=0 ip=198.41.192.27 location=DEN protocol=quic 2023-06-25T21:44:28Z INF Registered tunnel connection connIndex=3 connection=e1a712e9-9995-43da-9fe1-3d3928ff7450 event=0 ip=198.41.200.13 location=SLC protocol=quic 2023-06-25T21:44:29Z INF Registered tunnel connection connIndex=1 connection=577bf9b1-8008-4ebe-bb12-1a4054e06a3c event=0 ip=198.41.200.233 location=SLC protocol=quic

brenner-tobias commented 1 year ago

How are you running HA in Debian? Since with running it in a VM you are introducing many potential problems, I suggest to not use this add-on but use Docker within Debian, run the official Cloudflared Container and follow the instructions to create a tunnel in the Cloudflare Zero Trust Dashboard.

Dutchy-79 commented 1 year ago

It's running on a nuc in a proxmox VM, it's been running fine with cloudflare for a while. Trouble started few days ago.

tivo65 commented 1 year ago

I am running a VM using virtualbox with the supplied VDI file. at HAOS ver 10.3 - https://www.home-assistant.io/installation/alternative - I am somewhat new to HA, been running it for a few months now. please elaborate why running home assistant in a VM is problematic. I thought it was a fully supported installation. Runs totally file other than this cloudflare issue. I believe if I were to run cloudflared outside HA it would require me to spin up another linux VM as HAOS takes over my entire homeassitant VM.

tivo65 commented 1 year ago

i moved cloudflared to docker running on a separate host and so far no problems. you do have to update the trusted_proxies: setting in HA to the subnet where docker is running.

andiukas commented 1 year ago

i moved cloudflared to docker running on a separate host and so far no problems. you do have to update the trusted_proxies: setting in HA to the subnet where docker is running.

HI, I don't understand about trusted proxies setting, can you share your configuration ?

tivo65 commented 1 year ago

from my configuration.yaml on HA. my cloudflared is running on a host in docker that is, for example, 192.168.100.100

cloudflared

trusted proxies is subnet where tunnel running on synology

http: use_x_forwarded_for: true trusted_proxies: