🐛unable to configure repo for RPM package

[kevingunn-wk]

Describe the bug
Trying to update or repo to use the new GPG key, but the script to configure the repo points to a baseurl that does not resolve.

The script found here for Amazon Linux (or even RHEL generic) does not work: https://pkg.cloudflare.com/index.html#Amazon-Linux

The baseurl is configured as https://pkg-beta.tun.cfdata.org/cloudflared/rpm and does not resolve.

To Reproduce
Steps to reproduce the behavior:

1. Download script from https://pkg.cloudflare.com/index.html#Amazon-Linux as instructed
2. Attempt to install with yum install
3. See error

Expected behavior
It seems the URL in the repo config script may be a beta or test URL and should be updated. Tried using hte "old" baseurl ofhttps://pkg.cloudflare.com/cloudflared/rpm, but this fails with mismatch of GPG keys. At this point, unable to install cloudflared using repo package.

Environment and versions

• OS: Amazon LInux
• Architecture: AMD
• Version: 2

Logs and errors

"https://pkg-beta.tun.cfdata.org/cloudflared/rpm/repodata/repomd.xml: [Errno 14] curl#6 - \"Could not resolve host: pkg-beta.tun.cfdata.org\"\nTrying other mirror.\n\n\n One of the configured repositories failed (cloudflared stable),\n and yum doesn't have enough cached data to continue. At this point the only\n safe thing yum can do is fail. There are a few ways to work \"fix\" this:\n\n     1. Contact the upstream for the repository and get them to fix the problem.\n\n     2. Reconfigure the baseurl/etc. for the repository, to point to a working\n        upstream. This is most often useful if you are using a newer\n        distribution release than is supported by the repository (and the\n        packages for the previous distribution release still work).\n\n     3. Run the command with the repository temporarily disabled\n            yum --disablerepo=cloudflared-stable ...\n\n     4. Disable the repository permanently, so yum won't use it by default. Yum\n        will then just ignore the repository until you permanently enable it\n        again or use --enablerepo for temporary usage:\n\n            yum-config-manager --disable cloudflared-stable\n        or\n            subscription-manager repos --disable=cloudflared-stable\n\n     5. Configure the failing repository to be skipped, if it is unavailable.\n"

Additional context

[rgrthat]

There was a "Public Key Rollover (30 October 2025)"
New key URL: https://pkg.cloudflare.com/cloudflare-public-v2.gpg

[devondragon]

Same issue here. Ran into the key rollover issue when I was running normal update, so went to re-install the repo definition which points to the new key, but fails because the baseurl is configured for an internal only hostname of Cloudflare's which isn't publicly resolvable.

[SteveElliott]

So, combine https://github.com/kevingunn-wk & https://github.com/rgrthat.

Manually update /etc/yum.repos.d/cloudflared.repo to use baseurl=https://pkg.cloudflare.com/cloudflared/rpm

and directly download and install the new key.

"sudo dnf update" then worked for me...

[sectary-want-holly]

The usual amateur hour stuff from CF. For others facing this issue, use this .repo:

[cloudflared-stable]
name=cloudflared-stable
baseurl=https://pkg.cloudflare.com/cloudflared/rpm
enabled=1
type=rpm
gpgcheck=1
gpgkey=https://pkg.cloudflare.com/cloudflare-ascii-pubkey.gpg

[0xpsyduck]

rollover could have been smoother.
at the time of writing this .repo file is working fine.

[cloudflared-stable]
name=cloudflared-stable
baseurl=https://pkg.cloudflare.com/cloudflared/rpm
enabled=1
type=rpm
gpgcheck=1
gpgkey=https://pkg.cloudflare.com/cloudflare-public-v2.gpg