Import the new GPG key to upgrade to ePortal 2.18

Issue

KernelCare  ePortal 2.18 (scheduled for release on by 23 of May 2025) will be signed with a new GPG key.

Systems that still rely on the old key will display signature‑verification warnings during apt update and will refuse to refresh the ePortal repository metadata until the new key is installed.

If the key is missing, apt update will show errors similar to:

W: GPG error: https://repo.cloudlinux.com/kcare-eportal/debian/12 kcare InRelease: \    NO_PUBKEY 6DC3D600CDEF74BB W: Some index files failed to download. They have been ignored, or old ones used instead.

All other repositories will continue to update normally, so production is not interrupted. You will, however, stop receiving ePortal updates until the key is imported.

Environment

• ePortal

Who is affected

1. ePortal version less than 2.8.
2. Debian 11/12 (“Bullseye/Bookworm”) or Ubuntu 20.04/22.04.
3. server pulls packages from https://repo.cloudlinux.com/kcare-eportal.

If your ePortal is 2.8 or newer, no immediate action is required — though importing the key now is still safe and recommended.

Solution

Run the following one‑liner as root (or with sudo) on every ePortal server:

curl https://repo.cloudlinux.com/kernelcare/kernelcare.gpg -o /usr/share/keyrings/kcare-eportal.gpg