Skip to content
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

Why are "ERR Couldn't start tunnel error="lookup protocol.argotunnel.com on 8.8.8.8:53" errors prompted? #388

Closed
pospos369 opened this issue Jun 3, 2021 · 8 comments

Comments

@pospos369
Copy link

pospos369 commented Jun 3, 2021

Why does the following error appear?
2021-06-03T03:06:06Z ERR Couldn't start tunnel error="lookup protocol.argotunnel.com on 8.8.8.8:53: read udp x.x.x.x:53135->8.8.8.8:53: no such host"
lookup protocol.argotunnel.com on 8.8.8.8:53: read udp x.x.x.x:53135->8.8.8.8:53: no such host

@nalakawula
Copy link

I also got the same error

2021-06-22T01:24:50Z ERR update check failed error="no release found"
2021-06-22T01:25:14Z ERR Couldn't start tunnel error="lookup protocol.argotunnel.com on 8.8.4.4:53: read udp 10.0.13.76:47803->8.8.4.4:53: i/o timeout"
lookup protocol.argotunnel.com on 8.8.4.4:53: read udp 10.0.13.76:47803->8.8.4.4:53: i/o timeout

@araczkowski
Copy link

in my case

 ERR Couldn't start tunnel error="lookup protocol.argotunnel.com on [::1]:53: read udp [::1]:57267->[::1]:53: read: connection refused"
89|tunnel  | lookup protocol.argotunnel.com on [::1]:53: read udp [::1]:57267->[::1]:53: read: connection refused

it happens only if I'm using named tunnel via config.yaml (new recommended way)

on the same device in legacy mode all is OK, any idea how to fix this???

Thx

@nmldiegues
Copy link
Contributor

Hello everyone,

Could you let us know what's the output of:

dig -t txt protocol.argotunnel.com

(or equivalent, depending on your OS)

@nmldiegues
Copy link
Contributor

This is the same as #423

@Zibri
Copy link

Zibri commented Jul 28, 2021

Reason: dns TXT records are sometimes filtered (here they are for example)

Solution:
use an https dns in cloudflared or try different dns records like SRV as a backup.

@araczkowski
Copy link

Hello @nmldiegues

this is the output of dig -t txt protocol.argotunnel.com

~ $ dig -t txt protocol.argotunnel.com

; <<>> DiG 9.16.11 <<>> -t txt protocol.argotunnel.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4007
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;protocol.argotunnel.com.	IN	TXT

;; ANSWER SECTION:
protocol.argotunnel.com. 299	IN	TXT	"http2=100"

;; Query time: 68 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Sat Jul 31 09:27:46 CEST 2021
;; MSG SIZE  rcvd: 74

Please let me know if I should check or do something more. Thanks!

@nmldiegues
Copy link
Contributor

Hello,

We have released https://github.com/cloudflare/cloudflared/releases/tag/2021.8.0 with two fixes related to this thread:

  • Prevent tunnel from running accidentally when only proxy-dns should run
  • Tolerate protocol TXT record lookup failing

Thanks for all the reports!

@araczkowski
Copy link

thank you - it works now :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants