tamhamilton

Same issue here. cloudflared version 2020.10.0 (built 2020-10-06-1530 UTC) PRETTY_NAME="Raspbian GNU/Linux 10 (buster)" NAME="Raspbian GNU/Linux" VERSION_ID="10" VERSION="10 (buster)" VERSION_CODENAME=buster ID=raspbian ID_LIKE=debian HOME_URL="http://www.raspbian.org/" SUPPORT_URL="http://www.raspbian.org/RaspbianForums" BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"

OK, fixed it. Well, more specifically, they fixed it... This is how: Roll back cloudflared to an older, stable, version: `wget https://bin.equinox.io/c/VdrWdbjqyF/cloudflared-stable-linux-arm.tgz` `tar -xvzf cloudflared-stable-linux-arm.tgz` `sudo systemctl stop cloudflared` `sudo...

Cloudflared definitely reporting v2020.10.2?

That's what I thought, but I checked the version after my initial steps and it didn't report 2020.10.2 (can't remember what it actually was though). Ran the update command, and...

And what now happens when you run `cloudflared update` ?

The forced downgrade mentioned by @daltoniam didn't work for me either, attempting to go from 2020.10.2 to 2020.11.3, and the straight update also failed. However the steps I used previously...

Successfully updated cloudflared to 2020.11.4 from 2020.11.3 using the automatic updater; seems like the fix in .3 is functional!

Still intermittently getting this issue, actually. Just updated to 2020.11.10 successfully now, but was getting the error earlier today with 2020.11.9. Is it just 'internet weather'?

What version of cloudflared are you running? There are a couple of workarounds further up this thread...