Hi All,

The subject pretty much says it all, but here is a bit more description:

I am running mandrivia 10.1, a pretty fresh install. I have curl and libcurl 7.12.1, the server is behind a router, but that has never interfered before. Curl was working fine on my last install, but has now stopped working.

All I get is "curl (7) couldn't connect" no matter what I try to do with it...

Any ideas? Let me know if you need more info...

Thanks!

can you ping the site?

Hi, thanks for your reply.

I can ping all the sites I have tried (google.com, yahoo.com, localhost, etc) via terminal, if that is what you mean. Doesn't seem to matter what the site is. I can't even curl my own box via localhost or my own ip or network name, all of which load fine in a browser.

I did install and then uninstall a newer version of curl via source - could it have messed up one of my env-vars maybe? I don't know what curl needs to be able to run...

curl shouldn't implicitly need anything really, it's just a simple web client. try adding extra -v's to the command line, see where it gets step by step. only thing that i've seen affect it's abilities is when it tries to hit an ssl site without the right libraries, but if you're just using straight http that's irrelevant. if you can show us the WHOLE curl output, including your command line with those -v's and we'll see.

I hadn't realized I could make it verbose... Being a newbie sucks, I hope it's over soon.

I am getting back:

[root@lini root]# curl -v -v -v http://www.linuxquestions.org
* About to connect() to 192.168.0.1 port 1080
* Trying 192.168.0.1... * Connection refused
* Closing connection #0
curl: (7) couldn't connect

This means it is trying to get out the router and can't, which makes sense. It is returning the error instantaneously, not like it is waiting for a site or anything, so the problem has to be close to home...

hmm, ok. so i would think that you have some bizarre proxy issue if you can ping ok. does your http_proxy variable contain 192.168.0.1:1080 ? (run 'echo $http_proxy') i assume curl does work if you use the ip address directly? e.g. "curl 1.2.3.4:80"

I tried curling some of the sites in question, and the router, by ip, but none of them worked - same result as by domain.

The http_proxy is 192.168.0.1 with no port.

Do I need the http proxy for everything to work? I Could conceivably take it out. It seems odd that browsers, email, etc all work, and only curl is fried...

yes that is odd... essemtially if you don't *need* a proxy, don't use a proxy. thing is that the errors aren't that consistent with a proxy, as they will normally say they are connecting to a proxy. I think. If you temporarily just put http_proxy="" infront of the curl, it'll bypass the proxy and go direct.

Hey, you are right, that makes it work.

Weird, but whatever works. I guess it set the proxy up when I did the network setup stuff. If everything will work without it, I will just take it back out.

Thank you - I am really grateful. Such a dumb little thing when you know what you are doing, but it was driving me crazy.

Have a good night!

Ok, just one more dumb question...

Any idea how I change the http_proxy....

well it's more about wondering what made it be that way in the first place. generally this would be a "network proxy" widgetty configuration tool in a menu somewhere. i do not know where this actually get's held, i assume that it's held at desktop level (i assume if you quit X and do it it works just fine?)

That makes is even weirder then.

You are right, if I exit X (rather, select failsafe from the graphical boot menu, I don't seem to be able to get out of X entirely, CTRL+ALT+BACKSPACE only takes me back to the X login), curl works just fine from the command line.

The problem that kicked off the whole thing, though, is that I am using curl via php (both by the curl functions and by passing it to command via exec() show the same result), and the error is coming back as 7 all the time. It should be running under apache or nobody, I imagine. Could the fact that I am running X and logged in as root or a user affect that?

The problem persists in php even when I log in with failsafe and get curl working ok for my own user.

I've managed to fix the php issue (if I want to use exec at least) by doing this:

I think I will attack my configuration tools and see if I can figure out where that proxy setting is coming from...