#Cloudflared cannot install
36 messages · Page 1 of 1 (latest)
full error:
W: GPG error: https://pkg.cloudflare.com/cloudflared noble InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 254B391D8CACCBF8 NO_PUBKEY 8A682D308D4E5E73
E: The repository 'https://pkg.cloudflare.com/cloudflared noble InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
Did you install the key as per the instructions?
I followed all of the steps
What is the output of cat /etc/apt/sources.list.d/cloudflared.list?
deb [signed-by=/usr/share/keyrings/cloudflare-main.gpg] https://pkg.cloudflare.com/cloudflared any main
And if you check /usr/share/keyrings/cloudflare-main.gpg, does the file exist?
yes
It's a binary file
yeah i figured
really strange why this won't work.
Should i just manually add the missing key to apt?
sudo apt-get update && sudo apt-get install cloudflared
Hit:1 http://security.ubuntu.com/ubuntu noble-security InRelease
Hit:2 http://archive.ubuntu.com/ubuntu noble InRelease
Hit:3 http://archive.ubuntu.com/ubuntu noble-updates InRelease
Hit:4 https://packages.wazuh.com/4.x/apt stable InRelease
Hit:5 https://deb.nodesource.com/node_22.x nodistro InRelease
Hit:6 http://archive.ubuntu.com/ubuntu noble-backports InRelease
Get:7 https://pkg.cloudflare.com/cloudflared any InRelease [5039 B]
Get:8 https://packages.doppler.com/public/cli/deb/debian any-version InRelease [11.9 kB]
Err:7 https://pkg.cloudflare.com/cloudflared any InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 254B391D8CACCBF8 NO_PUBKEY 8A682D308D4E5E73
Reading package lists... Done
W: GPG error: https://pkg.cloudflare.com/cloudflared any InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 254B391D8CACCBF8 NO_PUBKEY 8A682D308D4E5E73
E: The repository 'https://pkg.cloudflare.com/cloudflared any InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.```
Are both files owned by root with the correct permissions?
gpg --show-keys /usr/share/keyrings/cloudflare-main.gpg What does that say?
My only idea is that the file permissions of the key aren't set correctly
pub rsa4096 2025-10-23 [SC]
CC94B39C77AE7342A68B89628A682D308D4E5E73
uid CloudFlare Software Packaging 2025 help@cloudflare.com
sub rsa4096 2025-10-23 [E]
i will check permissios now
my permission for the .gpg file is 640. Is that okay?
erm, i have no idea if other read is needed. But all the files in that folder have 644 for me, so I'd try that
okay i will try.
well setting it to 644 worked.
thank you so much
holy that took longer than expected
thanks man!!!!
You might want to check if they keyrings folder has the correct permissions so you don't run into the same problem again later
i will!
Btw laudian, sorry to ask.
I wanted to ask for some security advice.
My bot listens to telegram requests at port 3000. i setup an endpoint to localhost:3000.
I setup WAF to only allow post requests, only allowed IPs of telegram. Is this safe enough? Am i missing something?
Furthermore, it connects to http://localhost:3000.
Does cloudflare automatically forward it to https?
If you enable the automatic https redirect on cloudflare, yes
awesome! Is there any other thing i should enable for more security?
If Telegram doesn't offer any further authentication, limiting access to their IPs seems like a good place to start.