# Red Hat Certificate Upload Issues Last Updated On: 31 Oct 2026 7 minutes read ## Problem Diagnostic output can also show **RHEL CERTIFICATE TYPE: Valid RedHat certificate not available**. Review the certificate and subscription validation results and connectivity to the required Red Hat repositories. The patch scan or deployment failed with the message **"Linux package manager metadata files are not available because the Red Hat certificates are invalid"** ## Cause For a metadata download error without a Red Hat certificate error, follow [Linux metadata download checks](https://www.manageengine.com/products/desktop-central/kb/patch-management/troubleshooting-package-manager-files-download-failure.html). Generic metadata wording alone does not establish a certificate failure. This label does not identify every scan failure. If the logs also report a missing `patch-settings.json` file or an error while posting scan-failure status, investigate those stages separately. See [scan-data generation troubleshooting](https://www.manageengine.com/products/desktop-central/kb/patch-management/problem-in-generating-patch-scan-data.html). A vendor-connectivity warning still requires checking the failed request. - No active subscription on the agent-installed system. - Valid certificate with access to `cdn.redhat.com` is missing in the selected system. ## Resolution 1. Open Threats & Patches → Settings → Redhat Linux Settings and check for the errors below. - Error while uploading certificate from Agent to Server: - Certificate upload process from the chosen system is in-progress. - Certificate upload process from a previously nominated system is in-progress. - Certificate upload process from a previously nominated system has failed; a valid certificate will be uploaded from other agents. - Certificate upload from the chosen system has failed; a valid certificate will be uploaded from other agents. - Uploaded certificate is invalid: - Red Hat subscription validation process has failed due to timeout. - Red Hat patching for this edition will fail due to the certificate being expired; a valid certificate will be uploaded from other agents. - Uploaded certificate is about to expire; renew subscription. - Error remarks shown while choosing the alternate system: - The chosen system has an invalid Red Hat subscription; kindly choose an alternate system. - The chosen system has an RHUI subscription, which is not supported; kindly choose an alternate system. - The chosen system has configured a private mirror, which is not supported; kindly choose an alternate system. - The chosen system has a Red Hat Satellite subscription, which is not supported; kindly choose an alternate system. 2. If the remark states that the certificate upload retry limit has been exceeded after a 403 response from the CDN server, open the affected edition's **Actions** menu, choose an alternate system, and upload the certificate from that system. 3. If one of these errors occurs, follow the resolution steps below. - To receive updates from the Red Hat portal, you need to have an active subscription. - Refer [here](https://www.redhat.com/en/store) for purchasing a redhat subscription. - Refer [here](https://docs.redhat.com/en/documentation/subscription_central/1-latest/html/getting_started_with_rhel_system_registration/adv-reg-rhel-using-rhsm_#available_subs_ref) for managing your subscriptions. - Verify your purchased subscription. - Check the subscription status of the system by running the command: sudo subscription-manager status in the Linux terminal. - If you have Simple Content Access(SCA) enabled in your redhat account, then systems simply need to be registered (via subscription-manager) to get access to the repositories. Ensure that either of the following status is displayed. 1. When SCA is enabled ```plaintext subscription-manager status +-------------------------------------------+ System Status Details +-------------------------------------------+ Overall Status: Disabled Content Access Mode is set to Simple Content Access. This host has access to content, regardless of subscription status. System Purpose Status: Disabled ``` 2. When SCA is disabled ```plaintext subscription-manager status +-------------------------------------------+ System Status Details +-------------------------------------------+ Overall Status: Current System Purpose Status: Matched ``` - If the Red Hat Subscription status is 'Unknown', then it could be because your machine was registered when it was offline. If that's the case, refer to the steps [here](https://access.redhat.com/solutions/7065718?utm_source=pmp). - If the Red Hat Subscription Status is 'Insufficient', then it could be because you have subscribed a VM machine which was migrated. In that case, refer to the steps [here](https://access.redhat.com/solutions/3328401). - If you still face a problem or the subscription status was neither of the above two cases, then try to reattach the subscription or try executing the command "subscription-manager refresh", which updates your system with the latest subscription information from Red Hat. Then verify that the entitlement certificates are present in /etc/pki/entitlement/ directory. - If the purchased subscription is expired, renew your subscription. Refer [here](https://www.redhat.com/en/about/subscription-renewal-guide?utm_source=pmp) for the renewal steps. - Verify if valid Red Hat repository is configured in your systems, - Check if it meets the required criteria, as mentioned [here](https://www.manageengine.com/products/desktop-central/help/patch_management/kb/invalid-redhat-repo-found-in-agent-machine-1.html#criteria). - If the valid .repo file is missing, ensure /etc/rhsm/rhsm.conf has manage_repos set to "1". ## Further Assistance If you encounter any error messages other than the ones mentioned, or if the issue persists after following the resolution steps, kindly contact [patchmanagerplus-support@manageengine.com](mailto:patchmanagerplus-support@manageengine.com). ## Related - [Red Hat Linux patch management](https://www.manageengine.com/products/desktop-central/help/patch-management/patch-management-red-hat-linux.html)