apt-get fails: The method driver /usr/lib/apt/methods/https could not be found
Clash Royale CLAN TAG#URR8PPP
up vote
22
down vote
favorite
I tried to update my OS Debian jessie using the terminal and i get an error :
“E: The method driver /usr/lib/apt/methods/https could not be found.†error?
My sources.list :
deb http://httpredir.debian.org/debian/ jessie main
deb-src http://httpredir.debian.org/debian/ jessie main
deb http://security.debian.org/ jessie/updates main
deb-src http://security.debian.org/ jessie/updates main
# jessie-updates, previously known as 'volatile'
deb http://httpredir.debian.org/debian/ jessie-updates main
deb-src http://httpredir.debian.org/debian/ jessie-updates main
deb http://ftp.de.debian.org/debian jessie main
How to fix apt-get update and aptitude update?
debian apt https
asked Feb 17 '16 at 11:15
GAD3R
23.8k1648100
add a comment |Â
up vote
22
down vote
favorite
I tried to update my OS Debian jessie using the terminal and i get an error :
“E: The method driver /usr/lib/apt/methods/https could not be found.†error?
My sources.list :
deb http://httpredir.debian.org/debian/ jessie main
deb-src http://httpredir.debian.org/debian/ jessie main
deb http://security.debian.org/ jessie/updates main
deb-src http://security.debian.org/ jessie/updates main
# jessie-updates, previously known as 'volatile'
deb http://httpredir.debian.org/debian/ jessie-updates main
deb-src http://httpredir.debian.org/debian/ jessie-updates main
deb http://ftp.de.debian.org/debian jessie main
How to fix apt-get update and aptitude update?
debian apt https
asked Feb 17 '16 at 11:15
GAD3R
23.8k1648100
1
Keep in mind that there's no integrity benefit to using HTTPS since packages have signatures that are verified anyway - which is probably even better since you're not trusting many independent CAs. THere ay be some privacy benefit. See also: unix.stackexchange.com/questions/90227/…
– Bob
Feb 18 '16 at 0:07
add a comment |Â
up vote
22
down vote
favorite
up vote
22
down vote
favorite
I tried to update my OS Debian jessie using the terminal and i get an error :
“E: The method driver /usr/lib/apt/methods/https could not be found.†error?
My sources.list :
deb http://httpredir.debian.org/debian/ jessie main
deb-src http://httpredir.debian.org/debian/ jessie main
deb http://security.debian.org/ jessie/updates main
deb-src http://security.debian.org/ jessie/updates main
# jessie-updates, previously known as 'volatile'
deb http://httpredir.debian.org/debian/ jessie-updates main
deb-src http://httpredir.debian.org/debian/ jessie-updates main
deb http://ftp.de.debian.org/debian jessie main
How to fix apt-get update and aptitude update?
debian apt https
asked Feb 17 '16 at 11:15
GAD3R
23.8k1648100
I tried to update my OS Debian jessie using the terminal and i get an error :
“E: The method driver /usr/lib/apt/methods/https could not be found.†error?
My sources.list :
deb http://httpredir.debian.org/debian/ jessie main
deb-src http://httpredir.debian.org/debian/ jessie main
deb http://security.debian.org/ jessie/updates main
deb-src http://security.debian.org/ jessie/updates main
# jessie-updates, previously known as 'volatile'
deb http://httpredir.debian.org/debian/ jessie-updates main
deb-src http://httpredir.debian.org/debian/ jessie-updates main
deb http://ftp.de.debian.org/debian jessie main
How to fix apt-get update and aptitude update?
debian apt https
debian apt https
asked Feb 17 '16 at 11:15
GAD3R
23.8k1648100
asked Feb 17 '16 at 11:15
GAD3R
23.8k1648100
edited Apr 23 '16 at 17:27
asked Feb 17 '16 at 11:15
GAD3R
23.8k1648100
asked Feb 17 '16 at 11:15
GAD3R
23.8k1648100
asked Feb 17 '16 at 11:15
GAD3R
23.8k1648100
23.8k1648100
1
Keep in mind that there's no integrity benefit to using HTTPS since packages have signatures that are verified anyway - which is probably even better since you're not trusting many independent CAs. THere ay be some privacy benefit. See also: unix.stackexchange.com/questions/90227/…
– Bob
Feb 18 '16 at 0:07
add a comment |Â
1
Keep in mind that there's no integrity benefit to using HTTPS since packages have signatures that are verified anyway - which is probably even better since you're not trusting many independent CAs. THere ay be some privacy benefit. See also: unix.stackexchange.com/questions/90227/…
– Bob
Feb 18 '16 at 0:07
1
1
Keep in mind that there's no integrity benefit to using HTTPS since packages have signatures that are verified anyway - which is probably even better since you're not trusting many independent CAs. THere ay be some privacy benefit. See also: unix.stackexchange.com/questions/90227/…
– Bob
Feb 18 '16 at 0:07
Keep in mind that there's no integrity benefit to using HTTPS since packages have signatures that are verified anyway - which is probably even better since you're not trusting many independent CAs. THere ay be some privacy benefit. See also: unix.stackexchange.com/questions/90227/…
– Bob
Feb 18 '16 at 0:07
add a comment |Â
3 Answers
3
active
oldest
votes
up vote
55
down vote
accepted
Sounds like you may have added some https sources. Since there are no https sources in your sources.list, it would be something in /etc/apt/sources.list.d/.
You may also be dealing with a proxy that always redirects to https.
You can add support for https apt sources by installing a couple of packages:
apt-get install apt-transport-https ca-certificates
If your apt-get is too broken to do this, you can download the package directly and install it with dpkg -i. Any additional dependencies of that package can be tracked down and fetched similarly (dpkg will let you know if anything is missing).
answered Feb 17 '16 at 11:24
Matt Vollrath
1,104615
add a comment |Â
up vote
6
down vote
For me this issue happened because one of the mirrors happened to always redirect to https.
So none of my sources were https, but due to the redirect, apt would end up trying to fetch something off an https site.
To resolve this, I had to manually download and install:
libcurl3-gnutls and- apt-transport-https
(apt-transport-https had a dependency on libcurl3-gnutls).
Once those were installed, I was able to successfully install any other package, even if the mirror was on https.
answered Feb 4 '17 at 0:41
Awesome
6111
add a comment |Â
up vote
0
down vote
There are a few possible issues that can cause this issue. The most likely solution would be to run:
sudo apt-get install apt-transport-https
You can find more details and possible causes for this issue here.
answered 7 mins ago
Chaminda Bandara
2571217
add a comment |Â
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
55
down vote
accepted
Sounds like you may have added some https sources. Since there are no https sources in your sources.list, it would be something in /etc/apt/sources.list.d/.
You may also be dealing with a proxy that always redirects to https.
You can add support for https apt sources by installing a couple of packages:
apt-get install apt-transport-https ca-certificates
If your apt-get is too broken to do this, you can download the package directly and install it with dpkg -i. Any additional dependencies of that package can be tracked down and fetched similarly (dpkg will let you know if anything is missing).
answered Feb 17 '16 at 11:24
Matt Vollrath
1,104615
add a comment |Â
up vote
55
down vote
accepted
Sounds like you may have added some https sources. Since there are no https sources in your sources.list, it would be something in /etc/apt/sources.list.d/.
You may also be dealing with a proxy that always redirects to https.
You can add support for https apt sources by installing a couple of packages:
apt-get install apt-transport-https ca-certificates
If your apt-get is too broken to do this, you can download the package directly and install it with dpkg -i. Any additional dependencies of that package can be tracked down and fetched similarly (dpkg will let you know if anything is missing).
answered Feb 17 '16 at 11:24
Matt Vollrath
1,104615
add a comment |Â
up vote
55
down vote
accepted
up vote
55
down vote
accepted
Sounds like you may have added some https sources. Since there are no https sources in your sources.list, it would be something in /etc/apt/sources.list.d/.
You may also be dealing with a proxy that always redirects to https.
You can add support for https apt sources by installing a couple of packages:
apt-get install apt-transport-https ca-certificates
If your apt-get is too broken to do this, you can download the package directly and install it with dpkg -i. Any additional dependencies of that package can be tracked down and fetched similarly (dpkg will let you know if anything is missing).
answered Feb 17 '16 at 11:24
Matt Vollrath
1,104615
Sounds like you may have added some https sources. Since there are no https sources in your sources.list, it would be something in /etc/apt/sources.list.d/.
You may also be dealing with a proxy that always redirects to https.
You can add support for https apt sources by installing a couple of packages:
apt-get install apt-transport-https ca-certificates
If your apt-get is too broken to do this, you can download the package directly and install it with dpkg -i. Any additional dependencies of that package can be tracked down and fetched similarly (dpkg will let you know if anything is missing).
answered Feb 17 '16 at 11:24
Matt Vollrath
1,104615
edited Dec 13 '17 at 14:12
answered Feb 17 '16 at 11:24
Matt Vollrath
1,104615
answered Feb 17 '16 at 11:24
Matt Vollrath
1,104615
answered Feb 17 '16 at 11:24
Matt Vollrath
1,104615
1,104615
add a comment |Â
add a comment |Â
up vote
6
down vote
For me this issue happened because one of the mirrors happened to always redirect to https.
So none of my sources were https, but due to the redirect, apt would end up trying to fetch something off an https site.
To resolve this, I had to manually download and install:
libcurl3-gnutls and- apt-transport-https
(apt-transport-https had a dependency on libcurl3-gnutls).
Once those were installed, I was able to successfully install any other package, even if the mirror was on https.
answered Feb 4 '17 at 0:41
Awesome
6111
add a comment |Â
up vote
6
down vote
For me this issue happened because one of the mirrors happened to always redirect to https.
So none of my sources were https, but due to the redirect, apt would end up trying to fetch something off an https site.
To resolve this, I had to manually download and install:
libcurl3-gnutls and- apt-transport-https
(apt-transport-https had a dependency on libcurl3-gnutls).
Once those were installed, I was able to successfully install any other package, even if the mirror was on https.
answered Feb 4 '17 at 0:41
Awesome
6111
add a comment |Â
up vote
6
down vote
up vote
6
down vote
For me this issue happened because one of the mirrors happened to always redirect to https.
So none of my sources were https, but due to the redirect, apt would end up trying to fetch something off an https site.
To resolve this, I had to manually download and install:
libcurl3-gnutls and- apt-transport-https
(apt-transport-https had a dependency on libcurl3-gnutls).
Once those were installed, I was able to successfully install any other package, even if the mirror was on https.
answered Feb 4 '17 at 0:41
Awesome
6111
For me this issue happened because one of the mirrors happened to always redirect to https.
So none of my sources were https, but due to the redirect, apt would end up trying to fetch something off an https site.
To resolve this, I had to manually download and install:
libcurl3-gnutls and- apt-transport-https
(apt-transport-https had a dependency on libcurl3-gnutls).
Once those were installed, I was able to successfully install any other package, even if the mirror was on https.
answered Feb 4 '17 at 0:41
Awesome
6111
answered Feb 4 '17 at 0:41
Awesome
6111
answered Feb 4 '17 at 0:41
Awesome
6111
answered Feb 4 '17 at 0:41
Awesome
6111
6111
add a comment |Â
add a comment |Â
up vote
0
down vote
There are a few possible issues that can cause this issue. The most likely solution would be to run:
sudo apt-get install apt-transport-https
You can find more details and possible causes for this issue here.
answered 7 mins ago
Chaminda Bandara
2571217
add a comment |Â
up vote
0
down vote
There are a few possible issues that can cause this issue. The most likely solution would be to run:
sudo apt-get install apt-transport-https
You can find more details and possible causes for this issue here.
answered 7 mins ago
Chaminda Bandara
2571217
add a comment |Â
up vote
0
down vote
up vote
0
down vote
There are a few possible issues that can cause this issue. The most likely solution would be to run:
sudo apt-get install apt-transport-https
You can find more details and possible causes for this issue here.
answered 7 mins ago
Chaminda Bandara
2571217
There are a few possible issues that can cause this issue. The most likely solution would be to run:
sudo apt-get install apt-transport-https
You can find more details and possible causes for this issue here.
answered 7 mins ago
Chaminda Bandara
2571217
answered 7 mins ago
Chaminda Bandara
2571217
answered 7 mins ago
Chaminda Bandara
2571217
answered 7 mins ago
Chaminda Bandara
2571217
2571217
add a comment |Â
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%2f263801%2fapt-get-fails-the-method-driver-usr-lib-apt-methods-https-could-not-be-found%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
Keep in mind that there's no integrity benefit to using HTTPS since packages have signatures that are verified anyway - which is probably even better since you're not trusting many independent CAs. THere ay be some privacy benefit. See also: unix.stackexchange.com/questions/90227/…
– Bob
Feb 18 '16 at 0:07