Knowledgebase

Failed to retrieve repodata/repomd.xml from cloudlinux-x86_64-server-* error was [Errno 14] HTTPS Error 404 - Not Found

The error message you're encountering, "Failed to retrieve repodata/repomd.xml from cloudlinux-x86_64-server-* error was [Errno 14] HTTPS Error 404 - Not Found," indicates that yum or dnf is unable to locate the repository metadata (repomd.xml file) for the CloudLinux repository you're trying to access.

Here are steps to troubleshoot and potentially resolve the issue:

  1. Verify Repository Configuration:

    • Ensure that the repository configurations  /etc/yum.repos.d/ for CloudLinux are correctly set up. Check for any typos or mistakes in the configuration files.
  2. Update Repository Metadata:

    • Run the following commands to clean and regenerate the repository metadata:
      bash

 

    • sudo yum clean all sudo yum makecache
  • Verify Repository URLs:

    • Confirm that the repository URLs in your configuration files are correct and accessible from your network. Verify that there are no typos or mistakes in the URLs.
  • Temporary Disable Repository:

    • If the error persists with a specific repository, you may temporarily disable it by setting enabled=0 in the repository configuration file.
  • Check for Proxy Settings:

    • If your server is behind a proxy, make sure that the proxy settings are correctly configured. You might need to set up proxy settings in /etc/yum.conf or in the specific repository configuration file.
  • Check Firewall Rules:

    • Verify that your server's firewall is not blocking outgoing connections to the CloudLinux repositories. Allow traffic on the relevant ports (usually 80 and 443).
  • Temporary DNS Issues:

    • It's possible that there might be temporary DNS resolution issues. Try using a different DNS server or check if your current DNS server is functioning properly.
  • Check SELinux:

    • If you have SELinux enabled, it might be preventing the server from accessing certain directories or files. You can temporarily set SELinux to permissive mode:
      bash

 

    • sudo setenforce 0
      If this resolves the issue, you may need to adjust SELinux policies or file permissions.
  1. Verify System Date and Time:

    • Make sure that the date and time settings on your server are correct. Incorrect date/time settings can cause issues with SSL certificates during repository access.
  2. Check Logs:

    • Review the logs located in /var/log/yum.log for any specific error messages related to the 404 error.
  3. Contact CloudLinux Support:

    • If none of the above steps resolve the issue, it's possible that there may be an issue with the CloudLinux repository server itself. In this case, contact CloudLinux support for further assistance.

Remember to carefully review any output or prompts provided by the package manager during the installation process, as it may contain important information about potential conflicts or issues. Always back up critical data before making significant changes to your system.

 
  • 0 Users Found This Useful
Was this answer helpful?