Skip to main content

YUM encountered errors outside of EasyApache 4

Rawand Bradosty
Hi, Today I tried to install PHP 8.1 on my dedicated server, OS: CentOS v7.9.2009 STANDARD standard, cPanel Version: 110.0.9 on WHM when I access EasyApache 4 page I get this error ( YUM encountered errors outside of EasyApache 4. Log into the system via SSH to resolve them, or you can click the "Refresh" button to rebuild the system"s cache. ) I run these commands as suggested on another thread yum clean all yum update it showed this error [root@yaserver ~]# yum clean all Loaded plugins: fastestmirror, universal-hooks Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base extras : home_Jperkster_EA4_Mod_Cloudflare imunify360 : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3 : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6 : imunify360-rollout-7 imunify360-rollout-8 : mysql-connectors-community mysql-tools-community : mysql57-community updates Cleaning up list of fastest mirrors Other repos take up 992 M of disk space (use --verbose for details) [root@yaserver ~]# yum update Loaded plugins: fastestmirror, universal-hooks Determining fastest mirrors * EA4: 208.74.123.62 * cpanel-addons-production-feed: 208.74.123.62 * cpanel-plugins: 208.74.123.62 * base: centos-distro.cavecreek.net * extras: mirror.vacares.com * updates: centos.mirror.ndchost.com EA4 | 2.9 kB 00:00:00 cpanel-addons-production-feed | 2.9 kB 00:00:00 cpanel-plugins | 2.9 kB 00:00:00 base | 3.6 kB 00:00:00 extras | 2.9 kB 00:00:00 If above article doesn't help to resolve this issue please use

Comments

4 comments

Date Votes
  • ffeingol
    It looks like it's trying to pull in mod_cloudflare, which has been deprecated GitHub - cloudflare/mod_cloudflare
    0
  • kodeslogic
    The error message you provided indicates that there's a problem with the home_Jperkster_EA4_Mod_Cloudflare repository. It seems that this repository is either not accessible or no longer exists at the specified URL. Here's what you can do to address this issue: 1. Disable or Remove Problematic Repository: Since the home_Jperkster_EA4_Mod_Cloudflare repository is causing the error, you should disable or remove it from your YUM repository configuration. Navigate to the /etc/yum.repos.d/ directory and look for a file related to this repository. You can either delete the file or rename it by adding an extension like .bak to the filename. 2. Clean YUM Cache: As mentioned earlier, cleaning the YUM cache might help resolve issues related to outdated or corrupted metadata. Run the following command to clean the YUM cache: #yum clean all
    3. Update Your System: After performing the above steps, try running the update command again: #yum update
    By disabling or removing the problematic repository, you're preventing YUM from attempting to access it and encountering errors. Make sure to verify your other repository configurations to ensure they are correctly set up and pointing to valid URLs. If you're still facing issues after trying these steps, consider checking your entire repository configuration to ensure there are no other repositories causing conflicts or errors. If you're not comfortable with making these changes or if the issue persists, it might be a good idea to seek assistance from someone with experience in
    0
  • Rawand Bradosty
    The error message you provided indicates that there's a problem with the home_Jperkster_EA4_Mod_Cloudflare repository. It seems that this repository is either not accessible or no longer exists at the specified URL. Here's what you can do to address this issue: 1. Disable or Remove Problematic Repository: Since the home_Jperkster_EA4_Mod_Cloudflare repository is causing the error, you should disable or remove it from your YUM repository configuration. Navigate to the /etc/yum.repos.d/ directory and look for a file related to this repository. You can either delete the file or rename it by adding an extension like .bak to the filename. 2. Clean YUM Cache: As mentioned earlier, cleaning the YUM cache might help resolve issues related to outdated or corrupted metadata. Run the following command to clean the YUM cache: #yum clean all
    3. Update Your System: After performing the above steps, try running the update command again: #yum update
    By disabling or removing the problematic repository, you're preventing YUM from attempting to access it and encountering errors. Make sure to verify your other repository configurations to ensure they are correctly set up and pointing to valid URLs. If you're still facing issues after trying these steps, consider checking your entire repository configuration to ensure there are no other repositories causing conflicts or errors. If you're not comfortable with making these changes or if the issue persists, it might be a good idea to seek assistance from someone with experience in
    0
  • kodeslogic
    I am glad I was able to help.
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post