Argo Tunnel error

bug

#1

Hello,

Since today I’ve been getting some errors while starting my Argo Tunnel. Currently seeing the following error:

time="2019-02-15T19:24:52Z" level=info msg="Build info: {GoOS:linux GoVersion:go1.9.3 GoArch:amd64}"
time="2019-02-15T19:24:52Z" level=info msg="Version 2019.2.0"
time="2019-02-15T19:24:52Z" level=info msg="Flags map[config:/local/etc/cloudflared/config.yml 
hostname:***** logfile:/opt/cloudflare/log/cloudflared.log no-autoupdate:true url:http://172.31.1.4]"
time="2019-02-15T19:24:52Z" level=info msg="Starting metrics server" addr="127.0.0.1:34553"
time="2019-02-15T19:24:52Z" level=info msg="Proxying tunnel requests to http://172.31.1.4"
time="2019-02-15T19:24:52Z" level=warning msg="You requested 4 HA connections but I can give you at most 2."```

And just before that

time="2019-02-15T19:24:52Z" level=info msg="Build info: {GoOS:linux GoVersion:go1.9.3 GoArch:amd64}"
time="2019-02-15T19:24:52Z" level=info msg="Version 2019.2.0"
time="2019-02-15T19:24:52Z" level=info msg="Flags map[config:/local/etc/cloudflared/config.yml hostname:****** logfile:/opt/cloudflare/log/cloudflared.log no-autoupdate:true url:http://172.31.1.4]"
time="2019-02-15T19:24:52Z" level=info msg="Starting metrics server" addr="127.0.0.1:34553"
time="2019-02-15T19:24:52Z" level=info msg="Proxying tunnel requests to http://172.31.1.4"
time="2019-02-15T19:24:52Z" level=warning msg="You requested 4 HA connections but I can give you at most 2."
time="2019-02-15T19:29:53Z" level=info msg="Connected to FRA"
time="2019-02-15T19:29:53Z" level=error msg="Register tunnel error from server side" connectionID=0 error="Server error: tunnel provisioning timed out"
time="2019-02-15T19:29:54Z" level=info msg="Retrying in 1s seconds"

Config has been untouched compared to the version that was always working.

Worth noting is that, as far as I’m aware, before this I was always connected to AMS (which makes sense since we’re located closely to there).

We’re currently seeing Error 1016 Origin DNS Error issues from the frontend.

How can I further debug the issue / fix it ?


#2

I am seeing the same errors.


#3

I have reported to Argo team, and a fix is on the way. :+1:


#4

It is solved. Restart your argo tunnels if problems continues.
https://www.cloudflarestatus.com/incidents/splpn14d97gt


#5

I am still seeing this issue today.

I am trying to setup Argo Tunnel to point to a Proxmox web interface.

At first - it wouldn’t work, as the Proxmox certificate wasn’t trusted:

[email protected]:~/.cloudflared# cloudflared tunnel --hostname proxmox.example.com --url https://localhost:8006
WARN[0000] Cannot determine default configuration path. No file [config.yml config.yaml] in [~/.cloudflared ~/.cloudflare-warp ~/cloudflare-warp /usr/local/etc/cloudflared /etc/cloudflared] 
INFO[0000] Build info: {GoOS:linux GoVersion:go1.9.3 GoArch:amd64} 
INFO[0000] Version 2019.2.0                             
INFO[0000] Flags map[hostname:proxmox.matthiasmedia.com.au url:https://localhost:8006] 
INFO[0000] 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[0000] Starting metrics server                       addr="127.0.0.1:46121"
INFO[0000] Proxying tunnel requests to https://localhost:8006 
ERRO[0000] unable to connect to the origin               error="Get https://localhost:8006: x509: certificate signed by unknown authority"

Then I used --no-tls-verify:

[email protected]:~/.cloudflared# cloudflared tunnel --hostname proxmox.example.com --no-tls-verify --url https://localhost:8006
WARN[0000] Cannot determine default configuration path. No file [config.yml config.yaml] in [~/.cloudflared ~/.cloudflare-warp ~/cloudflare-warp /usr/local/etc/cloudflared /etc/cloudflared] 
INFO[0000] Build info: {GoOS:linux GoVersion:go1.9.3 GoArch:amd64} 
INFO[0000] Version 2019.2.0                             
INFO[0000] Flags map[hostname:proxmox.example.com no-tls-verify:true url:https://localhost:8006] 
INFO[0000] 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[0000] Starting metrics server                       addr="127.0.0.1:41665"
INFO[0000] Proxying tunnel requests to https://localhost:8006 
INFO[0008] Connected to SYD                             
INFO[0008] Each HA connection's tunnel IDs: map[0:gqliz63rq8p8i53upd49i0p27l8s8zr8bzyt74l4aphbb0rb32k0] 
INFO[0008] Route propagating, it may take up to 1 minute for your new route to become functional 
INFO[0016] Connected to SYD                             
INFO[0016] Each HA connection's tunnel IDs: map[0:gqliz63rq8p8i53upd49i0p27l8s8zr8bzyt74l4aphbb0rb32k0 2:gqliz63rq8p8i53upd49i0p27l8s8zr8bzyt74l4aphbb0rb32k0] 
INFO[0016] Route propagating, it may take up to 1 minute for your new route to become functional 

INFO[0309] Connected to MEL                             
INFO[0311] Connected to MEL                             
ERRO[0339] Register tunnel error from server side        connectionID=1 error="Server error: tunnel provisioning timed out"
INFO[0341] Retrying in 1s seconds                       
ERRO[0341] Register tunnel error from server side        connectionID=3 error="Server error: tunnel provisioning timed out"
INFO[0341] Retrying in 1s seconds                       
INFO[0349] Connected to MEL                             
INFO[0349] Each HA connection's tunnel IDs: map[0:gqliz63rq8p8i53upd49i0p27l8s8zr8bzyt74l4aphbb0rb32k0 2:gqliz63rq8p8i53upd49i0p27l8s8zr8bzyt74l4aphbb0rb32k0 1:gqliz63rq8p8i53upd49i0p27l8s8zr8bzyt74l4aphbb0rb32k0] 
INFO[0349] Route propagating, it may take up to 1 minute for your new route to become functional 
INFO[0349] Connected to MEL                             
INFO[0349] Each HA connection's tunnel IDs: map[0:gqliz63rq8p8i53upd49i0p27l8s8zr8bzyt74l4aphbb0rb32k0 2:gqliz63rq8p8i53upd49i0p27l8s8zr8bzyt74l4aphbb0rb32k0 1:gqliz63rq8p8i53upd49i0p27l8s8zr8bzyt74l4aphbb0rb32k0 3:gqliz63rq8p8i53upd49i0p27l8s8zr8bzyt74l4aphbb0rb32k0] 
INFO[0349] Route propagating, it may take up to 1 minute for your new route to become functional 	

And I can confirm the tunnel isn’t accessible from another machine.

Any idea why I’m still seeing Server error: tunnel provisioning timed out?


#6

If your are clearly inside your machine(localhost). Why not just go with http?
At I don’t know of any advantages.
Argo Tunnel will always be encrypted.