I had an odd occurrence recently where my internet stopped working. When I eventually, after restarting the router a couple of times, I got it working again the network settings somehow went back to default including the DHCP, IP address scheme, router IP etc.
After a bit of editing I got my TrueNAS Scale server connected to the network again. However, I’m now struggling to get my CloudFlared instance back up again. I have tried restarting the container, reinstalling the app both from “TrueCharts” and “TrueNAS Community” all of which yield the same error message listed below. I suspect that it’s it because the container is unable to connect to the internet. Do apps on TrueNAS have a separate place to configure network settings outside the normal settings? But also the container logs do list the correct Tunnel ID. So is the tunnel ID embeded somewhere in the token it is it able to see the Cloudflare Tunnel but not initalize the connection. I've never had issued reconnecting to CloudFlare Tunnel like this before. I also followed the steps suggested in the log however, set ine is not very clear on what command needs to be run and as for #2 I already have Cloudflare set as my second DNS providor and I have been able to successfully ping the address 1.1.1.1.
Thanks!
After a bit of editing I got my TrueNAS Scale server connected to the network again. However, I’m now struggling to get my CloudFlared instance back up again. I have tried restarting the container, reinstalling the app both from “TrueCharts” and “TrueNAS Community” all of which yield the same error message listed below. I suspect that it’s it because the container is unable to connect to the internet. Do apps on TrueNAS have a separate place to configure network settings outside the normal settings? But also the container logs do list the correct Tunnel ID. So is the tunnel ID embeded somewhere in the token it is it able to see the Cloudflare Tunnel but not initalize the connection. I've never had issued reconnecting to CloudFlare Tunnel like this before. I also followed the steps suggested in the log however, set ine is not very clear on what command needs to be run and as for #2 I already have Cloudflare set as my second DNS providor and I have been able to successfully ping the address 1.1.1.1.
Thanks!
Code:
2023-11-26 04:15:22.099637+00:002023-11-26T04:15:22Z INF Starting tunnel tunnelID=... 2023-11-26 04:15:22.099716+00:002023-11-26T04:15:22Z INF Version 2023.10.0 2023-11-26 04:15:22.099731+00:002023-11-26T04:15:22Z INF GOOS: linux, GOVersion: go1.20.6, GoArch: amd64 2023-11-26 04:15:22.099737+00:002023-11-26T04:15:22Z INF Settings: map[no-autoupdate:true] 2023-11-26 04:15:22.099745+00:002023-11-26T04:15:22Z INF Environmental variables map[TUNNEL_TOKEN:*****] 2023-11-26 04:15:22.100106+00:002023-11-26T04:15:22Z INF Generated Connector ID: 70d4d77c-1928-4a89-818e-14c087ba2070 2023-11-26 04:15:26.102523+00:002023-11-26T04:15:26Z ERR Failed to fetch features, default to disable error="lookup cfd-features.argotunnel.com on 172.17.0.10:53: no such host" 2023-11-26 04:15:26.102969+00:002023-11-26T04:15:26Z ERR update check failed error="Get \"https://update.argotunnel.com?arch=amd64&clientVersion=2023.10.0&os=linux\": dial tcp: lookup update.argotunnel.com on 172.17.0.10:53: server misbehaving" 2023-11-26 04:15:30.112024+00:002023-11-26T04:15:30Z WRN Unable to lookup protocol percentage. 2023-11-26 04:15:30.112099+00:002023-11-26T04:15:30Z INF Initial protocol quic 2023-11-26 04:15:30.118757+00:002023-11-26T04:15:30Z INF ICMP proxy will use 172.16.33.201 as source for IPv4 2023-11-26 04:15:30.118787+00:002023-11-26T04:15:30Z INF ICMP proxy will use :: as source for IPv6 2023-11-26 04:15:49.125143+00:002023-11-26T04:15:49Z ERR edge discovery: error looking up Cloudflare edge IPs: the DNS query failed error="lookup _v2-origintunneld._tcp.argotunnel.com on 172.17.0.10:53: no such host" event=0 2023-11-26 04:15:49.125300+00:002023-11-26T04:15:49Z ERR Please try the following things to diagnose this issue: event=0 2023-11-26 04:15:49.125332+00:002023-11-26T04:15:49Z ERR 1. ensure that argotunnel.com is returning "origintunneld" service records. event=0 2023-11-26 04:15:49.125364+00:002023-11-26T04:15:49Z ERR Run your system's equivalent of: dig srv _origintunneld._tcp.argotunnel.com event=0 2023-11-26 04:15:49.125405+00:002023-11-26T04:15:49Z ERR 2. ensure that your DNS resolver is not returning compressed SRV records. event=0 2023-11-26 04:15:49.125425+00:002023-11-26T04:15:49Z ERR See GitHub issue https://github.com/golang/go/issues/27546 event=0 2023-11-26 04:15:49.125443+00:002023-11-26T04:15:49Z ERR For example, you could use Cloudflare's 1.1.1.1 as your resolver: event=0 2023-11-26 04:15:49.125472+00:002023-11-26T04:15:49Z ERR https://developers.cloudflare.com/1.1.1.1/setting-up-1.1.1.1/ event=0 2023-11-26 04:15:49.126514+00:002023-11-26T04:15:49Z INF Starting metrics server on 127.0.0.1:37203/metrics 2023-11-26 04:16:08.131649+00:002023-11-26T04:16:08Z ERR edge discovery: error looking up Cloudflare edge IPs: the DNS query failed error="lookup _v2-origintunneld._tcp.argotunnel.com on 172.17.0.10:53: no such host" event=0
