# Troubleshoot a Redhat Certificate upload error

## Problems

The patch scan or deployment failed with the message: Linux package manager files are not available because the Red Hat certificates are invalid. Please navigate to the Red Hat Linux settings page to check for the error message.

Here are the potential errors that may occur during the patching process:

**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.

## Causes

- No active subscription on the agent-installed system.
- Valid certificate pointing to cdn.redhat.com is missing in the agent-installed systems.

## Resolution

You can resolve the issues as follows:

1. If you are a beginner to Red Hat Enterprise patching, start by purchasing a Red Hat subscription.  
   A Red Hat subscription gives you access to enterprise-ready software, updates, and information and support services that span your entire application infrastructure, life cycle, and architecture.

2. To receive updates from the Red Hat portal, you need to have an active subscription. Ensure the Red Hat account provided has a subscription that is currently active to receive updates.

3. Verify if the purchased subscription has recently expired. If yes, renew your subscription. [Refer here for the renewal steps.](https://www.redhat.com/en/about/subscription-renewal-guide?utm_source=pmp)

4. Check the subscription status of the system by running the code: **_"sudo subscription-manager status"_** in the Linux terminal.

   - 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/2158251?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 2 cases, then try to detach/remove the subscription from the system. Then, again attach the subscription to the system. [Refer to the steps here.](https://access.redhat.com/solutions/776723?utm_source=pmp)

5. Verify **redhat.repo** File:

   - Check whether the **redhat.repo** file is available in **/etc/yum.repos.d**.
   - If the redhat.repo file is missing, ensure **/etc/rhsm/rhsm.conf** has **manage_repos** set to "1".

Kindly contact [support](mailto:patchmanagerplus-support@manageengine.com) for any queries.