Constant Site timeouts while using cloudflared tunnel

What is the name of the domain?

thewerewolfhunters.cc

What is the error number?

524

What is the error message?

A timeout occurred

What is the issue you’re encountering

Im running cloudflared on ubuntu server, I used the quick setup from cloudflare zerotrust, and am using cloudflare hosted domain. The dashboard shows tunnel is in “healthy” status and the cloudflared service is up and running. When I first start the service, the tunnel works fine, and I’m able to reach the service I’m running without problems. However after maybe 45mins to an hour, the site stops responding, and eventually errors out. The tunnel still shows as “healthy” and the cloudflared service is still running as well. If I restart the service, the site is once again reachable, but again will time out after a short time. I could easily have a cron that restarts the service every 30mins or something but I really should not have to.The error message appears to just show “No recent network activity”. For the moment Im just running a small streamlit dashboard (running streamlit’s own “test” server while it’s being built)

What steps have you taken to resolve the issue?

I’ve read around a bit and seen similar issues reported when using HTTP/3 / QUIC, I’ve tried running the tunnel without this protocol, but nothing changed. I don’t believe this is a firewall related issue as the tunnel does actually work when service first starts.

What are the steps to reproduce the issue?

Start the tunnel service
Visit site - working without issue.
Wait 40mins or so
Refresh the site
Site times out

Screenshot of the error

May I ask have you switched to http2 instead? :thinking:

What’s your SSL status on the origin host/server?
Have you got a valid SSL certificate installed and present, or not?
Or at least self-signed one or not at all?

May I ask what SSL option have you got selected under the SSL/TLS tab at Cloudflare dashboard for your domain ( Flexible, Full, Full Strict … )? :thinking:

Furthermore, is noTLSVerify option enabled on the Zero Trust tunnel for your public hostname?
Is your web application/service serving and listening on both 80 and 443 (or some other HTTP and HTTPS) ports?

So i had altered the option in the cloudflare dashboard to disable http/3, but it seems that it still was defaulting to using it.

Instead i updated the service file to specifically use http 2 protocol and it does seem stable now.

I guess dont always trust the easy toggles on the dashboard :grin:

As for the rest ive got cloudflare doing full management of dns, ssl etc.

My stuff is still in testing but later will be full containerised and not using streamlits “test” serving stuff

Thanks for the suggestions - of course i solved it just after posting here :sweat_smile: