Any help around the Fedora 16 i686 yum error behind a proxy please. I have set up the proxy details correctly on the yum.conf file but it fails to resolve the proxy host-name. I put in the IP, and it still brings the same error. I also did a host <host-name> on the command and the results are good with the actual IP. If i take out the proxy setting from the conf file it complains with authentication meaning its definitely using those setting I have added. Is there a bug with the new distro? Did a fresh install of fedora 11 on another box and it worked like a charm.

If you do not provide /etc/yum/conf contents and only say it's correct then we can not check it and only take your word for it...


If you comment out the proxy settings and are still confronted with auth warnings then you might be behind a type of proxy Yum doesn't know how to deal with?


If so then it should be listed at bugzilla.redhat.com.


If nothing else works then you could copy one machines complete /etc/ tree to the other machines /tmp directory and then recursively diff both etc/ dirs for clues.

cat /etc/yum.conf
[main]
cachedir=/var/cache/yum/$basearch/$releasever
keepcache=0
debuglevel=2
logfile=/var/log/yum.log
exactarch=1
obsoletes=1
gpgcheck=1
plugins=1
installonly_limit=3
# The proxy server - proxy serverort number
proxy=http://proxyserverhostname:8080
# The account details for yum connections
proxy_username=myusername
proxy_password=andmypassword
#when you uncomment this line below, you exclude these packages from updates
#exclude=php* kernel*

# This is the default, if you make this bigger yum won't see if the metadata
# is newer on the remote and so you'll "gain" the bandwidth of not having to
# download the new metadata and "pay" for it by yum not having correct
# information.
# It is esp. important, to have correct metadata, for distributions like
# Fedora which don't keep old packages around. If you don't like this checking
# interupting your command line usage, it's much better to have something
# manually check the metadata once an hour (yum-updatesd will do this).
# metadata_expire=90m

# PUT YOUR REPOS HERE OR IN separate files named file.repo
# in /etc/yum.repos.d



My guess is yum cannot figure out the type of proxy im behind is false because yum indicates been authorised or not by the proxy. The big question is yum cannot resolve the proxy host even if you supply the actual IP and curl complains instead as below

http://linuxdownload.adobe.com/linux...ta/repomd.xml: [Errno 14] curl#5 - "Couldn't resolve proxy"
Trying other mirror.
Could not retrieve mirrorlist http://mirrors.rpmfusion.org/mirrorl...a-16&arch=i386 error was
14: curl#5 - "Couldn't resolve proxy"
Could not retrieve mirrorlist http://mirrors.rpmfusion.org/mirrorl...d-16&arch=i386 error was
14: curl#5 - "Couldn't resolve proxy"
Could not retrieve mirrorlist http://mirrors.rpmfusion.org/mirrorl...a-16&arch=i386 error was
14: curl#5 - "Couldn't resolve proxy"
Could not retrieve mirrorlist http://mirrors.rpmfusion.org/mirrorl...d-16&arch=i386 error was
14: curl#5 - "Couldn't resolve proxy"
http://linuxdownload.adobe.com/linux...ta/repomd.xml: [Errno 14] curl#5 - "Couldn't resolve proxy"
Trying other mirror.

Has anyone been able to resolve this one.I am facing the same issue?

I experienced same trouble, cause the presence of special character @ in my proxy password.

I changed @ in %40 in /etc/yum.conf and so i solved it.

NOTE: After the upgrade this fix in NOT more necessary so you have to change your /etc/yum.conf and can use @ in proxy_password field