curl tries to connect to 127.0.0.1:9050 by default
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
whenever I use curl it tries to connect to tor service by default. my tor service is turned off and network proxy is disabled in network settings.
here is the output of the command curl google.com
:
curl: (7) Failed to connect to 127.0.0.1 port 9050: Connection refused
I didn't change any configuration of curl to use Tor.
my OS is ubuntu 17.10
How can I fix it?
curl
add a comment |Â
up vote
0
down vote
favorite
whenever I use curl it tries to connect to tor service by default. my tor service is turned off and network proxy is disabled in network settings.
here is the output of the command curl google.com
:
curl: (7) Failed to connect to 127.0.0.1 port 9050: Connection refused
I didn't change any configuration of curl to use Tor.
my OS is ubuntu 17.10
How can I fix it?
curl
1
Try using "curl --noproxy * google.com" This will disable the use of a proxy server for all addresses.
â Raman Sailopal
Jan 5 at 10:59
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
whenever I use curl it tries to connect to tor service by default. my tor service is turned off and network proxy is disabled in network settings.
here is the output of the command curl google.com
:
curl: (7) Failed to connect to 127.0.0.1 port 9050: Connection refused
I didn't change any configuration of curl to use Tor.
my OS is ubuntu 17.10
How can I fix it?
curl
whenever I use curl it tries to connect to tor service by default. my tor service is turned off and network proxy is disabled in network settings.
here is the output of the command curl google.com
:
curl: (7) Failed to connect to 127.0.0.1 port 9050: Connection refused
I didn't change any configuration of curl to use Tor.
my OS is ubuntu 17.10
How can I fix it?
curl
edited Jan 5 at 11:02
asked Jan 5 at 10:32
Yashar
1013
1013
1
Try using "curl --noproxy * google.com" This will disable the use of a proxy server for all addresses.
â Raman Sailopal
Jan 5 at 10:59
add a comment |Â
1
Try using "curl --noproxy * google.com" This will disable the use of a proxy server for all addresses.
â Raman Sailopal
Jan 5 at 10:59
1
1
Try using "curl --noproxy * google.com" This will disable the use of a proxy server for all addresses.
â Raman Sailopal
Jan 5 at 10:59
Try using "curl --noproxy * google.com" This will disable the use of a proxy server for all addresses.
â Raman Sailopal
Jan 5 at 10:59
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
3
down vote
Check your environment variables with some command as env
at the command interface line. Perhaps some variable as http_proxy or HTTPS_PROXY is set.
Another way to bypass the setting of these environment variables is to launch curl --noproxy '*' google.com
to see if the unwanted behaviour still happens.
The curl
command has also a configuration file where some options can be set (See ~/.curlrc
in the cse of default settings).
I don't have such environment variables.--noproxy
flag also returnscurl: no URL specified!
. I don't have any~/.curlrc
nor configuration under /etc
â Yashar
Jan 5 at 10:54
The--noproxy
flag must be followed by a wildcard, v.gr.*
, otherwise www.google.com will be considered as the argument of--noproxy
andcurl
will return 'no URL specified!'. I eddited my answer above. See the correct way to launchcurl
and escape the*
.
â Pierre François
Jan 5 at 11:00
that solved my problem thanks! but is there any way to use curl without this flag? there are lots of scripts which use curl and its hard to change them to use this flag
â Yashar
Jan 5 at 11:05
You can define these settings in the~/.curlrc
configuration file.
â Pierre François
Jan 5 at 11:28
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
Check your environment variables with some command as env
at the command interface line. Perhaps some variable as http_proxy or HTTPS_PROXY is set.
Another way to bypass the setting of these environment variables is to launch curl --noproxy '*' google.com
to see if the unwanted behaviour still happens.
The curl
command has also a configuration file where some options can be set (See ~/.curlrc
in the cse of default settings).
I don't have such environment variables.--noproxy
flag also returnscurl: no URL specified!
. I don't have any~/.curlrc
nor configuration under /etc
â Yashar
Jan 5 at 10:54
The--noproxy
flag must be followed by a wildcard, v.gr.*
, otherwise www.google.com will be considered as the argument of--noproxy
andcurl
will return 'no URL specified!'. I eddited my answer above. See the correct way to launchcurl
and escape the*
.
â Pierre François
Jan 5 at 11:00
that solved my problem thanks! but is there any way to use curl without this flag? there are lots of scripts which use curl and its hard to change them to use this flag
â Yashar
Jan 5 at 11:05
You can define these settings in the~/.curlrc
configuration file.
â Pierre François
Jan 5 at 11:28
add a comment |Â
up vote
3
down vote
Check your environment variables with some command as env
at the command interface line. Perhaps some variable as http_proxy or HTTPS_PROXY is set.
Another way to bypass the setting of these environment variables is to launch curl --noproxy '*' google.com
to see if the unwanted behaviour still happens.
The curl
command has also a configuration file where some options can be set (See ~/.curlrc
in the cse of default settings).
I don't have such environment variables.--noproxy
flag also returnscurl: no URL specified!
. I don't have any~/.curlrc
nor configuration under /etc
â Yashar
Jan 5 at 10:54
The--noproxy
flag must be followed by a wildcard, v.gr.*
, otherwise www.google.com will be considered as the argument of--noproxy
andcurl
will return 'no URL specified!'. I eddited my answer above. See the correct way to launchcurl
and escape the*
.
â Pierre François
Jan 5 at 11:00
that solved my problem thanks! but is there any way to use curl without this flag? there are lots of scripts which use curl and its hard to change them to use this flag
â Yashar
Jan 5 at 11:05
You can define these settings in the~/.curlrc
configuration file.
â Pierre François
Jan 5 at 11:28
add a comment |Â
up vote
3
down vote
up vote
3
down vote
Check your environment variables with some command as env
at the command interface line. Perhaps some variable as http_proxy or HTTPS_PROXY is set.
Another way to bypass the setting of these environment variables is to launch curl --noproxy '*' google.com
to see if the unwanted behaviour still happens.
The curl
command has also a configuration file where some options can be set (See ~/.curlrc
in the cse of default settings).
Check your environment variables with some command as env
at the command interface line. Perhaps some variable as http_proxy or HTTPS_PROXY is set.
Another way to bypass the setting of these environment variables is to launch curl --noproxy '*' google.com
to see if the unwanted behaviour still happens.
The curl
command has also a configuration file where some options can be set (See ~/.curlrc
in the cse of default settings).
edited Jan 5 at 11:02
answered Jan 5 at 10:48
Pierre François
1333
1333
I don't have such environment variables.--noproxy
flag also returnscurl: no URL specified!
. I don't have any~/.curlrc
nor configuration under /etc
â Yashar
Jan 5 at 10:54
The--noproxy
flag must be followed by a wildcard, v.gr.*
, otherwise www.google.com will be considered as the argument of--noproxy
andcurl
will return 'no URL specified!'. I eddited my answer above. See the correct way to launchcurl
and escape the*
.
â Pierre François
Jan 5 at 11:00
that solved my problem thanks! but is there any way to use curl without this flag? there are lots of scripts which use curl and its hard to change them to use this flag
â Yashar
Jan 5 at 11:05
You can define these settings in the~/.curlrc
configuration file.
â Pierre François
Jan 5 at 11:28
add a comment |Â
I don't have such environment variables.--noproxy
flag also returnscurl: no URL specified!
. I don't have any~/.curlrc
nor configuration under /etc
â Yashar
Jan 5 at 10:54
The--noproxy
flag must be followed by a wildcard, v.gr.*
, otherwise www.google.com will be considered as the argument of--noproxy
andcurl
will return 'no URL specified!'. I eddited my answer above. See the correct way to launchcurl
and escape the*
.
â Pierre François
Jan 5 at 11:00
that solved my problem thanks! but is there any way to use curl without this flag? there are lots of scripts which use curl and its hard to change them to use this flag
â Yashar
Jan 5 at 11:05
You can define these settings in the~/.curlrc
configuration file.
â Pierre François
Jan 5 at 11:28
I don't have such environment variables.
--noproxy
flag also returns curl: no URL specified!
. I don't have any ~/.curlrc
nor configuration under /etcâ Yashar
Jan 5 at 10:54
I don't have such environment variables.
--noproxy
flag also returns curl: no URL specified!
. I don't have any ~/.curlrc
nor configuration under /etcâ Yashar
Jan 5 at 10:54
The
--noproxy
flag must be followed by a wildcard, v.gr. *
, otherwise www.google.com will be considered as the argument of --noproxy
and curl
will return 'no URL specified!'. I eddited my answer above. See the correct way to launch curl
and escape the *
.â Pierre François
Jan 5 at 11:00
The
--noproxy
flag must be followed by a wildcard, v.gr. *
, otherwise www.google.com will be considered as the argument of --noproxy
and curl
will return 'no URL specified!'. I eddited my answer above. See the correct way to launch curl
and escape the *
.â Pierre François
Jan 5 at 11:00
that solved my problem thanks! but is there any way to use curl without this flag? there are lots of scripts which use curl and its hard to change them to use this flag
â Yashar
Jan 5 at 11:05
that solved my problem thanks! but is there any way to use curl without this flag? there are lots of scripts which use curl and its hard to change them to use this flag
â Yashar
Jan 5 at 11:05
You can define these settings in the
~/.curlrc
configuration file.â Pierre François
Jan 5 at 11:28
You can define these settings in the
~/.curlrc
configuration file.â Pierre François
Jan 5 at 11:28
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f414962%2fcurl-tries-to-connect-to-127-0-0-19050-by-default%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
1
Try using "curl --noproxy * google.com" This will disable the use of a proxy server for all addresses.
â Raman Sailopal
Jan 5 at 10:59