111: Connection Refused

Multi tool use
When I attempt to install packages through sudo apt-get install, no matter what I try to install, it returns a 111: Connection Refused error.
The web browser appears to work, but not sudo apt-get install. I attempted to install Ruby, PHP, and open-shift RHC tools, and I also attempted to use Synaptic to update/install packages, and I was unable to.
I get errors similar to the following, every time:
W: Failed to fetch http://security.ubuntu.com/ubuntu/pool/main /liby/libyaml > /libyaml-0-2_0.1.4-3ubuntu3.1_i386.deb
Could not connect to 155.238.4.87:8080 (155.238.4.87). - connect (111: Connection refused)
I am using Ubuntu 14.04.1 LTS.
I connect to my adsl router via wireless, and am running an image that i got from my university running on vmware, using Windows 10. The university used a proxy but I edited it out in the M2 setting file and edited firefox to auto detect proxy to get my internet working
Please can someone help me figure out how to fix this?
networking apt proxy synaptic
add a comment |
When I attempt to install packages through sudo apt-get install, no matter what I try to install, it returns a 111: Connection Refused error.
The web browser appears to work, but not sudo apt-get install. I attempted to install Ruby, PHP, and open-shift RHC tools, and I also attempted to use Synaptic to update/install packages, and I was unable to.
I get errors similar to the following, every time:
W: Failed to fetch http://security.ubuntu.com/ubuntu/pool/main /liby/libyaml > /libyaml-0-2_0.1.4-3ubuntu3.1_i386.deb
Could not connect to 155.238.4.87:8080 (155.238.4.87). - connect (111: Connection refused)
I am using Ubuntu 14.04.1 LTS.
I connect to my adsl router via wireless, and am running an image that i got from my university running on vmware, using Windows 10. The university used a proxy but I edited it out in the M2 setting file and edited firefox to auto detect proxy to get my internet working
Please can someone help me figure out how to fix this?
networking apt proxy synaptic
add a comment |
When I attempt to install packages through sudo apt-get install, no matter what I try to install, it returns a 111: Connection Refused error.
The web browser appears to work, but not sudo apt-get install. I attempted to install Ruby, PHP, and open-shift RHC tools, and I also attempted to use Synaptic to update/install packages, and I was unable to.
I get errors similar to the following, every time:
W: Failed to fetch http://security.ubuntu.com/ubuntu/pool/main /liby/libyaml > /libyaml-0-2_0.1.4-3ubuntu3.1_i386.deb
Could not connect to 155.238.4.87:8080 (155.238.4.87). - connect (111: Connection refused)
I am using Ubuntu 14.04.1 LTS.
I connect to my adsl router via wireless, and am running an image that i got from my university running on vmware, using Windows 10. The university used a proxy but I edited it out in the M2 setting file and edited firefox to auto detect proxy to get my internet working
Please can someone help me figure out how to fix this?
networking apt proxy synaptic
When I attempt to install packages through sudo apt-get install, no matter what I try to install, it returns a 111: Connection Refused error.
The web browser appears to work, but not sudo apt-get install. I attempted to install Ruby, PHP, and open-shift RHC tools, and I also attempted to use Synaptic to update/install packages, and I was unable to.
I get errors similar to the following, every time:
W: Failed to fetch http://security.ubuntu.com/ubuntu/pool/main /liby/libyaml > /libyaml-0-2_0.1.4-3ubuntu3.1_i386.deb
Could not connect to 155.238.4.87:8080 (155.238.4.87). - connect (111: Connection refused)
I am using Ubuntu 14.04.1 LTS.
I connect to my adsl router via wireless, and am running an image that i got from my university running on vmware, using Windows 10. The university used a proxy but I edited it out in the M2 setting file and edited firefox to auto detect proxy to get my internet working
Please can someone help me figure out how to fix this?
networking apt proxy synaptic
networking apt proxy synaptic
asked Sep 25 '15 at 11:20
LanceLance
12113
12113
add a comment |
add a comment |
5 Answers
5
active
oldest
votes
See if there's a proxy set in /etc/apt/apt.conf
(or somewhere in /etc/apt/apt/apt.conf.d
).
There'll be a file with a line something like:
Acquire::http::Proxy "http://155.238.4.87:8080";
Comment the line(s) by putting a #
at the beginning of it and try again.
I dont have either of those files, I only have one apt folder
– Lance
Sep 25 '15 at 15:03
think it was using a maven proxy before
– Lance
Sep 25 '15 at 15:04
I doubt apt-get was using a maven proxy - or at least I've never heard of such a thing...
– ssta
Sep 25 '15 at 15:42
I had to remove proxy setting in mavens settings.xml and change firefox to auto-detect proxy settings in order to access the internet but still get the same error when trying to download a package
– Lance
Sep 26 '15 at 7:48
add a comment |
I solve this error by removing network settings.
I do :
cat /etc/apt/apt.conf
If I see this
Acquire::http::proxy "http://macth-with-your-ip-or-dns-setting:8080/";
Acquire::https::proxy "https://macth-with-your-ip-or-dns-setting:9999/";
I go to network system settings and choose network then select Network Proxy Method see drop-down menu, choose manual then DELETE all settings there. Click Apply to save the setting or configuration that you made.
In the terminal do
cat /etc/apt/apt.conf
if there is no output, you have finished and you can apt-get update
add a comment |
Could not connect to x.x.x.x:8080
Connection to IP:8080
indicates that you're using proxy.
Here are few suggestions:
- Check by:
apt-config dump | grep -i proxy
. - If proxy is used, edit
/etc/apt/apt.conf
file or check for config files in/etc/apt/apt.conf.d/
or find bygrep -ri proxy /etc/apt/
, then adjust or remove the proxy.
To check the direct connection to
security.ubuntu.com
, run:
curl http://security.ubuntu.com/ && echo Works
To test the connection through proxy, run:
curl -x http://PROXYIP:8080/ http://security.ubuntu.com/ && echo Works
To debug networking for
apt-get
command, you can run:
strace -f -e network apt-get update 2>&1 | grep -C10 refused
Check your firewall rules and network configuration.
add a comment |
First check
/etc/apt/apt.conf
: if you foundAcquire::http::proxy "http://x.x.x.x:8080/"
just commented it with (#
) at the beginning of the line.Then check
/etc/environment
: if you foundhttp_proxy="http://x.x.x.x:8080/"
just commented it with (#
) on the beginning of the line.
add a comment |
If you are using the WSL(Windows Subsystem for Linux) version of Ubuntu, make sure you don't have any 3rd party Antivirus/firewalls enabled.
Try deactivating them and see if the connection goes back to normal.
There are known issues regarding 3rd party firewalls that do not behave well with WSL.
See the WSL GitHub issues 475 and 1720 for more details.
New contributor
kaltu is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f678285%2f111-connection-refused%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
5 Answers
5
active
oldest
votes
5 Answers
5
active
oldest
votes
active
oldest
votes
active
oldest
votes
See if there's a proxy set in /etc/apt/apt.conf
(or somewhere in /etc/apt/apt/apt.conf.d
).
There'll be a file with a line something like:
Acquire::http::Proxy "http://155.238.4.87:8080";
Comment the line(s) by putting a #
at the beginning of it and try again.
I dont have either of those files, I only have one apt folder
– Lance
Sep 25 '15 at 15:03
think it was using a maven proxy before
– Lance
Sep 25 '15 at 15:04
I doubt apt-get was using a maven proxy - or at least I've never heard of such a thing...
– ssta
Sep 25 '15 at 15:42
I had to remove proxy setting in mavens settings.xml and change firefox to auto-detect proxy settings in order to access the internet but still get the same error when trying to download a package
– Lance
Sep 26 '15 at 7:48
add a comment |
See if there's a proxy set in /etc/apt/apt.conf
(or somewhere in /etc/apt/apt/apt.conf.d
).
There'll be a file with a line something like:
Acquire::http::Proxy "http://155.238.4.87:8080";
Comment the line(s) by putting a #
at the beginning of it and try again.
I dont have either of those files, I only have one apt folder
– Lance
Sep 25 '15 at 15:03
think it was using a maven proxy before
– Lance
Sep 25 '15 at 15:04
I doubt apt-get was using a maven proxy - or at least I've never heard of such a thing...
– ssta
Sep 25 '15 at 15:42
I had to remove proxy setting in mavens settings.xml and change firefox to auto-detect proxy settings in order to access the internet but still get the same error when trying to download a package
– Lance
Sep 26 '15 at 7:48
add a comment |
See if there's a proxy set in /etc/apt/apt.conf
(or somewhere in /etc/apt/apt/apt.conf.d
).
There'll be a file with a line something like:
Acquire::http::Proxy "http://155.238.4.87:8080";
Comment the line(s) by putting a #
at the beginning of it and try again.
See if there's a proxy set in /etc/apt/apt.conf
(or somewhere in /etc/apt/apt/apt.conf.d
).
There'll be a file with a line something like:
Acquire::http::Proxy "http://155.238.4.87:8080";
Comment the line(s) by putting a #
at the beginning of it and try again.
answered Sep 25 '15 at 12:01
sstassta
54327
54327
I dont have either of those files, I only have one apt folder
– Lance
Sep 25 '15 at 15:03
think it was using a maven proxy before
– Lance
Sep 25 '15 at 15:04
I doubt apt-get was using a maven proxy - or at least I've never heard of such a thing...
– ssta
Sep 25 '15 at 15:42
I had to remove proxy setting in mavens settings.xml and change firefox to auto-detect proxy settings in order to access the internet but still get the same error when trying to download a package
– Lance
Sep 26 '15 at 7:48
add a comment |
I dont have either of those files, I only have one apt folder
– Lance
Sep 25 '15 at 15:03
think it was using a maven proxy before
– Lance
Sep 25 '15 at 15:04
I doubt apt-get was using a maven proxy - or at least I've never heard of such a thing...
– ssta
Sep 25 '15 at 15:42
I had to remove proxy setting in mavens settings.xml and change firefox to auto-detect proxy settings in order to access the internet but still get the same error when trying to download a package
– Lance
Sep 26 '15 at 7:48
I dont have either of those files, I only have one apt folder
– Lance
Sep 25 '15 at 15:03
I dont have either of those files, I only have one apt folder
– Lance
Sep 25 '15 at 15:03
think it was using a maven proxy before
– Lance
Sep 25 '15 at 15:04
think it was using a maven proxy before
– Lance
Sep 25 '15 at 15:04
I doubt apt-get was using a maven proxy - or at least I've never heard of such a thing...
– ssta
Sep 25 '15 at 15:42
I doubt apt-get was using a maven proxy - or at least I've never heard of such a thing...
– ssta
Sep 25 '15 at 15:42
I had to remove proxy setting in mavens settings.xml and change firefox to auto-detect proxy settings in order to access the internet but still get the same error when trying to download a package
– Lance
Sep 26 '15 at 7:48
I had to remove proxy setting in mavens settings.xml and change firefox to auto-detect proxy settings in order to access the internet but still get the same error when trying to download a package
– Lance
Sep 26 '15 at 7:48
add a comment |
I solve this error by removing network settings.
I do :
cat /etc/apt/apt.conf
If I see this
Acquire::http::proxy "http://macth-with-your-ip-or-dns-setting:8080/";
Acquire::https::proxy "https://macth-with-your-ip-or-dns-setting:9999/";
I go to network system settings and choose network then select Network Proxy Method see drop-down menu, choose manual then DELETE all settings there. Click Apply to save the setting or configuration that you made.
In the terminal do
cat /etc/apt/apt.conf
if there is no output, you have finished and you can apt-get update
add a comment |
I solve this error by removing network settings.
I do :
cat /etc/apt/apt.conf
If I see this
Acquire::http::proxy "http://macth-with-your-ip-or-dns-setting:8080/";
Acquire::https::proxy "https://macth-with-your-ip-or-dns-setting:9999/";
I go to network system settings and choose network then select Network Proxy Method see drop-down menu, choose manual then DELETE all settings there. Click Apply to save the setting or configuration that you made.
In the terminal do
cat /etc/apt/apt.conf
if there is no output, you have finished and you can apt-get update
add a comment |
I solve this error by removing network settings.
I do :
cat /etc/apt/apt.conf
If I see this
Acquire::http::proxy "http://macth-with-your-ip-or-dns-setting:8080/";
Acquire::https::proxy "https://macth-with-your-ip-or-dns-setting:9999/";
I go to network system settings and choose network then select Network Proxy Method see drop-down menu, choose manual then DELETE all settings there. Click Apply to save the setting or configuration that you made.
In the terminal do
cat /etc/apt/apt.conf
if there is no output, you have finished and you can apt-get update
I solve this error by removing network settings.
I do :
cat /etc/apt/apt.conf
If I see this
Acquire::http::proxy "http://macth-with-your-ip-or-dns-setting:8080/";
Acquire::https::proxy "https://macth-with-your-ip-or-dns-setting:9999/";
I go to network system settings and choose network then select Network Proxy Method see drop-down menu, choose manual then DELETE all settings there. Click Apply to save the setting or configuration that you made.
In the terminal do
cat /etc/apt/apt.conf
if there is no output, you have finished and you can apt-get update
edited Oct 15 '16 at 22:01


Zanna
50.6k13135241
50.6k13135241
answered Oct 15 '16 at 21:45
Raja Gading SiahaanRaja Gading Siahaan
111
111
add a comment |
add a comment |
Could not connect to x.x.x.x:8080
Connection to IP:8080
indicates that you're using proxy.
Here are few suggestions:
- Check by:
apt-config dump | grep -i proxy
. - If proxy is used, edit
/etc/apt/apt.conf
file or check for config files in/etc/apt/apt.conf.d/
or find bygrep -ri proxy /etc/apt/
, then adjust or remove the proxy.
To check the direct connection to
security.ubuntu.com
, run:
curl http://security.ubuntu.com/ && echo Works
To test the connection through proxy, run:
curl -x http://PROXYIP:8080/ http://security.ubuntu.com/ && echo Works
To debug networking for
apt-get
command, you can run:
strace -f -e network apt-get update 2>&1 | grep -C10 refused
Check your firewall rules and network configuration.
add a comment |
Could not connect to x.x.x.x:8080
Connection to IP:8080
indicates that you're using proxy.
Here are few suggestions:
- Check by:
apt-config dump | grep -i proxy
. - If proxy is used, edit
/etc/apt/apt.conf
file or check for config files in/etc/apt/apt.conf.d/
or find bygrep -ri proxy /etc/apt/
, then adjust or remove the proxy.
To check the direct connection to
security.ubuntu.com
, run:
curl http://security.ubuntu.com/ && echo Works
To test the connection through proxy, run:
curl -x http://PROXYIP:8080/ http://security.ubuntu.com/ && echo Works
To debug networking for
apt-get
command, you can run:
strace -f -e network apt-get update 2>&1 | grep -C10 refused
Check your firewall rules and network configuration.
add a comment |
Could not connect to x.x.x.x:8080
Connection to IP:8080
indicates that you're using proxy.
Here are few suggestions:
- Check by:
apt-config dump | grep -i proxy
. - If proxy is used, edit
/etc/apt/apt.conf
file or check for config files in/etc/apt/apt.conf.d/
or find bygrep -ri proxy /etc/apt/
, then adjust or remove the proxy.
To check the direct connection to
security.ubuntu.com
, run:
curl http://security.ubuntu.com/ && echo Works
To test the connection through proxy, run:
curl -x http://PROXYIP:8080/ http://security.ubuntu.com/ && echo Works
To debug networking for
apt-get
command, you can run:
strace -f -e network apt-get update 2>&1 | grep -C10 refused
Check your firewall rules and network configuration.
Could not connect to x.x.x.x:8080
Connection to IP:8080
indicates that you're using proxy.
Here are few suggestions:
- Check by:
apt-config dump | grep -i proxy
. - If proxy is used, edit
/etc/apt/apt.conf
file or check for config files in/etc/apt/apt.conf.d/
or find bygrep -ri proxy /etc/apt/
, then adjust or remove the proxy.
To check the direct connection to
security.ubuntu.com
, run:
curl http://security.ubuntu.com/ && echo Works
To test the connection through proxy, run:
curl -x http://PROXYIP:8080/ http://security.ubuntu.com/ && echo Works
To debug networking for
apt-get
command, you can run:
strace -f -e network apt-get update 2>&1 | grep -C10 refused
Check your firewall rules and network configuration.
answered Apr 15 '18 at 23:45
kenorbkenorb
4,38513953
4,38513953
add a comment |
add a comment |
First check
/etc/apt/apt.conf
: if you foundAcquire::http::proxy "http://x.x.x.x:8080/"
just commented it with (#
) at the beginning of the line.Then check
/etc/environment
: if you foundhttp_proxy="http://x.x.x.x:8080/"
just commented it with (#
) on the beginning of the line.
add a comment |
First check
/etc/apt/apt.conf
: if you foundAcquire::http::proxy "http://x.x.x.x:8080/"
just commented it with (#
) at the beginning of the line.Then check
/etc/environment
: if you foundhttp_proxy="http://x.x.x.x:8080/"
just commented it with (#
) on the beginning of the line.
add a comment |
First check
/etc/apt/apt.conf
: if you foundAcquire::http::proxy "http://x.x.x.x:8080/"
just commented it with (#
) at the beginning of the line.Then check
/etc/environment
: if you foundhttp_proxy="http://x.x.x.x:8080/"
just commented it with (#
) on the beginning of the line.
First check
/etc/apt/apt.conf
: if you foundAcquire::http::proxy "http://x.x.x.x:8080/"
just commented it with (#
) at the beginning of the line.Then check
/etc/environment
: if you foundhttp_proxy="http://x.x.x.x:8080/"
just commented it with (#
) on the beginning of the line.
edited Sep 26 '18 at 13:28


David Foerster
28k1365111
28k1365111
answered Sep 26 '18 at 7:58
goodCongoodCon
11
11
add a comment |
add a comment |
If you are using the WSL(Windows Subsystem for Linux) version of Ubuntu, make sure you don't have any 3rd party Antivirus/firewalls enabled.
Try deactivating them and see if the connection goes back to normal.
There are known issues regarding 3rd party firewalls that do not behave well with WSL.
See the WSL GitHub issues 475 and 1720 for more details.
New contributor
kaltu is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
If you are using the WSL(Windows Subsystem for Linux) version of Ubuntu, make sure you don't have any 3rd party Antivirus/firewalls enabled.
Try deactivating them and see if the connection goes back to normal.
There are known issues regarding 3rd party firewalls that do not behave well with WSL.
See the WSL GitHub issues 475 and 1720 for more details.
New contributor
kaltu is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
If you are using the WSL(Windows Subsystem for Linux) version of Ubuntu, make sure you don't have any 3rd party Antivirus/firewalls enabled.
Try deactivating them and see if the connection goes back to normal.
There are known issues regarding 3rd party firewalls that do not behave well with WSL.
See the WSL GitHub issues 475 and 1720 for more details.
New contributor
kaltu is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
If you are using the WSL(Windows Subsystem for Linux) version of Ubuntu, make sure you don't have any 3rd party Antivirus/firewalls enabled.
Try deactivating them and see if the connection goes back to normal.
There are known issues regarding 3rd party firewalls that do not behave well with WSL.
See the WSL GitHub issues 475 and 1720 for more details.
New contributor
kaltu is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited 2 days ago


Amolith
6031628
6031628
New contributor
kaltu is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 2 days ago
kaltukaltu
11
11
New contributor
kaltu is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
kaltu is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
kaltu is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f678285%2f111-connection-refused%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
vKC r,6TRq,I91vevkpzHfwSWAkYjN45NS32l pHQ9OToe1ec1,z