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>
or
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
compromise:
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 今天在使用yum安裝軟體時遇到了如上報錯，提示資訊發現提示我epel源有問題，但是經過和可以安裝的主機epel源的對比，發現並沒有差別，所以問題肯定不在epel源配置檔案上，所以就需要分析環境上的差異了，這臺雲主機是一臺純內網伺服器，使用yum安裝是通過使用了公網雲主機的tinyproxy代理，而且使用curl命令測試連線網站沒問題，也就是當前代理還在生效中，epel源就是使用yum命令安裝的，所以yum也沒問題，解決辦法以及配置寫到下面：
vim /etc/profile
export http_proxy=http://192.168.1.1:2525
export https_proxy=https://192.168.1.1:2525報錯的原因是我在使用tinyproxy代理時，本地配置http全域性代理，但是沒新增https協議的代理，所以出現了以上的報錯，新增https協議代理後，yum可以正常安裝。