January 7, 20251 yr Every few months, I suddenly lose access to my apps. I check Unraid and container isn't running. I assume it crashes for some reason, but I don't see anything in the logs. Is it possible to write a script that would automatically start it?
January 15, 20251 yr On 11/30/2024 at 3:05 AM, k3vbert said: Hi guys, I have been using the Cloudflare tunnel successfully for a few days now. Yesterday, however, the Internet connection was reestablished (I was not at home) and my IP was changed. Since then, I have no longer been able to access my services via DNS. After checking Cloudflare, I saw that my IP had not been updated in A-Record. When I did this manually, I was able to access my services again. Does the container update the IP automatically or do I need to optimize it? Translated with DeepL.com (free version) If you use an A-record with a dynamic DNS, you will have to manually update in the Cloudflare DNS portion. I recommend not setting an A-Record with IP for the domain; instead use a CNAME pointing the domain to a dynamic DNS host (one that can monitor your IP changes and updates automatically.) I.E. (Not recommending any specific dynamic DNS hosts - just an example): -Create a DuckDNS account and domain through them. -Install the DuckDNS plugin on UnRAID -In the Cloudflare DNS page for your "traditional" domain (i.e. mycooldomain.com) Edited January 15, 20251 yr by timekills Consistency between instructions and image
January 21, 20251 yr Hi @Figro, I've been having an small issue with the Flood UI container the last few months. Every time I update the app all of my app settings reset (need to enter qbit information again, create account, and re-customize UI). I haven't changed anything with the Docker configuration. Any idea why this might be happening and what I could do to fix it? Running latest version of Flood UI, and Unraid 6.11.5. Thanks
January 21, 20251 yr 5 minutes ago, Chris W said: all of my app settings reset Looks like the template doesn't have a default setting for appdata. From the first post in the thread: On 10/17/2022 at 9:59 PM, Figro said: Setup the appdata path Did you? Post docker run
January 21, 20251 yr Author 14 hours ago, Chris W said: Hi @Figro, I've been having an small issue with the Flood UI container the last few months. Every time I update the app all of my app settings reset (need to enter qbit information again, create account, and re-customize UI). I haven't changed anything with the Docker configuration. Any idea why this might be happening and what I could do to fix it? Running latest version of Flood UI, and Unraid 6.11.5. Thanks Currently it puts the flood config in it's default location `~/.local/share/flood`. This config is reset on updates. Setting this up yourself might prove difficult as you would need to customize the Docker run command to specify an appdata path for it as mentioned here: https://github.com/jesec/flood/wiki/Install-Flood-on-Debian,-Ubuntu-and-derivatives with --rundir I am going to try and update the container and template to allow for this so it does not get overwritten on update. I'll update here with details. Thanks
January 21, 20251 yr Author 40 minutes ago, Figro said: Currently it puts the flood config in it's default location `~/.local/share/flood`. This config is reset on updates. Setting this up yourself might prove difficult as you would need to customize the Docker run command to specify an appdata path for it as mentioned here: https://github.com/jesec/flood/wiki/Install-Flood-on-Debian,-Ubuntu-and-derivatives with --rundir I am going to try and update the container and template to allow for this so it does not get overwritten on update. I'll update here with details. Thanks Seems like this was easier than anticipated. I already updated the template and that will be live in a couple of hours. To do it yourself you can simply add a container path variable `/.local/share/flood` with any host path you would like. Just make sure your permissions are sufficent
January 24, 20251 yr On 1/21/2025 at 9:56 AM, Figro said: Seems like this was easier than anticipated. I already updated the template and that will be live in a couple of hours. To do it yourself you can simply add a container path variable `/.local/share/flood` with any host path you would like. Just make sure your permissions are sufficent Thank you! Cheers
January 27, 20251 yr Hi there, I have been using Cloudflared-Tunnel since I setup my Unraid server 6 months ago, it was easy to install and works like a charm however I logged in to Cloudflare to setup another public hostname and was greeted with a message advising my certificate will expire in a few days. I have generated a new certificate but I don`t know what im supposed to do with it, can you \ anyone advise ? Many Thanks.
March 5, 20251 yr Hello, I've been using this docker to connect my tunnel with Cloudflare and has been working well for a while. Yesterday, the tunnel went down and I have not been able to get it to connect. I have restarted the Unraid server but still won't start. I did upgrade to Unraid 7.0.1 on Monday, so don't know if that's what broke it. However, I don't know if the issue is with the docker (that needs to be updated) or something on my end that broke. If anyone else has experienced this in the last day or so, were you able to fix it? Here is the log of the docker, I even changed the DNS to the Cloudflare dns, but did not make a difference, received the same error. I'm not sure how to read and interpret the dig command. % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 36.0M 100 36.0M 0 0 15.0M 0 0:00:02 0:00:02 --:--:-- 14.2M 2025-03-05T15:39:57Z INF Starting tunnel tunnelID=c7f2dc20-5eb2-41cf-9893-1c55639aa017 2025-03-05T15:39:57Z INF Version 2025.2.1 (Checksum afdfadd1ef552e66bffc35246fe30a9bd578356d2d386de95585ccfc432472b8) 2025-03-05T15:39:57Z INF GOOS: linux, GOVersion: go1.22.10, GoArch: amd64 2025-03-05T15:39:57Z INF Settings: map[token:*****] 2025-03-05T15:39:57Z INF Environmental variables map[TUNNEL_EDGE_BIND_ADDRESS: TUNNEL_EDGE_IP_VERSION:auto TUNNEL_GRACE_PERIOD:30s TUNNEL_LOGLEVEL:info TUNNEL_METRICS:0.0.0.0:46495 TUNNEL_ORIGIN_CERT: TUNNEL_REGION: TUNNEL_RETRIES:5 TUNNEL_TOKEN:***** TUNNEL_TRANSPORT_PROTOCOL:auto] 2025-03-05T15:39:57Z INF Generated Connector ID: 1dbf7920-688f-4f23-91ae-176d48b2458f 2025-03-05T15:39:58Z INF Initial protocol quic 2025-03-05T15:39:58Z INF ICMP proxy will use 172.19.0.2 as source for IPv4 2025-03-05T15:39:58Z INF ICMP proxy will use ::1 in zone lo as source for IPv6 2025-03-05T15:39:58Z ERR edge discovery: error looking up Cloudflare edge IPs: the DNS query failed error="lookup _v2-origintunneld._tcp.argotunnel.com on 127.0.0.11:53: server misbehaving" event=0 2025-03-05T15:39:58Z ERR Please try the following things to diagnose this issue: event=0 2025-03-05T15:39:58Z ERR 1. ensure that argotunnel.com is returning "origintunneld" service records. event=0 2025-03-05T15:39:58Z ERR Run your system's equivalent of: dig srv _origintunneld._tcp.argotunnel.com event=0 2025-03-05T15:39:58Z ERR 2. ensure that your DNS resolver is not returning compressed SRV records. event=0 2025-03-05T15:39:58Z ERR See GitHub issue https://github.com/golang/go/issues/27546 event=0 2025-03-05T15:39:58Z ERR For example, you could use Cloudflare's 1.1.1.1 as your resolver: event=0 2025-03-05T15:39:58Z ERR https://developers.cloudflare.com/1.1.1.1/setting-up-1.1.1.1/ event=0 2025-03-05T15:39:58Z INF ICMP proxy will use 172.19.0.2 as source for IPv4 2025-03-05T15:39:58Z INF ICMP proxy will use ::1 in zone lo as source for IPv6 2025-03-05T15:39:58Z INF Starting metrics server on [::]:46495/metrics 2025-03-05T15:39:58Z ERR edge discovery: error looking up Cloudflare edge IPs: the DNS query failed error="lookup _v2-origintunneld._tcp.argotunnel.com on 127.0.0.11:53: server misbehaving" event=0 2025-03-05T15:39:58Z ERR Please try the following things to diagnose this issue: event=0 2025-03-05T15:39:58Z ERR 1. ensure that argotunnel.com is returning "origintunneld" service records. event=0 2025-03-05T15:39:58Z ERR Run your system's equivalent of: dig srv _origintunneld._tcp.argotunnel.com event=0 2025-03-05T15:39:58Z ERR 2. ensure that your DNS resolver is not returning compressed SRV records. event=0 2025-03-05T15:39:58Z ERR See GitHub issue https://github.com/golang/go/issues/27546 event=0 2025-03-05T15:39:58Z ERR For example, you could use Cloudflare's 1.1.1.1 as your resolver: event=0 2025-03-05T15:39:58Z ERR https://developers.cloudflare.com/1.1.1.1/setting-up-1.1.1.1/ event=0 2025-03-05T15:39:58Z INF Tunnel server stopped 2025-03-05T15:39:58Z ERR Initiating shutdown error="Could not lookup srv records on _v2-origintunneld._tcp.argotunnel.com: lookup _v2-origintunneld._tcp.argotunnel.com on 127.0.0.11:53: server misbehaving" 2025-03-05T15:39:59Z INF Metrics server stopped Could not lookup srv records on _v2-origintunneld._tcp.argotunnel.com: lookup _v2-origintunneld._tcp.argotunnel.com on 127.0.0.11:53: server misbehaving ** Press ANY KEY to close this window **
June 26, 20251 yr Not sure if this is related to the above mentioned issue with the cloudflare tunnel, but within the last five days, I've been having issues with the cloudflare tunnel. Log looks something like this:2025-06-26T13:47:09Z INF Retrying connection in up to 4s connIndex=3 event=0 ip=198.41.200.332025-06-26T13:47:09Z INF Retrying connection in up to 4s connIndex=2 event=0 ip=198.41.192.372025-06-26T13:47:09Z ERR Failed to dial a quic connection error="failed to dial to edge with quic: timeout: no recent network activity" connIndex=1 event=0 ip=198.41.200.1932025-06-26T13:47:09Z ERR Failed to dial a quic connection error="failed to dial to edge with quic: timeout: no recent network activity" connIndex=0 event=0 ip=198.41.192.72025-06-26T13:47:09Z INF Retrying connection in up to 4s connIndex=1 event=0 ip=198.41.200.1932025-06-26T13:47:09Z INF Retrying connection in up to 4s connIndex=0 event=0 ip=198.41.192.72025-06-26T13:47:11Z ERR Connection terminated error="failed to dial to edge with quic: timeout: no recent network activity" connIndex=02025-06-26T13:47:11Z ERR Connection terminated error="failed to dial to edge with quic: timeout: no recent network activity" connIndex=12025-06-26T13:47:12Z ERR Connection terminated error="failed to dial to edge with quic: timeout: no recent network activity" connIndex=22025-06-26T13:47:13Z ERR Connection terminated error="failed to dial to edge with quic: timeout: no recent network activity" connIndex=32025-06-26T13:50:02Z INF Tunnel connection curve preferences: [X25519MLKEM768 CurveID(25497) CurveP256] connIndex=0 event=0 ip=198.41.192.2272025-06-26T13:50:02Z INF Tunnel connection curve preferences: [X25519MLKEM768 CurveID(25497) CurveP256] connIndex=3 event=0 ip=198.41.200.432025-06-26T13:50:02Z INF Tunnel connection curve preferences: [X25519MLKEM768 CurveID(25497) CurveP256] connIndex=2 event=0 ip=198.41.192.472025-06-26T13:50:02Z INF Tunnel connection curve preferences: [X25519MLKEM768 CurveID(25497) CurveP256] connIndex=1 event=0 ip=198.41.200.132025-06-26T13:50:02Z INF Registered tunnel connection connIndex=1 connection=90709d22-81ac-48f4-b231-5cd585284ac0 event=0 ip=198.41.200.13 location=ewr08 protocol=quic2025-06-26T13:50:02Z INF Registered tunnel connection connIndex=2 connection=0763e2dc-3c50-47bb-9d64-ec48ecd481f6 event=0 ip=198.41.192.47 location=ewr13 protocol=quic2025-06-26T13:50:03Z INF Registered tunnel connection connIndex=3 connection=36d6b4f7-bce9-4c12-8e86-6860f8cb1f5f event=0 ip=198.41.200.43 location=ewr14 protocol=quic2025-06-26T13:50:03Z INF Registered tunnel connection connIndex=0 connection=23de1620-b84b-462a-90ab-2e85de3edbcd event=0 ip=198.41.192.227 location=ewr01 protocol=quic2025-06-26T13:50:59Z WRN Failed to serve tunnel connection error="timeout: no recent network activity" connIndex=3 event=0 ip=198.41.200.432025-06-26T13:50:59Z WRN Serve tunnel error error="timeout: no recent network activity" connIndex=3 event=0 ip=198.41.200.432025-06-26T13:50:59Z INF Retrying connection in up to 1s connIndex=3 event=0 ip=198.41.200.432025-06-26T13:50:59Z WRN Failed to serve tunnel connection error="timeout: no recent network activity" connIndex=0 event=0 ip=198.41.192.2272025-06-26T13:50:59Z WRN Serve tunnel error error="timeout: no recent network activity" connIndex=0 event=0 ip=198.41.192.2272025-06-26T13:50:59Z INF Retrying connection in up to 1s connIndex=0 event=0 ip=198.41.192.2272025-06-26T13:50:59Z WRN Failed to serve tunnel connection error="timeout: no recent network activity" connIndex=1 event=0 ip=198.41.200.132025-06-26T13:50:59Z WRN Serve tunnel error error="timeout: no recent network activity" connIndex=1 event=0 ip=198.41.200.132025-06-26T13:50:59Z INF Retrying connection in up to 1s connIndex=1 event=0 ip=198.41.200.132025-06-26T13:50:59Z WRN Failed to serve tunnel connection error="timeout: no recent network activity" connIndex=2 event=0 ip=198.41.192.472025-06-26T13:50:59Z ERR Serve tunnel error error="timeout: no recent network activity" connIndex=2 event=0 ip=198.41.192.472025-06-26T13:50:59Z INF Retrying connection in up to 1s connIndex=2 event=0 ip=198.41.192.472025-06-26T13:50:59Z ERR Connection terminated error="timeout: no recent network activity" connIndex=22025-06-26T13:51:00Z ERR Connection terminated error="timeout: no recent network activity" connIndex=32025-06-26T13:51:00Z ERR Connection terminated error="timeout: no recent network activity" connIndex=12025-06-26T13:51:00Z ERR Connection terminated error="timeout: no recent network activity" connIndex=02025-06-26T13:54:09Z INF Tunnel connection curve preferences: [X25519MLKEM768 CurveID(25497) CurveP256] connIndex=2 event=0 ip=198.41.192.72025-06-26T13:54:09Z INF Tunnel connection curve preferences: [X25519MLKEM768 CurveID(25497) CurveP256] connIndex=0 event=0 ip=198.41.192.272025-06-26T13:54:09Z INF Tunnel connection curve preferences: [X25519MLKEM768 CurveID(25497) CurveP256] connIndex=1 event=0 ip=198.41.200.1932025-06-26T13:54:09Z INF Tunnel connection curve preferences: [X25519MLKEM768 CurveID(25497) CurveP256] connIndex=3 event=0 ip=198.41.200.632025-06-26T13:54:09Z INF Registered tunnel connection connIndex=1 connection=07e9ac79-6136-4520-9ba6-1ed60a28d1f3 event=0 ip=198.41.200.193 location=ewr12 protocol=quic2025-06-26T13:54:09Z INF Registered tunnel connection connIndex=0 connection=7690f0ce-0dce-4e77-ad54-dc51a17ffe68 event=0 ip=198.41.192.27 location=ewr13 protocol=quic2025-06-26T13:54:09Z INF Registered tunnel connection connIndex=2 connection=f0330b22-86ba-421c-b76f-db41baca9040 event=0 ip=198.41.192.7 location=ewr11 protocol=quic2025-06-26T13:54:09Z INF Registered tunnel connection connIndex=3 connection=9cbc1b8b-7ee1-4b28-9384-057177c386f6 event=0 ip=198.41.200.63 location=ewr08 protocol=quic2025-06-26T13:54:58Z WRN Failed to serve tunnel connection error="timeout: no recent network activity" connIndex=3 event=0 ip=198.41.200.632025-06-26T13:54:58Z WRN Serve tunnel error error="timeout: no recent network activity" connIndex=3 event=0 ip=198.41.200.632025-06-26T13:54:58Z INF Retrying connection in up to 1s connIndex=3 event=0 ip=198.41.200.632025-06-26T13:54:59Z WRN Failed to serve tunnel connection error="timeout: no recent network activity" connIndex=1 event=0 ip=198.41.200.1932025-06-26T13:54:59Z WRN Serve tunnel error error="timeout: no recent network activity" connIndex=1 event=0 ip=198.41.200.1932025-06-26T13:54:59Z INF Retrying connection in up to 1s connIndex=1 event=0 ip=198.41.200.1932025-06-26T13:54:59Z WRN Failed to serve tunnel connection error="timeout: no recent network activity" connIndex=0 event=0 ip=198.41.192.272025-06-26T13:54:59Z WRN Serve tunnel error error="timeout: no recent network activity" connIndex=0 event=0 ip=198.41.192.272025-06-26T13:54:59Z INF Retrying connection in up to 1s connIndex=0 event=0 ip=198.41.192.272025-06-26T13:54:59Z WRN Failed to serve tunnel connection error="timeout: no recent network activity" connIndex=2 event=0 ip=198.41.192.72025-06-26T13:54:59Z ERR Serve tunnel error error="timeout: no recent network activity" connIndex=2 event=0 ip=198.41.192.72025-06-26T13:54:59Z INF Retrying connection in up to 1s connIndex=2 event=0 ip=198.41.192.72025-06-26T13:55:00Z ERR Connection terminated error="timeout: no recent network activity" connIndex=02025-06-26T13:55:00Z ERR Connection terminated error="timeout: no recent network activity" connIndex=32025-06-26T13:55:00Z ERR Connection terminated error="timeout: no recent network activity" connIndex=12025-06-26T13:55:00Z ERR Connection terminated error="timeout: no recent network activity" connIndex=22025-06-26T13:58:57Z INF Tunnel connection curve preferences: [X25519MLKEM768 CurveID(25497) CurveP256] connIndex=2 event=0 ip=198.41.192.372025-06-26T13:58:57Z INF Tunnel connection curve preferences: [X25519MLKEM768 CurveID(25497) CurveP256] connIndex=1 event=0 ip=198.41.200.332025-06-26T13:58:57Z INF Tunnel connection curve preferences: [X25519MLKEM768 CurveID(25497) CurveP256] connIndex=0 event=0 ip=198.41.192.1072025-06-26T13:58:57Z INF Tunnel connection curve preferences: [X25519MLKEM768 CurveID(25497) CurveP256] connIndex=3 event=0 ip=198.41.200.532025-06-26T13:59:02Z ERR Failed to dial a quic connection error="failed to dial to edge with quic: timeout: no recent network activity" connIndex=1 event=0 ip=198.41.200.332025-06-26T13:59:02Z ERR Failed to dial a quic connection error="failed to dial to edge with quic: timeout: no recent network activity" connIndex=0 event=0 ip=198.41.192.1072025-06-26T13:59:02Z ERR Failed to dial a quic connection error="failed to dial to edge with quic: timeout: no recent network activity" connIndex=2 event=0 ip=198.41.192.372025-06-26T13:59:02Z INF Retrying connection in up to 4s connIndex=1 event=0 ip=198.41.200.332025-06-26T13:59:02Z INF Retrying connection in up to 4s connIndex=2 event=0 ip=198.41.192.372025-06-26T13:59:02Z ERR Failed to dial a quic connection error="failed to dial to edge with quic: timeout: no recent network activity" connIndex=3 event=0 ip=198.41.200.532025-06-26T13:59:02Z INF Retrying connection in up to 4s connIndex=0 event=0 ip=198.41.192.1072025-06-26T13:59:02Z INF Retrying connection in up to 4s connIndex=3 event=0 ip=198.41.200.532025-06-26T13:59:02Z ERR Connection terminated error="failed to dial to edge with quic: timeout: no recent network activity" connIndex=32025-06-26T13:59:03Z ERR Connection terminated error="failed to dial to edge with quic: timeout: no recent network activity" connIndex=12025-06-26T13:59:03Z ERR Connection terminated error="failed to dial to edge with quic: timeout: no recent network activity" connIndex=02025-06-26T13:59:04Z ERR Connection terminated error="failed to dial to edge with quic: timeout: no recent network activity" connIndex=22025-06-26T14:02:23Z INF Tunnel connection curve preferences: [X25519MLKEM768 CurveID(25497) CurveP256] connIndex=2 event=0 ip=198.41.192.472025-06-26T14:02:23Z INF Tunnel connection curve preferences: [X25519MLKEM768 CurveID(25497) CurveP256] connIndex=0 event=0 ip=198.41.192.372025-06-26T14:02:23Z INF Tunnel connection curve preferences: [X25519MLKEM768 CurveID(25497) CurveP256] connIndex=1 event=0 ip=198.41.200.632025-06-26T14:02:23Z INF Tunnel connection curve preferences: [X25519MLKEM768 CurveID(25497) CurveP256] connIndex=3 event=0 ip=198.41.200.332025-06-26T14:02:28Z ERR Failed to dial a quic connection error="failed to dial to edge with quic: timeout: no recent network activity" connIndex=3 event=0 ip=198.41.200.332025-06-26T14:02:28Z ERR Failed to dial a quic connection error="failed to dial to edge with quic: timeout: no recent network activity" connIndex=1 event=0 ip=198.41.200.632025-06-26T14:02:28Z INF Retrying connection in up to 8s connIndex=1 event=0 ip=198.41.200.632025-06-26T14:02:28Z INF Retrying connection in up to 8s connIndex=3 event=0 ip=198.41.200.332025-06-26T14:02:28Z ERR Failed to dial a quic connection error="failed to dial to edge with quic: timeout: no recent network activity" connIndex=2 event=0 ip=198.41.192.472025-06-26T14:02:28Z ERR Failed to dial a quic connection error="failed to dial to edge with quic: timeout: no recent network activity" connIndex=0 event=0 ip=198.41.192.372025-06-26T14:02:28Z INF Retrying connection in up to 8s connIndex=2 event=0 ip=198.41.192.472025-06-26T14:02:28Z INF Retrying connection in up to 8s connIndex=0 event=0 ip=198.41.192.372025-06-26T14:02:29Z ERR Connection terminated error="failed to dial to edge with quic: timeout: no recent network activity" connIndex=22025-06-26T14:02:29Z ERR Connection terminated error="failed to dial to edge with quic: timeout: no recent network activity" connIndex=12025-06-26T14:02:32Z ERR Connection terminated error="failed to dial to edge with quic: timeout: no recent network activity" connIndex=32025-06-26T14:02:34Z ERR Connection terminated error="failed to dial to edge with quic: timeout: no recent network activity" connIndex=0I am not sure what to make of it. If I restart the tunnel it come up for a few seconds, then goes down again. I was able to get it to last for a few days before going back down again. Also, I recently upgraded to 7.1.4 as well. Any thoughts?
July 13, 2025Jul 13 After update from Unraid 7.0.1 to 7.1.4 I can't start Unraid-Cloudflared-Tunnel it show "Execution Error and Server Error"
August 25, 2025Aug 25 I was checking the container logs, and did see the following error? 2025-08-25T20:25:38Z ERR Cannot determine default origin certificate path. No file cert.pem in [~/.cloudflared ~/.cloudflare-warp ~/cloudflare-warp /etc/cloudflared /usr/local/etc/cloudflared]. You need to specify the origin certificate path by specifying the origincert option in the configuration file, or set TUNNEL_ORIGIN_CERT environment variable originCertPath= When I was looking at the variable in the container said to go to download a cert.pem at this link: https://dash.cloudflare.com/argotunnelI did this, but how do I put this file in this variable:Also is this really needed? Or can I ignore the error?
August 27, 2025Aug 27 On 8/25/2025 at 10:34 PM, de Techneut said:I did this, but how do I put this file in this variable:No idea about the necessity, but you can copy the file into the appdata/clouflared foldder on your unraid system which is available as /appdata/ inside the container. So you'd write /appdata/cert.pem - worked for meI have a question on my own: does this support multiple tunnels? How would I add another tunnel token?
August 30, 2025Aug 30 On 8/27/2025 at 11:19 PM, wambo said:No idea about the necessity, but you can copy the file into the appdata/clouflared foldder on your unraid system which is available as /appdata/ inside the container. So you'd write /appdata/cert.pem - worked for meI have a question on my own: does this support multiple tunnels? How would I add another tunnel token?Managed to get it working. What I needed to do wat map the directory of the cert.pem to /etc/cloudflared/cert.pemAnd set the variable TUNNEL_ORIGIN_CERT to /etc/cloudflared/cert.pemNow it is working!
October 31, 2025Oct 31 After messing around with the clouflared apps from the Unraid app store with no success, I did the following...I installed the Dockge app. Dockge manages docker compose containers. I had used it before on multiple other machines. Easily manages docker compose containers.In this case you copy the cloudflared docker run command into Dockge and it converts it into docker compose and manages it.Cloudflared shows up in Unraid's docker tab as a 3rd party container, but it works. Easy, Peasy!I have 3 Unraid boxes and each of them is using cloudflared.
November 4, 2025Nov 4 Anyone else having issues post 7.2.0?My cloudflared isn't working for connecting to many local services and the logs show lots of the following:"025-11-04T19:34:58Z ERR Request failed error="Incoming request ended abruptly: context canceled" connIndex=3 dest=https://xxxxx.xxxxxxxxxx.xx/ event=0 ip=198.41.192.47 type=http"My network setup is a little convoluted.I can access all the services locally from my PC, so all are running and fine, just any attempt by the tunnel to access a service ends with the above errors.@Figro My cloudflared container is in a vlan br0.60Seems to be containers in custom networks, those that can be set to 'host' are working fine, and so are those in other vlans (e.g. br0.40) and I can access the unraid NAS itself via the tunnel..Weird.. Edited November 5, 2025Nov 5 by Snubbers
February 24Feb 24 Is there anyway to run multiples of this docker without errors? I know I can add routes to the same one in cloudflare but have a couple lets me set different logins using cloudflare and I do kinda need that. Any thoughts? Seems to be an issue with duplicate ports maybe?
February 24Feb 24 Sorted. Just had to go into advanced mode and change the webui address (I just increased the number by 1), then click show more settings at the bottom and again make the same change in both the Tunnel Metrics field and the Metrics Port field (again I just increased the number by 1). Worked perfectly. Now I can use CloudFlare to password the tunnels with different logins and I can share some and not others. Perfect setup for me. Edited February 24Feb 24 by Dick Dawson typo
March 9Mar 9 Found this container, set it up, and it works great.While it works great for one (1) tunnel, is there a way to get a second tunnel added to it? I've tried adding another variable to the container, however the connection always seems to drop after a minute (at least from Cloudflare's side). The original (first) connection/tunnel remains up, it's just getting the second one seems to cause trouble.
May 13May 13 On 1/7/2025 at 3:57 PM, Gobblerpl said:Every few months, I suddenly lose access to my apps. I check Unraid and container isn't running. I assume it crashes for some reason, but I don't see anything in the logs.Is it possible to write a script that would automatically start it?Same issue here. Yes you can use user scripts plugin to restart it, my script is simply: "docker restart Unraid-Cloudflared-Tunnel" and is scheduled to run weekly.
May 27May 27 On 5/13/2026 at 6:19 PM, Parax said:Same issue here.Yes you can use user scripts plugin to restart it, my script is simply: "docker restart Unraid-Cloudflared-Tunnel" and is scheduled to run weekly.in my case i have the docker already in a schedule on updates to the docker and also for backup. I'm now monitoring how often it happens but i can't see any log about it breaking. i almost feel like doing a force update in the docker
May 28May 28 10 hours ago, gacpac said:in my case i have the docker already in a schedule on updates to the docker and also for backup. I'm now monitoring how often it happens but i can't see any log about it breaking. i almost feel like doing a force update in the dockerI'm suddenly seeing the docker down also. Last line in the logs this time was it was doing an update 4 days ago (my regular scheduled weekly docker update slot). It's the second time in a month it's happened where it's not come back up (nothing in the logs to say why). Never had an issue with it before. Very strange. Edited May 28May 28 by unraid-user
June 10Jun 10 On 5/28/2026 at 6:03 AM, unraid-user said:I'm suddenly seeing the docker down also. Last line in the logs this time was it was doing an update 4 days ago (my regular scheduled weekly docker update slot). It's the second time in a month it's happened where it's not come back up (nothing in the logs to say why). Never had an issue with it before. Very strange.i'm having the same problem. I'm monitoring the docker now with uptimekuma. and nothing happened last night at 3am. What could i provide from my end because i don't see logs either anywhere, docker just stopped. Ideally yes i could simply have a script to start a docker manually like a watchdog, but that's just a band aid not the real fix.
June 19Jun 19 On 6/10/2026 at 6:36 PM, gacpac said:i'm having the same problem. I'm monitoring the docker now with uptimekuma. and nothing happened last night at 3am.What could i provide from my end because i don't see logs either anywhere, docker just stopped. Ideally yes i could simply have a script to start a docker manually like a watchdog, but that's just a band aid not the real fix.I have the same question too. My docker logs don't really provide much info. I have added --restart unless-stopped to the extra params section just so it comes back up if it crashes. Not a proper solution really as I'd love to know why it's begun to crash more recently but at least (hopefully) it'll come back up the next time it goes down
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.