Repository error: Cannot retrieve metalink for repository: epel

Refers to:

  • Plesk 12.5 for Linux
  • Plesk 11.0 for Linux
  • Plesk 12.0 for Linux

Created:

2016-11-16 12:51:05 UTC

Modified:

2016-12-21 19:22:26 UTC

0

Was this article helpful?


Have more questions?

Submit a request

Repository error: Cannot retrieve metalink for repository: epel

Note : applicable for RedHat-based operating systems only.

Symptoms

  • ModSecurity rule set update failed with error below:

    Error: Failed to update the ModSecurity rule set: modsecurity_ctl failed: gpg: key 4520AFA9: "Atomicorp (Atomicorp Official Signing Key) <support@atomicorp.com>" not changed gpg: Total number processed: 1 gpg: unchanged: 1 gpg: Signature made Tue Sep 9 20:45:23 2014 CEST using RSA key ID 4520AFA9 gpg: Good signature from "Atomicorp (Atomicorp Official Signing Key) <support@atomicorp.com>" gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: 1818 66DF 9DAC A40E 5B42 9B08 FFBD 5D0A 4520 AFA9 TERM environment variable not set. Error: Cannot retrieve metalink for repository: epel. Please verify its path and try again Command '/bin/bash < /tmp/tmpsGmerE/aum-plesk-installer' returned non-zero exit status 1 Unable to download tortix rule set
  • Plesk upgrade fails with the following error:

    RepoError: Cannot retrieve metalink for repository: epel. Please verify its path and try again

Cause

" epel " repository can not be verified.

Resolution

  1. Upgrade ca-certificates package.

    # yum upgrade ca-certificates
  2. If it is still not possible to update ModSecurity, disable epel repository:

    # grep enabled /etc/yum.repos.d/epel.repo
    enabled=0
  3. Update ModSecurity rule set manually with atomic update manager (aum):

    # aum -u
Have more questions? Submit a request
Please sign in to leave a comment.