Closed Kirizan closed 3 years ago
Unfortunately, Cloudflare does not properly tag their docker images with latest
. You've likely pulled an old version of cloudflared (like I did). Visit this page and copy the pull command of the most recent image (you'll see a docker pull
command on the right side). For example, I used:
docker pull cloudflare/cloudflared:2021.7.0-amd64
This pulls the latest image. You can either reference those tags in the commands or use the following commands to remove the old one and tag the new one as latest
.
docker rmi cloudflare/cloudflared:latest
docker tag cloudflare/cloudflared:2021.7.0-amd64 cloudflare/cloudflared:latest
Then you may need to remove the faulty tunnel before recreating it (replace TUNNELNAME
):
docker run -it --rm -v /mnt/user/appdata/cloudflared:/home/nonroot/.cloudflared/ cloudflare/cloudflared tunnel delete TUNNELNAME
This did it, now everything is working as expected. Thank you very much!
When following the guide to create the tunnel I run the command:
However there is no UUID assigned. The output from the above command is:
The command
docker run -it --rm -v /mnt/user/appdata/cloudflared:/home/nonroot/.cloudflared/ cloudflare/cloudflared tunnel login
was successful, and shows active when I browse to the linked site. Thecert.pem
file exists in the cloudflared directory.The file
/.json
contains anAccountTag
andTunnelSecret
entry. If I use theAccountTag
as the UUID in theconfig.yaml
and point to the/.json
file, then the Unraid container logs show:If I try to list the tunnels (to get the UUID there), I get the error:
If I try to rename the
/.json
file toAccountTag.json
(replacing with the actual value from the account tag, and updateding theconfig.yaml
), then the Unraid container logs show:If I try to create other tunnels, it's the same. I can't find any tunnel list from within the CloudFlare to try to find the correct UUID. Have you see anything like this, or how to fix it?