Cloudflared (argo tunnel) login problem

Is anyone else having trouble logging into argo tunnel from a new client? It seems that the certificates never get created after clicking authorize. I’ve tried it with a couple different client os’s (Debian and Mac OS) and a couple different browsers (Safari, Firefox, Edge.) I’m using the latest version of cloudflared and running on a newly provisioned free account with argo enabled. If I use the logging parameter, no log file is generated. Here’s the output from cloudflared (from the Mac OS attempt):

===============================================
A browser window should have opened at the following URL:

https://dash.cloudflare.com/argotunnel?callback=https%3A%2F%2Flogin.cloudflarewarp.com%2F{unique token}%3D

If the browser failed to open, open it yourself and visit the URL above.
INFO[0050] Waiting for login…
INFO[0101] Waiting for login…
INFO[0151] Waiting for login…
INFO[0201] Waiting for login…
INFO[0252] Waiting for login…
INFO[0302] Waiting for login…
INFO[0352] Waiting for login…
INFO[0402] Waiting for login…
INFO[0452] Waiting for login…
INFO[0503] Waiting for login…
Failed to write the certificate due to the following error:
Failed to fetch resource

Your browser will download the certificate instead. You will have to manually
copy it to the following path:

/Users/{local username}/.cloudflared/cert.pem

================================================

The browser never presents a certificate and just stays on the cancel/authorize screen. Clicking authorize too many times results in a 429 “too many requests” error.

I have a support ticket open for this issue.

It looks like at least one other person has had this issue, but it was a year ago
https://community.cloudflare.com/t/argo-tunnel-issues-in-toronto/27002

Update: Got this working in a different browser. After installing the latest Chrome, the process works as documented. My install of Safari and Firefox are a bit old at this point and I suspect that is the issue. As far as Edge… well I’m comfortable chalking that one up to it being Edge. I’ll update Firefox and Safari and report back.

Updating the browser versions did the trick.

3 Likes