-
Notifications
You must be signed in to change notification settings - Fork 907
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🐛 stream X canceled by remote with error code 0 #1105
Comments
Logs now tunnel has failed:
|
More logs
|
More logs
|
Another failed tunnel. What else can I do to try and resolve this issue?
|
A reboot of the Cloudflare add on in HomeAssistant resolves the issue temporarily |
I have the exact same problem. Very annoying. |
Hi @mklaiber What I have done to deal with this is install https://github.com/mvdwetering/websitechecker and set that up to check my cloudflared tunnel url. Then an automation that restarts the Cloudflared add-on when the tunnel has failed. This really is a workaround but until the tunnel failing issue is resolved it’s the best I can come up with. |
Can confirm this happened to me just now. |
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 the CF team to check this out. |
Same here, I tried to use Nextcloud as additional host in Cloudflare and I encountered so many errors with |
I have the same logs showing. |
Wondering if there was any news on this/any steps to take to remedy. Thanks! |
Hi, Restarting the tunnel container isn't exactly a great solution, but it would be ideal to see a fix for this soon / or preventative measures that I can take, Cheers, |
Looks like the error is caused by quic-go These parts of the library seems to handle read/write fails and return this specific error. Potentially due to some server-side issue at cloudflare or network dropouts, though I have no way to test that theory. |
I just ran into a similar problem (logs below). Also solved with a restart. Been running these tunnels for almost a year now and this is the first time I've encountered this. I have Uptime Kuma running and checking these connections, this started suddenly at 2024-07-11T09:09:23Z with these error messages, nothing I can find prior to that. Strangely only 3 of my 5 active tunnels were affected. 2 of the tunnels connected to the same target host came down at the same time, 1 more (on a different target host) went down 10 minutes later. 2 of the connections came back by themselves, one after 2 minutes, the other one came back after 5 minutes. That last one went down again 13 minutes after that, then back up after 7 minutes, down again 13 minutes later, and back up 7 minutes after that, then stayed up until I restarted the tunnel. 🤷🏼♂️
|
Seeing the same thing. Restart of the Cloudflare add-on (a docker container) in Home Assistant fixes things for a few hours. I would post my logs but they are pretty much the same as everyone else's. Hate this. Cloudflare has been reliable for a very long time for me. |
Exactly the same issue occurs when connecting from a specific device and network (iPhone + cellular). When sharing the internet from the phone and connecting from a PC, there is no problem. When connecting from the phone via WiFi, there is no problem. Restarting cloudflared temporarily solves the issue. |
We are also bumping into this issue. Restarting |
Same Issue as above. |
Have been using |
What version of cloudflared is everyone running that is having this issue? |
We also have this exact issue. We are running version 2024.6.1. |
Same issue here. 2024.6.1 but the issue only started up within the past few days. |
Our issue started on 7/19/2024 and has been randomly reoccurring since then. We have a ticket open with support and provided this thread as a reference. If I get a resolution I’ll make sure to share. |
Hey everyone, not a CF engineer here, just a support guy but to keep from blowing up this random person's post with comments I opened a bug report under this link #1300 lets move to leaving comments there as it will also give me a bit of visibility into people reporting this outside of our ticket system. Definitely feel free to also open tickets for this as well, or your own Github bug reports, as mine just has generalized info. |
Sad to hear I am not the only one. This has started happening to me also in a recent update and none of my services resolve at all but load indefinitely and then time out with an HTTP 524 error. Would be super grateful for a fix. |
Wanted to respond for anyone who isn't on the other issue. It appears to be fixed now. |
Hey there. We are having the exact same issue, and it seems to be related to how Cloudflare handles peer discovery. Cloudflared stills picks proxy locations that can be monitored as "rerouted" from Cloudflare status page. I updated our analysis here: #1360 (comment) |
Describe the bug
Cloudflare Tunnel disconnects after a few hours
To Reproduce
Steps to reproduce the behavior:
If it's an issue with Cloudflare Tunnel:
4. Tunnel ID : a123c10a-8b4b-49ff-870b-5880edbd505e
5. cloudflared config: remote managed tunnel
Expected behavior
I expect tunnel to stay open. It disconnects and requires a restart of the cloudflared add-on to reconnect tunnel
Environment and versions
Logs and errors
Will add when this tunnel fails (HomeAssistant doesn't t display logs after a restart of the add-on)
The text was updated successfully, but these errors were encountered: