Quantcast
Channel: FedoraForum.org
Viewing all articles
Browse latest Browse all 36127

[SOLVED] Error: Cannot find a valid baseurl for repo: rpmfusion-free/18/x86_64

$
0
0
Hello. I installed Fedora 18 yesterday, and I'm currently having a problem with rpmfusion.


Quote:

Loaded plugins: langpacks, presto, refresh-packagekit
Could not retrieve mirrorlist http//mirrors.rpmfusion.org/mirrorlist?repo=free-fedora-18&arch=x86_64 error was
12: Timeout on http//mirrors.rpmfusion.org/mirrorlist?repo=free-fedora-18&arch=x86_64: (28, '')
Error: Cannot find a valid baseurl for repo: rpmfusion-free/18/x86_64

I had a similar issue with the fedora repos immediately after installing, and that turned out to be a proxy problem (I was setting the HTTP_PROXY, but required HTTPS_PROXY as well). The .repo files have the mirrorlist and baseurl using http protocol, so I don't see why it shouldn't work.

There are a number of threads about this all pointing to a DNS problem. My DNS settings are good, but I have tried switching to OpenDNS and that does not fix the problem.

Other suggested solutions involve setting the "method" in "IPv4 settings" to "Automatic (DCHP) Addresses Only". Mine is set to, and needs to be set to, Manual. If I check the "Require IPv4 addressing for this connection to complete" the network does not connect.


If I paste the mirror list url into firefox it loads the mirror list as one would expect. If I use wget, it resolves the hostname to a list of 3 IP's, all of which time out:

Quote:

# wget http//mirrors.rpmfusion.org/mirrorlist
--2013-03-03 11:16:40-- http//mirrors.rpmfusion.org/mirrorlist
Resolving mirrors.rpmfusion.org (mirrors.rpmfusion.org)... 85.214.67.247, 88.198.59.188, 134.108.44.54
Connecting to mirrors.rpmfusion.org (mirrors.rpmfusion.org)|85.214.67.247|:80... failed: Connection timed out.
Connecting to mirrors.rpmfusion.org (mirrors.rpmfusion.org)|88.198.59.188|:80... failed: Connection timed out.
Connecting to mirrors.rpmfusion.org (mirrors.rpmfusion.org)|134.108.44.54|:80... failed: Connection timed out.

It looks suspiciously like the proxy problem I was having yesterday, but the proxy settings are (or at least appears to be, and should be) correct. I can ping both the IP and the hostname.





I am really beating my head against my desk at this stage, so any help would be greatly appreciated!




nb: the colon in "http//" is missing due to the url posting restriction.

Viewing all articles
Browse latest Browse all 36127

Trending Articles