Error apt-get update on Kali Linux System [duplicate]
up vote
-2
down vote
favorite
This question already has an answer here:
Why is Kali Linux so hard to set up? Why won't people help me?
5 answers
I am trying to update the system, but the following error appears, what should I do?
apt-get update
Ign:1 http://dl.google.com/linux/chrome/deb stable InRelease
Err:2 http://dl.google.com/linux/chrome/deb stable Release
Redirection loop encountered
Err:3 https://http.kali.org/kali kali-rolling InRelease
Could not connect to proxy:443 (103.224.182.210). - connect (111:Connection refused)
Reading package lists... Done
E: The repository 'http://dl.google.com/linux/chrome/deb stable Release'no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
apt kali-linux
New contributor
Matheus Vasconcellos is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
marked as duplicate by Rui F Ribeiro, roaima, Filipe Brandenburger, Mr Shunz, Thomas yesterday
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
add a comment |
up vote
-2
down vote
favorite
This question already has an answer here:
Why is Kali Linux so hard to set up? Why won't people help me?
5 answers
I am trying to update the system, but the following error appears, what should I do?
apt-get update
Ign:1 http://dl.google.com/linux/chrome/deb stable InRelease
Err:2 http://dl.google.com/linux/chrome/deb stable Release
Redirection loop encountered
Err:3 https://http.kali.org/kali kali-rolling InRelease
Could not connect to proxy:443 (103.224.182.210). - connect (111:Connection refused)
Reading package lists... Done
E: The repository 'http://dl.google.com/linux/chrome/deb stable Release'no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
apt kali-linux
New contributor
Matheus Vasconcellos is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
marked as duplicate by Rui F Ribeiro, roaima, Filipe Brandenburger, Mr Shunz, Thomas yesterday
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
What is the system you're on?
– SouravGhosh
yesterday
system kali linux
– Matheus Vasconcellos
yesterday
add a comment |
up vote
-2
down vote
favorite
up vote
-2
down vote
favorite
This question already has an answer here:
Why is Kali Linux so hard to set up? Why won't people help me?
5 answers
I am trying to update the system, but the following error appears, what should I do?
apt-get update
Ign:1 http://dl.google.com/linux/chrome/deb stable InRelease
Err:2 http://dl.google.com/linux/chrome/deb stable Release
Redirection loop encountered
Err:3 https://http.kali.org/kali kali-rolling InRelease
Could not connect to proxy:443 (103.224.182.210). - connect (111:Connection refused)
Reading package lists... Done
E: The repository 'http://dl.google.com/linux/chrome/deb stable Release'no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
apt kali-linux
New contributor
Matheus Vasconcellos is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
This question already has an answer here:
Why is Kali Linux so hard to set up? Why won't people help me?
5 answers
I am trying to update the system, but the following error appears, what should I do?
apt-get update
Ign:1 http://dl.google.com/linux/chrome/deb stable InRelease
Err:2 http://dl.google.com/linux/chrome/deb stable Release
Redirection loop encountered
Err:3 https://http.kali.org/kali kali-rolling InRelease
Could not connect to proxy:443 (103.224.182.210). - connect (111:Connection refused)
Reading package lists... Done
E: The repository 'http://dl.google.com/linux/chrome/deb stable Release'no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
This question already has an answer here:
Why is Kali Linux so hard to set up? Why won't people help me?
5 answers
apt kali-linux
apt kali-linux
New contributor
Matheus Vasconcellos is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Matheus Vasconcellos is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited yesterday
Sylla
603
603
New contributor
Matheus Vasconcellos is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked yesterday
Matheus Vasconcellos
6
6
New contributor
Matheus Vasconcellos is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Matheus Vasconcellos is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Matheus Vasconcellos is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
marked as duplicate by Rui F Ribeiro, roaima, Filipe Brandenburger, Mr Shunz, Thomas yesterday
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
marked as duplicate by Rui F Ribeiro, roaima, Filipe Brandenburger, Mr Shunz, Thomas yesterday
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
What is the system you're on?
– SouravGhosh
yesterday
system kali linux
– Matheus Vasconcellos
yesterday
add a comment |
What is the system you're on?
– SouravGhosh
yesterday
system kali linux
– Matheus Vasconcellos
yesterday
What is the system you're on?
– SouravGhosh
yesterday
What is the system you're on?
– SouravGhosh
yesterday
system kali linux
– Matheus Vasconcellos
yesterday
system kali linux
– Matheus Vasconcellos
yesterday
add a comment |
2 Answers
2
active
oldest
votes
up vote
1
down vote
you have two issues:
1) Err:1 https://http.kali.org/kali kali-rolling InRelease and
2) Err:3 http://dl.google.com/linux/chrome/deb stable Release
To fix the 1st issue:
3) Edit your /etc/apt/sources.list and change from deb https://http.kali.org/kali to deb http://http.kali.org/kali kali-rolling main contrib non-free
To fix the 2nd issue:
4) Edit your /etc/apt/sources.list and remove http://dl.google.com/linux/chrome/deb , saved and update your apt.
For more details see https://askubuntu.com/questions/1100734/error-apt-get-update
add a comment |
up vote
-2
down vote
You probably have lower level networking issues.
But to address the symptoms you show here, you'll need to check your /etc/apt/sources.list and make sure they're actually reachable from your device.
2
Could not connect to proxy:443 (103.224.182.210). - connect (111:Connection refused)is a pretty good hint that the sources are, indeed, not reachable...
– Jeff Schaller
yesterday
Hmm, so why was I downvoted? Maybe because I didn't provide full / precise answer? (new to stack exchange world)
– Jake Hassings
23 hours ago
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
you have two issues:
1) Err:1 https://http.kali.org/kali kali-rolling InRelease and
2) Err:3 http://dl.google.com/linux/chrome/deb stable Release
To fix the 1st issue:
3) Edit your /etc/apt/sources.list and change from deb https://http.kali.org/kali to deb http://http.kali.org/kali kali-rolling main contrib non-free
To fix the 2nd issue:
4) Edit your /etc/apt/sources.list and remove http://dl.google.com/linux/chrome/deb , saved and update your apt.
For more details see https://askubuntu.com/questions/1100734/error-apt-get-update
add a comment |
up vote
1
down vote
you have two issues:
1) Err:1 https://http.kali.org/kali kali-rolling InRelease and
2) Err:3 http://dl.google.com/linux/chrome/deb stable Release
To fix the 1st issue:
3) Edit your /etc/apt/sources.list and change from deb https://http.kali.org/kali to deb http://http.kali.org/kali kali-rolling main contrib non-free
To fix the 2nd issue:
4) Edit your /etc/apt/sources.list and remove http://dl.google.com/linux/chrome/deb , saved and update your apt.
For more details see https://askubuntu.com/questions/1100734/error-apt-get-update
add a comment |
up vote
1
down vote
up vote
1
down vote
you have two issues:
1) Err:1 https://http.kali.org/kali kali-rolling InRelease and
2) Err:3 http://dl.google.com/linux/chrome/deb stable Release
To fix the 1st issue:
3) Edit your /etc/apt/sources.list and change from deb https://http.kali.org/kali to deb http://http.kali.org/kali kali-rolling main contrib non-free
To fix the 2nd issue:
4) Edit your /etc/apt/sources.list and remove http://dl.google.com/linux/chrome/deb , saved and update your apt.
For more details see https://askubuntu.com/questions/1100734/error-apt-get-update
you have two issues:
1) Err:1 https://http.kali.org/kali kali-rolling InRelease and
2) Err:3 http://dl.google.com/linux/chrome/deb stable Release
To fix the 1st issue:
3) Edit your /etc/apt/sources.list and change from deb https://http.kali.org/kali to deb http://http.kali.org/kali kali-rolling main contrib non-free
To fix the 2nd issue:
4) Edit your /etc/apt/sources.list and remove http://dl.google.com/linux/chrome/deb , saved and update your apt.
For more details see https://askubuntu.com/questions/1100734/error-apt-get-update
answered yesterday
Sylla
603
603
add a comment |
add a comment |
up vote
-2
down vote
You probably have lower level networking issues.
But to address the symptoms you show here, you'll need to check your /etc/apt/sources.list and make sure they're actually reachable from your device.
2
Could not connect to proxy:443 (103.224.182.210). - connect (111:Connection refused)is a pretty good hint that the sources are, indeed, not reachable...
– Jeff Schaller
yesterday
Hmm, so why was I downvoted? Maybe because I didn't provide full / precise answer? (new to stack exchange world)
– Jake Hassings
23 hours ago
add a comment |
up vote
-2
down vote
You probably have lower level networking issues.
But to address the symptoms you show here, you'll need to check your /etc/apt/sources.list and make sure they're actually reachable from your device.
2
Could not connect to proxy:443 (103.224.182.210). - connect (111:Connection refused)is a pretty good hint that the sources are, indeed, not reachable...
– Jeff Schaller
yesterday
Hmm, so why was I downvoted? Maybe because I didn't provide full / precise answer? (new to stack exchange world)
– Jake Hassings
23 hours ago
add a comment |
up vote
-2
down vote
up vote
-2
down vote
You probably have lower level networking issues.
But to address the symptoms you show here, you'll need to check your /etc/apt/sources.list and make sure they're actually reachable from your device.
You probably have lower level networking issues.
But to address the symptoms you show here, you'll need to check your /etc/apt/sources.list and make sure they're actually reachable from your device.
answered yesterday
Jake Hassings
125
125
2
Could not connect to proxy:443 (103.224.182.210). - connect (111:Connection refused)is a pretty good hint that the sources are, indeed, not reachable...
– Jeff Schaller
yesterday
Hmm, so why was I downvoted? Maybe because I didn't provide full / precise answer? (new to stack exchange world)
– Jake Hassings
23 hours ago
add a comment |
2
Could not connect to proxy:443 (103.224.182.210). - connect (111:Connection refused)is a pretty good hint that the sources are, indeed, not reachable...
– Jeff Schaller
yesterday
Hmm, so why was I downvoted? Maybe because I didn't provide full / precise answer? (new to stack exchange world)
– Jake Hassings
23 hours ago
2
2
Could not connect to proxy:443 (103.224.182.210). - connect (111:Connection refused) is a pretty good hint that the sources are, indeed, not reachable...– Jeff Schaller
yesterday
Could not connect to proxy:443 (103.224.182.210). - connect (111:Connection refused) is a pretty good hint that the sources are, indeed, not reachable...– Jeff Schaller
yesterday
Hmm, so why was I downvoted? Maybe because I didn't provide full / precise answer? (new to stack exchange world)
– Jake Hassings
23 hours ago
Hmm, so why was I downvoted? Maybe because I didn't provide full / precise answer? (new to stack exchange world)
– Jake Hassings
23 hours ago
add a comment |
What is the system you're on?
– SouravGhosh
yesterday
system kali linux
– Matheus Vasconcellos
yesterday