Cloudflared tunnel doesn't display the free tunnel URL

Performance Cloudflare Tunnel
#1

Hi there,

[[email protected] ~]# cloudflared tunnel --url http://localhost:80
INFO[2020-12-05T04:09:37Z] Version 2020.11.11
INFO[2020-12-05T04:09:37Z] GOOS: linux, GOVersion: go1.15.5, GoArch: arm
INFO[2020-12-05T04:09:37Z] Environment variables map[logfile:/var/log/cloudflared.log proxy-dns:true proxy-dns-address:127.0.0.1 proxy-dns-port:5300 proxy-dns-upstream:https://1.1.1.1/dns-query, https://1.0.0.1/dns-query url:http://localhost:80]
INFO[2020-12-05T04:09:37Z] Adding DNS upstream - url: https://1.1.1.1/dns-query
INFO[2020-12-05T04:09:37Z] Adding DNS upstream - url: https://1.0.0.1/dns-query
INFO[2020-12-05T04:09:37Z] Starting DNS over HTTPS proxy server on: dns://127.0.0.1:5300
INFO[2020-12-05T04:09:37Z] cloudflared will not automatically update when run from the shell. To enable auto-updates, run cloudflared as a service: https://developers.cloudflare.com/argo-tunnel/reference/service/
INFO[2020-12-05T04:09:37Z] Starting metrics server on 127.0.0.1:39209/metrics

I do not see the free tunnel URL.

Is it a know issue? I am missing something?
This is on a Arch Linux container, armv7l.

#2

How long after the initiation of the command did you wait? On my machine(OSX) with the same build a tunnel URL appeared in the command line interface ~ 1 minute later.

#3

It is possible that it is picking up a previously used config.yml

#4

This a fresh install without config or credentials.

#5

Tried for 5 minutes:

[[email protected] ~]# date
Sat Dec  5 04:47:06 UTC 2020
[[email protected] ~]# timeout 5m cloudflared tunnel --url http://localhost:80; date
INFO[2020-12-05T04:47:19Z] Version 2020.11.11
INFO[2020-12-05T04:47:19Z] GOOS: linux, GOVersion: go1.15.5, GoArch: arm
INFO[2020-12-05T04:47:19Z] Environment variables map[logfile:/var/log/cloudflared.log proxy-dns:true proxy-dns-address:127.0.0.1 proxy-dns-port:5300 proxy-dns-upstream:https://1.1.1.1/dns-query, https://1.0.0.1/dns-query url:http://localhost:80]
INFO[2020-12-05T04:47:19Z] Adding DNS upstream - url: https://1.1.1.1/dns-query
INFO[2020-12-05T04:47:19Z] Adding DNS upstream - url: https://1.0.0.1/dns-query
INFO[2020-12-05T04:47:19Z] Starting DNS over HTTPS proxy server on: dns://127.0.0.1:5300
INFO[2020-12-05T04:47:19Z] cloudflared will not automatically update when run from the shell. To enable auto-updates, run cloudflared as a service: https://developers.cloudflare.com/argo-tunnel/reference/service/
INFO[2020-12-05T04:47:19Z] Starting metrics server on 127.0.0.1:41629/metrics
INFO[2020-12-05T04:52:18Z] terminating due to signal terminated
INFO[2020-12-05T04:52:18Z] Quitting...
INFO[2020-12-05T04:52:19Z] Metrics server stopped
Sat Dec  5 04:52:19 UTC 2020
#6

So I straced the process and saw a lot of:

[pid 23004] <... recvmsg resumed>{msg_namelen=112}, 0) = -1 EAGAIN (Resource temporarily unavailable)

[pid 22998] futex(0x1c1c4e0, FUTEX_WAIT_PRIVATE, 0, {tv_sec=0, tv_nsec=970683986}) = -1 ETIMEDOUT (Connection timed out)

[pid 23004] <... recvmsg resumed>{msg_namelen=112}, 0) = -1 EAGAIN (Resource temporarily unavailable)
[pid 22998] futex(0x1c1c4e0, FUTEX_WAIT_PRIVATE, 0, {tv_sec=0, tv_nsec=551261803}) = -1 ETIMEDOUT (Connection timed out)

So it sounds related to some issue with a futex…? Like some internal process communication?
Here is a go trace if it may help: https://share.benpro.fr/selif/trace306204742.file