starred/uptime-kuma

Fork 0

mirror of https://github.com/louislam/uptime-kuma.git synced 2026-03-02 22:57:00 -05:00

Cloudflare Tunnel client outdated #1025

New issue

Closed

opened 2026-02-28 02:07:34 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-28 02:07:34 -05:00

Owner

Originally created by @computman007 on GitHub (Apr 24, 2022).

⚠️ Please verify that this bug has NOT been raised before.

I checked and didn't find similar issue

🛡️ Security Policy

I agree to have read this project Security Policy

📝 Describe your problem

After activating the Cloudflare tunnels, it show in the Cloudflare interface that the client is outdated

Can we update it mannually (how ?) or this will be fixed in next release ?

🐻 Uptime-Kuma Version

1.14.1

💻 Operating System and Arch

Ubuntu 20.04

🌐 Browser

Vivaldi last version

🐋 Docker Version

Docker Version 20.10.14

🟩 NodeJS Version

No response

Originally created by @computman007 on GitHub (Apr 24, 2022). ### ⚠️ Please verify that this bug has NOT been raised before. - [X] I checked and didn't find similar issue ### 🛡️ Security Policy - [X] I agree to have read this project [Security Policy](https://github.com/louislam/uptime-kuma/security/policy) ### 📝 Describe your problem After activating the Cloudflare tunnels, it show in the Cloudflare interface that the client is outdated Can we update it mannually (how ?) or this will be fixed in next release ? ![2022-04-25 00_16_00-Clipboard](https://user-images.githubusercontent.com/25824896/164999135-3f79990d-5267-45bd-b3be-c6897726dbb0.png) ### 🐻 Uptime-Kuma Version 1.14.1 ### 💻 Operating System and Arch Ubuntu 20.04 ### 🌐 Browser Vivaldi last version ### 🐋 Docker Version Docker Version 20.10.14 ### 🟩 NodeJS Version _No response_

deekerman

2026-02-28 02:07:34 -05:00

closed this issue
added the
help
label

deekerman commented

2026-02-28 02:07:39 -05:00

Author

Owner

@gaby commented on GitHub (Apr 24, 2022):

@computman007 I think this is a CI issue, I just submitted a PR to take care of this in the future. Ideally every time a new release of Uptime-Kuma is created the latest version of cloudflared and other dependencies are installed.

@gaby commented on GitHub (Apr 24, 2022): @computman007 I think this is a CI issue, I just submitted a PR to take care of this in the future. Ideally every time a new release of `Uptime-Kuma` is created the latest version of `cloudflared` and other dependencies are installed.

deekerman commented

2026-02-28 02:07:39 -05:00

Author

Owner

@k3rnelpan1c-dev commented on GitHub (Apr 25, 2022):

TBH, unless uptime-kume gets released by building on a local dev machine, the docker cache can mostly be ignored 🤔.
In the case of GHA the environment should be clean by default for each run, hence why there are cache actions 😉

Anyway, this still is indeed a CI issue in a way, that it depends on when the last image was built which version will get downloaded (given how this script works).
I don't really have a solid solution for this beyond something similar to what you can do with Renovate-Bot and the RegexMatcher directive, and thereby pinning which version gets installed as well as updating it once there is an update:

github.com/k3rnelpan1c-dev/uptime-kuma-helm@3f1ff2a978/container/Containerfile (L8-L9)

However, that won't save you if there is a release in between uptime-kuma releases.

Allow me question though: given that cloudflared seems to warn you that a version is outdated just cause you are not on the latest (2022.4.0, in the screenshot, is 18 days old and 2022.4.1 is the latest with an age of 13 days), yet it still working fine, is it really that important?

@k3rnelpan1c-dev commented on GitHub (Apr 25, 2022): TBH, unless uptime-kume gets released by building on a local dev machine, the docker cache can mostly be ignored :thinking:. In the case of GHA the environment should be clean by default for each run, hence why there are cache actions :wink: Anyway, this still is indeed a CI issue in a way, that it depends on when the last image was built which version will get downloaded ([given how this script works](https://github.com/louislam/uptime-kuma/blob/master/extra/download-cloudflared.js)). I don't really have a solid solution for this beyond something similar to what you can do with Renovate-Bot and the RegexMatcher directive, and thereby pinning which version gets installed as well as updating it once there is an update: https://github.com/k3rnelpan1c-dev/uptime-kuma-helm/blob/3f1ff2a97889003e00ae6a0df2bdd944c472831c/container/Containerfile#L8-L9 However, that won't save you if there is a release in between uptime-kuma releases. Allow me question though: given that cloudflared seems to warn you that a version is outdated just cause you are not on the latest (2022.4.0, in the screenshot, is 18 days old and 2022.4.1 is the latest with an age of 13 days), yet it still working fine, is it really that important?

deekerman commented

2026-02-28 02:07:39 -05:00

Author

Owner

@computman007 commented on GitHub (Apr 25, 2022):

It's not a big issue as it's working. 18 days are not important if you always keep up to date the client as you said in futur release.

@computman007 commented on GitHub (Apr 25, 2022): It's not a big issue as it's working. 18 days are not important if you always keep up to date the client as you said in futur release.

deekerman referenced this issue

2026-02-28 04:00:36 -05:00

Support for setting "IP Family" accross all monitor types #4381