[Solved] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again

Cannot retrieve metalink for repository: epel/x86_ 64. Please verify its path and try again

Loaded plugins: fastestmirror

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

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

Today, when using Yum to install the software, I encountered an error. I was prompted to find that there was a problem with the EPEL source. However, after comparing with the EPEL source of the host that can be installed, I found that there was no difference, so the problem was definitely not in the EPEL source configuration file, so I need to analyze the differences in the environment. This virtual machine is a pure intranet server, Using Yum to install is through the use of the tinyproxy proxy of the public network virtual machine, and using the curl command to test the connection to the website has no problem, that is, the current proxy is still in effect, and the EPEL source is installed using the yum command, so there is no problem with yum. The solution and configuration are written as follows:

export http_proxy=
export https_proxy=

The reason for the error is that when I use the tinyproxy proxy, I configure the HTTP global proxy locally, but I did not add the proxy of the HTTPS protocol, so the above error is reported. After adding the proxy of the HTTPS protocol, yum can be installed normally

Similar Posts: